I am having a problem with one of my databases since the log is getting
rather large dispite regular back up. I have heard that there a extended
stored proceedure that will recycle the log. Anyone have an idea..?
I really appreciate this.
"Recycle The Log" is a term used when talking about the SQL Server Errorlog.
The command in question is sp_cycle_errorlog. To view it use
sp_readerrorlog.
However, neither of these are any good to you as the log you are refering to
is the TransAction Log. There are numerous articles on the subject, here are
a few :-
http://www.support.microsoft.com/?id=256650 INF: How to Shrink the SQL
Server 7.0 Tran Log
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
http://www.support.microsoft.com/?id=272318 INF: Shrinking Log in SQL
Server 2000 with DBCC SHRINKFILE
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
HTH. Ryan
"bluefish" <bluefish@.discussions.microsoft.com> wrote in message
news:32533A4B-FC3A-4536-BD99-BD9BEFEAA1C9@.microsoft.com...
>I am having a problem with one of my databases since the log is getting
> rather large dispite regular back up. I have heard that there a extended
> stored proceedure that will recycle the log. Anyone have an idea..?
> I really appreciate this.
>
Showing posts with label regular. Show all posts
Showing posts with label regular. Show all posts
Wednesday, March 28, 2012
Log Full
I am having a problem with one of my databases since the log is getting
rather large dispite regular back up. I have heard that there a extended
stored proceedure that will recycle the log. Anyone have an idea..?
I really appreciate this."Recycle The Log" is a term used when talking about the SQL Server Errorlog.
The command in question is sp_cycle_errorlog. To view it use
sp_readerrorlog.
However, neither of these are any good to you as the log you are refering to
is the TransAction Log. There are numerous articles on the subject, here are
a few :-
http://www.support.microsoft.com/?id=256650 INF: How to Shrink the SQL
Server 7.0 Tran Log
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
http://www.support.microsoft.com/?id=272318 INF: Shrinking Log in SQL
Server 2000 with DBCC SHRINKFILE
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
--
HTH. Ryan
"bluefish" <bluefish@.discussions.microsoft.com> wrote in message
news:32533A4B-FC3A-4536-BD99-BD9BEFEAA1C9@.microsoft.com...
>I am having a problem with one of my databases since the log is getting
> rather large dispite regular back up. I have heard that there a extended
> stored proceedure that will recycle the log. Anyone have an idea..?
> I really appreciate this.
>
rather large dispite regular back up. I have heard that there a extended
stored proceedure that will recycle the log. Anyone have an idea..?
I really appreciate this."Recycle The Log" is a term used when talking about the SQL Server Errorlog.
The command in question is sp_cycle_errorlog. To view it use
sp_readerrorlog.
However, neither of these are any good to you as the log you are refering to
is the TransAction Log. There are numerous articles on the subject, here are
a few :-
http://www.support.microsoft.com/?id=256650 INF: How to Shrink the SQL
Server 7.0 Tran Log
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
http://www.support.microsoft.com/?id=272318 INF: Shrinking Log in SQL
Server 2000 with DBCC SHRINKFILE
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
--
HTH. Ryan
"bluefish" <bluefish@.discussions.microsoft.com> wrote in message
news:32533A4B-FC3A-4536-BD99-BD9BEFEAA1C9@.microsoft.com...
>I am having a problem with one of my databases since the log is getting
> rather large dispite regular back up. I have heard that there a extended
> stored proceedure that will recycle the log. Anyone have an idea..?
> I really appreciate this.
>
Log Full
I am having a problem with one of my databases since the log is getting
rather large dispite regular back up. I have heard that there a extended
stored proceedure that will recycle the log. Anyone have an idea..?
I really appreciate this."Recycle The Log" is a term used when talking about the SQL Server Errorlog.
The command in question is sp_cycle_errorlog. To view it use
sp_readerrorlog.
However, neither of these are any good to you as the log you are refering to
is the TransAction Log. There are numerous articles on the subject, here are
a few :-
http://www.support.microsoft.com/?id=256650 INF: How to Shrink the SQL
Server 7.0 Tran Log
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
http://www.support.microsoft.com/?id=272318 INF: Shrinking Log in SQL
Server 2000 with DBCC SHRINKFILE
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
HTH. Ryan
"bluefish" <bluefish@.discussions.microsoft.com> wrote in message
news:32533A4B-FC3A-4536-BD99-BD9BEFEAA1C9@.microsoft.com...
>I am having a problem with one of my databases since the log is getting
> rather large dispite regular back up. I have heard that there a extended
> stored proceedure that will recycle the log. Anyone have an idea..?
> I really appreciate this.
>sql
rather large dispite regular back up. I have heard that there a extended
stored proceedure that will recycle the log. Anyone have an idea..?
I really appreciate this."Recycle The Log" is a term used when talking about the SQL Server Errorlog.
The command in question is sp_cycle_errorlog. To view it use
sp_readerrorlog.
However, neither of these are any good to you as the log you are refering to
is the TransAction Log. There are numerous articles on the subject, here are
a few :-
http://www.support.microsoft.com/?id=256650 INF: How to Shrink the SQL
Server 7.0 Tran Log
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
http://www.support.microsoft.com/?id=272318 INF: Shrinking Log in SQL
Server 2000 with DBCC SHRINKFILE
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
HTH. Ryan
"bluefish" <bluefish@.discussions.microsoft.com> wrote in message
news:32533A4B-FC3A-4536-BD99-BD9BEFEAA1C9@.microsoft.com...
>I am having a problem with one of my databases since the log is getting
> rather large dispite regular back up. I have heard that there a extended
> stored proceedure that will recycle the log. Anyone have an idea..?
> I really appreciate this.
>sql
Wednesday, March 21, 2012
Log file is not truncated inspite of regular log backup
I am taking regular log backup (every 30 mins). But still
the log file size of one database is 1110MB even when no
users are connected.
While using dbcc shrinkfile, i am getting the following
msg:
Cannot shrink log file 2 (Gsap_Log) because all logical
log files are in use.
DBCC OPENTRAN gives:
Replicated Transaction Information:
Oldest distributed LSN : (1134:527:1)
Oldest non-distributed LSN : (1134:1041:4)
Execution of the SP sp_repldone gives "The database is
not published."
EXEC sp_repldone @.xactid = NULL, @.xact_segno = NULL,
@.numtrans = 0, @.time = 0, @.reset = 1
Can anyone help me in truncating my log file?
Regards,
MangaiCheck out below KB articles:
INF: How to Shrink the SQL Server 7.0 Transaction Log
http://support.microsoft.com/default.aspx?scid=kb;en-us;256650
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/default.aspx?scid=kb;en-us;272318
Log File Grows too big
http://www.support.microsoft.com/?id=317375
Log file filling up
http://www.support.microsoft.com/?id=110139
Considerations for Autogrow and AutoShrink
http://www.support.microsoft.com/?id=315512
http://www.mssqlserver.com/faq/logs-shrinklog.asp
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Mangai" <mangaiyarkarasi_@.hotmail.com> wrote in message
news:007001c3af1e$a1c81570$a001280a@.phx.gbl...
> I am taking regular log backup (every 30 mins). But still
> the log file size of one database is 1110MB even when no
> users are connected.
> While using dbcc shrinkfile, i am getting the following
> msg:
> Cannot shrink log file 2 (Gsap_Log) because all logical
> log files are in use.
> DBCC OPENTRAN gives:
> Replicated Transaction Information:
> Oldest distributed LSN : (1134:527:1)
> Oldest non-distributed LSN : (1134:1041:4)
> Execution of the SP sp_repldone gives "The database is
> not published."
> EXEC sp_repldone @.xactid = NULL, @.xact_segno = NULL,
> @.numtrans = 0, @.time = 0, @.reset = 1
>
> Can anyone help me in truncating my log file?
> Regards,
> Mangai
>|||Got the solution.
Just created a publication on the server for the database
and executed sp_repldone with null values. The log file
was truncated and I had shrinked the log file to 10 MB.
>--Original Message--
>I am taking regular log backup (every 30 mins). But
still
>the log file size of one database is 1110MB even when no
>users are connected.
>While using dbcc shrinkfile, i am getting the following
>msg:
>Cannot shrink log file 2 (Gsap_Log) because all logical
>log files are in use.
>DBCC OPENTRAN gives:
>Replicated Transaction Information:
> Oldest distributed LSN : (1134:527:1)
> Oldest non-distributed LSN : (1134:1041:4)
>Execution of the SP sp_repldone gives "The database is
>not published."
>EXEC sp_repldone @.xactid = NULL, @.xact_segno = NULL,
>@.numtrans = 0, @.time = 0, @.reset = 1
>
>Can anyone help me in truncating my log file?
>Regards,
>Mangai
>.
>
the log file size of one database is 1110MB even when no
users are connected.
While using dbcc shrinkfile, i am getting the following
msg:
Cannot shrink log file 2 (Gsap_Log) because all logical
log files are in use.
DBCC OPENTRAN gives:
Replicated Transaction Information:
Oldest distributed LSN : (1134:527:1)
Oldest non-distributed LSN : (1134:1041:4)
Execution of the SP sp_repldone gives "The database is
not published."
EXEC sp_repldone @.xactid = NULL, @.xact_segno = NULL,
@.numtrans = 0, @.time = 0, @.reset = 1
Can anyone help me in truncating my log file?
Regards,
MangaiCheck out below KB articles:
INF: How to Shrink the SQL Server 7.0 Transaction Log
http://support.microsoft.com/default.aspx?scid=kb;en-us;256650
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/default.aspx?scid=kb;en-us;272318
Log File Grows too big
http://www.support.microsoft.com/?id=317375
Log file filling up
http://www.support.microsoft.com/?id=110139
Considerations for Autogrow and AutoShrink
http://www.support.microsoft.com/?id=315512
http://www.mssqlserver.com/faq/logs-shrinklog.asp
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Mangai" <mangaiyarkarasi_@.hotmail.com> wrote in message
news:007001c3af1e$a1c81570$a001280a@.phx.gbl...
> I am taking regular log backup (every 30 mins). But still
> the log file size of one database is 1110MB even when no
> users are connected.
> While using dbcc shrinkfile, i am getting the following
> msg:
> Cannot shrink log file 2 (Gsap_Log) because all logical
> log files are in use.
> DBCC OPENTRAN gives:
> Replicated Transaction Information:
> Oldest distributed LSN : (1134:527:1)
> Oldest non-distributed LSN : (1134:1041:4)
> Execution of the SP sp_repldone gives "The database is
> not published."
> EXEC sp_repldone @.xactid = NULL, @.xact_segno = NULL,
> @.numtrans = 0, @.time = 0, @.reset = 1
>
> Can anyone help me in truncating my log file?
> Regards,
> Mangai
>|||Got the solution.
Just created a publication on the server for the database
and executed sp_repldone with null values. The log file
was truncated and I had shrinked the log file to 10 MB.
>--Original Message--
>I am taking regular log backup (every 30 mins). But
still
>the log file size of one database is 1110MB even when no
>users are connected.
>While using dbcc shrinkfile, i am getting the following
>msg:
>Cannot shrink log file 2 (Gsap_Log) because all logical
>log files are in use.
>DBCC OPENTRAN gives:
>Replicated Transaction Information:
> Oldest distributed LSN : (1134:527:1)
> Oldest non-distributed LSN : (1134:1041:4)
>Execution of the SP sp_repldone gives "The database is
>not published."
>EXEC sp_repldone @.xactid = NULL, @.xact_segno = NULL,
>@.numtrans = 0, @.time = 0, @.reset = 1
>
>Can anyone help me in truncating my log file?
>Regards,
>Mangai
>.
>
Monday, March 12, 2012
Log File Backups
I am running regular maintenance jobs to back up database files nightly and
incremental log file backups every hour between 6am and 8pm. I notice that
the first log file backup seem to be extremely large 5gig, the database
backup that is created 7 hours prior to that is 4.1 gig. (SQL2000
standard - SP4) Can someone tell me if there is a better way to run these
job and what are the best parameters to include in a job to run this type of
job ? OR is it a normal thing for the first log file backup to be so
huge? Thanks,...
WANNABE wrote:
> I am running regular maintenance jobs to back up database files nightly and
> incremental log file backups every hour between 6am and 8pm. I notice that
> the first log file backup seem to be extremely large 5gig, the database
> backup that is created 7 hours prior to that is 4.1 gig. (SQL2000
> standard - SP4) Can someone tell me if there is a better way to run these
> job and what are the best parameters to include in a job to run this type of
> job ? OR is it a normal thing for the first log file backup to be so
> huge? Thanks,...
>
If there is alot of activity in the database during the 7 hours between
the full backup and the first log backup, then yes, it will be large.
What processes are run against that database overnight?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Yes, there are about 15 Stored Procs that run during the night to
recalculate
values, and adjustments.. But for the log backup to be larger then the db
backup
I was puzzled. Thanks
==============================================
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45534747.70107@.realsqlguy.com...
> WANNABE wrote:
> If there is alot of activity in the database during the 7 hours between
> the full backup and the first log backup, then yes, it will be large. What
> processes are run against that database overnight?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||WANNABE wrote:
> Yes, there are about 15 Stored Procs that run during the night to
> recalculate
> values, and adjustments.. But for the log backup to be larger then the db
> backup
> I was puzzled. Thanks
The log file is basically a "journal", recording everything that happens
in the database. Those journal entries continue to accumulate until you
perform a log backup, at which point they are flushed out. You might
consider doing log backups around the clock, rather than just between
6am and 8pm...
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Thank you, I will try log file backups around the clock
==========================================
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45534CF9.2040700@.realsqlguy.com...
> WANNABE wrote:
> The log file is basically a "journal", recording everything that happens
> in the database. Those journal entries continue to accumulate until you
> perform a log backup, at which point they are flushed out. You might
> consider doing log backups around the clock, rather than just between 6am
> and 8pm...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
incremental log file backups every hour between 6am and 8pm. I notice that
the first log file backup seem to be extremely large 5gig, the database
backup that is created 7 hours prior to that is 4.1 gig. (SQL2000
standard - SP4) Can someone tell me if there is a better way to run these
job and what are the best parameters to include in a job to run this type of
job ? OR is it a normal thing for the first log file backup to be so
huge? Thanks,...
WANNABE wrote:
> I am running regular maintenance jobs to back up database files nightly and
> incremental log file backups every hour between 6am and 8pm. I notice that
> the first log file backup seem to be extremely large 5gig, the database
> backup that is created 7 hours prior to that is 4.1 gig. (SQL2000
> standard - SP4) Can someone tell me if there is a better way to run these
> job and what are the best parameters to include in a job to run this type of
> job ? OR is it a normal thing for the first log file backup to be so
> huge? Thanks,...
>
If there is alot of activity in the database during the 7 hours between
the full backup and the first log backup, then yes, it will be large.
What processes are run against that database overnight?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Yes, there are about 15 Stored Procs that run during the night to
recalculate
values, and adjustments.. But for the log backup to be larger then the db
backup
I was puzzled. Thanks
==============================================
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45534747.70107@.realsqlguy.com...
> WANNABE wrote:
> If there is alot of activity in the database during the 7 hours between
> the full backup and the first log backup, then yes, it will be large. What
> processes are run against that database overnight?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||WANNABE wrote:
> Yes, there are about 15 Stored Procs that run during the night to
> recalculate
> values, and adjustments.. But for the log backup to be larger then the db
> backup
> I was puzzled. Thanks
The log file is basically a "journal", recording everything that happens
in the database. Those journal entries continue to accumulate until you
perform a log backup, at which point they are flushed out. You might
consider doing log backups around the clock, rather than just between
6am and 8pm...
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Thank you, I will try log file backups around the clock
==========================================
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45534CF9.2040700@.realsqlguy.com...
> WANNABE wrote:
> The log file is basically a "journal", recording everything that happens
> in the database. Those journal entries continue to accumulate until you
> perform a log backup, at which point they are flushed out. You might
> consider doing log backups around the clock, rather than just between 6am
> and 8pm...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Log File Backups
I am running regular maintenance jobs to back up database files nightly and
incremental log file backups every hour between 6am and 8pm. I notice that
the first log file backup seem to be extremely large 5gig, the database
backup that is created 7 hours prior to that is 4.1 gig. (SQL2000
standard - SP4) Can someone tell me if there is a better way to run these
job and what are the best parameters to include in a job to run this type of
job ' OR is it a normal thing for the first log file backup to be so
huge? Thanks,...WANNABE wrote:
> I am running regular maintenance jobs to back up database files nightly and
> incremental log file backups every hour between 6am and 8pm. I notice that
> the first log file backup seem to be extremely large 5gig, the database
> backup that is created 7 hours prior to that is 4.1 gig. (SQL2000
> standard - SP4) Can someone tell me if there is a better way to run these
> job and what are the best parameters to include in a job to run this type of
> job ' OR is it a normal thing for the first log file backup to be so
> huge? Thanks,...
>
If there is alot of activity in the database during the 7 hours between
the full backup and the first log backup, then yes, it will be large.
What processes are run against that database overnight?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yes, there are about 15 Stored Procs that run during the night to
recalculate
values, and adjustments.. But for the log backup to be larger then the db
backup
I was puzzled. Thanks
=============================================="Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45534747.70107@.realsqlguy.com...
> WANNABE wrote:
>> I am running regular maintenance jobs to back up database files nightly
>> and incremental log file backups every hour between 6am and 8pm. I
>> notice that the first log file backup seem to be extremely large 5gig,
>> the database backup that is created 7 hours prior to that is 4.1 gig.
>> (SQL2000 standard - SP4) Can someone tell me if there is a better way
>> to run these job and what are the best parameters to include in a job to
>> run this type of job ' OR is it a normal thing for the first log file
>> backup to be so huge? Thanks,...
> If there is alot of activity in the database during the 7 hours between
> the full backup and the first log backup, then yes, it will be large. What
> processes are run against that database overnight?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||WANNABE wrote:
> Yes, there are about 15 Stored Procs that run during the night to
> recalculate
> values, and adjustments.. But for the log backup to be larger then the db
> backup
> I was puzzled. Thanks
The log file is basically a "journal", recording everything that happens
in the database. Those journal entries continue to accumulate until you
perform a log backup, at which point they are flushed out. You might
consider doing log backups around the clock, rather than just between
6am and 8pm...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thank you, I will try log file backups around the clock
=========================================="Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45534CF9.2040700@.realsqlguy.com...
> WANNABE wrote:
>> Yes, there are about 15 Stored Procs that run during the night to
>> recalculate
>> values, and adjustments.. But for the log backup to be larger then the
>> db backup
>> I was puzzled. Thanks
> The log file is basically a "journal", recording everything that happens
> in the database. Those journal entries continue to accumulate until you
> perform a log backup, at which point they are flushed out. You might
> consider doing log backups around the clock, rather than just between 6am
> and 8pm...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
incremental log file backups every hour between 6am and 8pm. I notice that
the first log file backup seem to be extremely large 5gig, the database
backup that is created 7 hours prior to that is 4.1 gig. (SQL2000
standard - SP4) Can someone tell me if there is a better way to run these
job and what are the best parameters to include in a job to run this type of
job ' OR is it a normal thing for the first log file backup to be so
huge? Thanks,...WANNABE wrote:
> I am running regular maintenance jobs to back up database files nightly and
> incremental log file backups every hour between 6am and 8pm. I notice that
> the first log file backup seem to be extremely large 5gig, the database
> backup that is created 7 hours prior to that is 4.1 gig. (SQL2000
> standard - SP4) Can someone tell me if there is a better way to run these
> job and what are the best parameters to include in a job to run this type of
> job ' OR is it a normal thing for the first log file backup to be so
> huge? Thanks,...
>
If there is alot of activity in the database during the 7 hours between
the full backup and the first log backup, then yes, it will be large.
What processes are run against that database overnight?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yes, there are about 15 Stored Procs that run during the night to
recalculate
values, and adjustments.. But for the log backup to be larger then the db
backup
I was puzzled. Thanks
=============================================="Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45534747.70107@.realsqlguy.com...
> WANNABE wrote:
>> I am running regular maintenance jobs to back up database files nightly
>> and incremental log file backups every hour between 6am and 8pm. I
>> notice that the first log file backup seem to be extremely large 5gig,
>> the database backup that is created 7 hours prior to that is 4.1 gig.
>> (SQL2000 standard - SP4) Can someone tell me if there is a better way
>> to run these job and what are the best parameters to include in a job to
>> run this type of job ' OR is it a normal thing for the first log file
>> backup to be so huge? Thanks,...
> If there is alot of activity in the database during the 7 hours between
> the full backup and the first log backup, then yes, it will be large. What
> processes are run against that database overnight?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||WANNABE wrote:
> Yes, there are about 15 Stored Procs that run during the night to
> recalculate
> values, and adjustments.. But for the log backup to be larger then the db
> backup
> I was puzzled. Thanks
The log file is basically a "journal", recording everything that happens
in the database. Those journal entries continue to accumulate until you
perform a log backup, at which point they are flushed out. You might
consider doing log backups around the clock, rather than just between
6am and 8pm...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thank you, I will try log file backups around the clock
=========================================="Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45534CF9.2040700@.realsqlguy.com...
> WANNABE wrote:
>> Yes, there are about 15 Stored Procs that run during the night to
>> recalculate
>> values, and adjustments.. But for the log backup to be larger then the
>> db backup
>> I was puzzled. Thanks
> The log file is basically a "journal", recording everything that happens
> in the database. Those journal entries continue to accumulate until you
> perform a log backup, at which point they are flushed out. You might
> consider doing log backups around the clock, rather than just between 6am
> and 8pm...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Log File Backups
I am running regular maintenance jobs to back up database files nightly and
incremental log file backups every hour between 6am and 8pm. I notice that
the first log file backup seem to be extremely large 5gig, the database
backup that is created 7 hours prior to that is 4.1 gig. (SQL2000
standard - SP4) Can someone tell me if there is a better way to run these
job and what are the best parameters to include in a job to run this type of
job ' OR is it a normal thing for the first log file backup to be so
huge? Thanks,...WANNABE wrote:
> I am running regular maintenance jobs to back up database files nightly an
d
> incremental log file backups every hour between 6am and 8pm. I notice tha
t
> the first log file backup seem to be extremely large 5gig, the database
> backup that is created 7 hours prior to that is 4.1 gig. (SQL2000
> standard - SP4) Can someone tell me if there is a better way to run thes
e
> job and what are the best parameters to include in a job to run this type
of
> job ' OR is it a normal thing for the first log file backup to be so
> huge? Thanks,...
>
If there is alot of activity in the database during the 7 hours between
the full backup and the first log backup, then yes, it will be large.
What processes are run against that database overnight?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yes, there are about 15 Stored Procs that run during the night to
recalculate
values, and adjustments.. But for the log backup to be larger then the db
backup
I was puzzled. Thanks
========================================
======
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45534747.70107@.realsqlguy.com...
> WANNABE wrote:
> If there is alot of activity in the database during the 7 hours between
> the full backup and the first log backup, then yes, it will be large. What
> processes are run against that database overnight?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||WANNABE wrote:
> Yes, there are about 15 Stored Procs that run during the night to
> recalculate
> values, and adjustments.. But for the log backup to be larger then the db
> backup
> I was puzzled. Thanks
The log file is basically a "journal", recording everything that happens
in the database. Those journal entries continue to accumulate until you
perform a log backup, at which point they are flushed out. You might
consider doing log backups around the clock, rather than just between
6am and 8pm...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thank you, I will try log file backups around the clock
========================================
==
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45534CF9.2040700@.realsqlguy.com...
> WANNABE wrote:
> The log file is basically a "journal", recording everything that happens
> in the database. Those journal entries continue to accumulate until you
> perform a log backup, at which point they are flushed out. You might
> consider doing log backups around the clock, rather than just between 6am
> and 8pm...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
incremental log file backups every hour between 6am and 8pm. I notice that
the first log file backup seem to be extremely large 5gig, the database
backup that is created 7 hours prior to that is 4.1 gig. (SQL2000
standard - SP4) Can someone tell me if there is a better way to run these
job and what are the best parameters to include in a job to run this type of
job ' OR is it a normal thing for the first log file backup to be so
huge? Thanks,...WANNABE wrote:
> I am running regular maintenance jobs to back up database files nightly an
d
> incremental log file backups every hour between 6am and 8pm. I notice tha
t
> the first log file backup seem to be extremely large 5gig, the database
> backup that is created 7 hours prior to that is 4.1 gig. (SQL2000
> standard - SP4) Can someone tell me if there is a better way to run thes
e
> job and what are the best parameters to include in a job to run this type
of
> job ' OR is it a normal thing for the first log file backup to be so
> huge? Thanks,...
>
If there is alot of activity in the database during the 7 hours between
the full backup and the first log backup, then yes, it will be large.
What processes are run against that database overnight?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yes, there are about 15 Stored Procs that run during the night to
recalculate
values, and adjustments.. But for the log backup to be larger then the db
backup
I was puzzled. Thanks
========================================
======
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45534747.70107@.realsqlguy.com...
> WANNABE wrote:
> If there is alot of activity in the database during the 7 hours between
> the full backup and the first log backup, then yes, it will be large. What
> processes are run against that database overnight?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||WANNABE wrote:
> Yes, there are about 15 Stored Procs that run during the night to
> recalculate
> values, and adjustments.. But for the log backup to be larger then the db
> backup
> I was puzzled. Thanks
The log file is basically a "journal", recording everything that happens
in the database. Those journal entries continue to accumulate until you
perform a log backup, at which point they are flushed out. You might
consider doing log backups around the clock, rather than just between
6am and 8pm...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thank you, I will try log file backups around the clock
========================================
==
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45534CF9.2040700@.realsqlguy.com...
> WANNABE wrote:
> The log file is basically a "journal", recording everything that happens
> in the database. Those journal entries continue to accumulate until you
> perform a log backup, at which point they are flushed out. You might
> consider doing log backups around the clock, rather than just between 6am
> and 8pm...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Subscribe to:
Posts (Atom)