Hello Experts
We just started using SQL Server 7.0 in our organization which had come
along with BackOffice with NT 4.0. We have just started putting in some data
in it and have created some tables and some relationships.
My Question is
Should One Truncate Log?
If Yes When Should it be done?
Would appreciate your suggestions on this - THANKS in advance
Regards
Manish Sawjiani
Three Cheers to Technet for the Help!
I suggest you start with Tibor's aricle:
http://www.karaszi.com/sqlserver/info_dont_shrink.asp
-oj
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
message news:24CEF98E-AF48-4707-BA94-1AF01E796BAE@.microsoft.com...
> Hello Experts
> We just started using SQL Server 7.0 in our organization which had come
> along with BackOffice with NT 4.0. We have just started putting in some
> data
> in it and have created some tables and some relationships.
> My Question is
> Should One Truncate Log?
> If Yes When Should it be done?
> Would appreciate your suggestions on this - THANKS in advance
> Regards
> Manish Sawjiani
> --
> Three Cheers to Technet for the Help!
|||Hi,
If it is not production database you could set the database option "Truncate
Log on Checkpoint". This will clear the Transaction log byy may itself.
If it is a production database or if the data is critical then you can not
enable the Truncate log on checkpoint option. Instead of that you have to
perform
Transaction log backup (See BACKUP LOG in books online). After the
Trasnaction log backup Log will be automatically cleared.
Thanks
Hari
SQL Server DBA
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
message news:24CEF98E-AF48-4707-BA94-1AF01E796BAE@.microsoft.com...
> Hello Experts
> We just started using SQL Server 7.0 in our organization which had come
> along with BackOffice with NT 4.0. We have just started putting in some
> data
> in it and have created some tables and some relationships.
> My Question is
> Should One Truncate Log?
> If Yes When Should it be done?
> Would appreciate your suggestions on this - THANKS in advance
> Regards
> Manish Sawjiani
> --
> Three Cheers to Technet for the Help!
Showing posts with label truncate. Show all posts
Showing posts with label truncate. Show all posts
Tuesday, March 27, 2012
Basic Question - Truncate Log
Basic Question - Truncate Log
Hello Experts
We just started using SQL Server 7.0 in our organization which had come
along with BackOffice with NT 4.0. We have just started putting in some data
in it and have created some tables and some relationships.
My Question is
Should One Truncate Log?
If Yes When Should it be done?
Would appreciate your suggestions on this - THANKS in advance
Regards
Manish Sawjiani
--
Three Cheers to Technet for the Help!I suggest you start with Tibor's aricle:
http://www.karaszi.com/sqlserver/info_dont_shrink.asp
--
-oj
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
message news:24CEF98E-AF48-4707-BA94-1AF01E796BAE@.microsoft.com...
> Hello Experts
> We just started using SQL Server 7.0 in our organization which had come
> along with BackOffice with NT 4.0. We have just started putting in some
> data
> in it and have created some tables and some relationships.
> My Question is
> Should One Truncate Log?
> If Yes When Should it be done?
> Would appreciate your suggestions on this - THANKS in advance
> Regards
> Manish Sawjiani
> --
> Three Cheers to Technet for the Help!|||Hi,
If it is not production database you could set the database option "Truncate
Log on Checkpoint". This will clear the Transaction log byy may itself.
If it is a production database or if the data is critical then you can not
enable the Truncate log on checkpoint option. Instead of that you have to
perform
Transaction log backup (See BACKUP LOG in books online). After the
Trasnaction log backup Log will be automatically cleared.
Thanks
Hari
SQL Server DBA
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
message news:24CEF98E-AF48-4707-BA94-1AF01E796BAE@.microsoft.com...
> Hello Experts
> We just started using SQL Server 7.0 in our organization which had come
> along with BackOffice with NT 4.0. We have just started putting in some
> data
> in it and have created some tables and some relationships.
> My Question is
> Should One Truncate Log?
> If Yes When Should it be done?
> Would appreciate your suggestions on this - THANKS in advance
> Regards
> Manish Sawjiani
> --
> Three Cheers to Technet for the Help!
We just started using SQL Server 7.0 in our organization which had come
along with BackOffice with NT 4.0. We have just started putting in some data
in it and have created some tables and some relationships.
My Question is
Should One Truncate Log?
If Yes When Should it be done?
Would appreciate your suggestions on this - THANKS in advance
Regards
Manish Sawjiani
--
Three Cheers to Technet for the Help!I suggest you start with Tibor's aricle:
http://www.karaszi.com/sqlserver/info_dont_shrink.asp
--
-oj
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
message news:24CEF98E-AF48-4707-BA94-1AF01E796BAE@.microsoft.com...
> Hello Experts
> We just started using SQL Server 7.0 in our organization which had come
> along with BackOffice with NT 4.0. We have just started putting in some
> data
> in it and have created some tables and some relationships.
> My Question is
> Should One Truncate Log?
> If Yes When Should it be done?
> Would appreciate your suggestions on this - THANKS in advance
> Regards
> Manish Sawjiani
> --
> Three Cheers to Technet for the Help!|||Hi,
If it is not production database you could set the database option "Truncate
Log on Checkpoint". This will clear the Transaction log byy may itself.
If it is a production database or if the data is critical then you can not
enable the Truncate log on checkpoint option. Instead of that you have to
perform
Transaction log backup (See BACKUP LOG in books online). After the
Trasnaction log backup Log will be automatically cleared.
Thanks
Hari
SQL Server DBA
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
message news:24CEF98E-AF48-4707-BA94-1AF01E796BAE@.microsoft.com...
> Hello Experts
> We just started using SQL Server 7.0 in our organization which had come
> along with BackOffice with NT 4.0. We have just started putting in some
> data
> in it and have created some tables and some relationships.
> My Question is
> Should One Truncate Log?
> If Yes When Should it be done?
> Would appreciate your suggestions on this - THANKS in advance
> Regards
> Manish Sawjiani
> --
> Three Cheers to Technet for the Help!
Basic Question - Truncate Log
Hello Experts
We just started using SQL Server 7.0 in our organization which had come
along with BackOffice with NT 4.0. We have just started putting in some data
in it and have created some tables and some relationships.
My Question is
Should One Truncate Log?
If Yes When Should it be done?
Would appreciate your suggestions on this - THANKS in advance
Regards
Manish Sawjiani
--
Three Cheers to technet for the Help!I suggest you start with Tibor's aricle:
http://www.karaszi.com/sqlserver/info_dont_shrink.asp
-oj
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
message news:24CEF98E-AF48-4707-BA94-1AF01E796BAE@.microsoft.com...
> Hello Experts
> We just started using SQL Server 7.0 in our organization which had come
> along with BackOffice with NT 4.0. We have just started putting in some
> data
> in it and have created some tables and some relationships.
> My Question is
> Should One Truncate Log?
> If Yes When Should it be done?
> Would appreciate your suggestions on this - THANKS in advance
> Regards
> Manish Sawjiani
> --
> Three Cheers to technet for the Help!|||Hi,
If it is not production database you could set the database option "Truncate
Log on Checkpoint". This will clear the Transaction log byy may itself.
If it is a production database or if the data is critical then you can not
enable the Truncate log on checkpoint option. Instead of that you have to
perform
Transaction log backup (See BACKUP LOG in books online). After the
Trasnaction log backup Log will be automatically cleared.
Thanks
Hari
SQL Server DBA
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
message news:24CEF98E-AF48-4707-BA94-1AF01E796BAE@.microsoft.com...
> Hello Experts
> We just started using SQL Server 7.0 in our organization which had come
> along with BackOffice with NT 4.0. We have just started putting in some
> data
> in it and have created some tables and some relationships.
> My Question is
> Should One Truncate Log?
> If Yes When Should it be done?
> Would appreciate your suggestions on this - THANKS in advance
> Regards
> Manish Sawjiani
> --
> Three Cheers to technet for the Help!sql
We just started using SQL Server 7.0 in our organization which had come
along with BackOffice with NT 4.0. We have just started putting in some data
in it and have created some tables and some relationships.
My Question is
Should One Truncate Log?
If Yes When Should it be done?
Would appreciate your suggestions on this - THANKS in advance
Regards
Manish Sawjiani
--
Three Cheers to technet for the Help!I suggest you start with Tibor's aricle:
http://www.karaszi.com/sqlserver/info_dont_shrink.asp
-oj
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
message news:24CEF98E-AF48-4707-BA94-1AF01E796BAE@.microsoft.com...
> Hello Experts
> We just started using SQL Server 7.0 in our organization which had come
> along with BackOffice with NT 4.0. We have just started putting in some
> data
> in it and have created some tables and some relationships.
> My Question is
> Should One Truncate Log?
> If Yes When Should it be done?
> Would appreciate your suggestions on this - THANKS in advance
> Regards
> Manish Sawjiani
> --
> Three Cheers to technet for the Help!|||Hi,
If it is not production database you could set the database option "Truncate
Log on Checkpoint". This will clear the Transaction log byy may itself.
If it is a production database or if the data is critical then you can not
enable the Truncate log on checkpoint option. Instead of that you have to
perform
Transaction log backup (See BACKUP LOG in books online). After the
Trasnaction log backup Log will be automatically cleared.
Thanks
Hari
SQL Server DBA
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in
message news:24CEF98E-AF48-4707-BA94-1AF01E796BAE@.microsoft.com...
> Hello Experts
> We just started using SQL Server 7.0 in our organization which had come
> along with BackOffice with NT 4.0. We have just started putting in some
> data
> in it and have created some tables and some relationships.
> My Question is
> Should One Truncate Log?
> If Yes When Should it be done?
> Would appreciate your suggestions on this - THANKS in advance
> Regards
> Manish Sawjiani
> --
> Three Cheers to technet for the Help!sql
Sunday, February 12, 2012
Backup Transaction Job with NO truncate
Is there a way to setup a SQL Agent backup job to backup the transaction log and NOT truncate it
I can't seem to find any information on this.How about BACKUP LOG YourDatabase WITH NO_TRUNCATE? Why would you want to
back it up and never truncate it?
--
Andrew J. Kelly
SQL Server MVP
"mannie" <anonymous@.discussions.microsoft.com> wrote in message
news:C1903053-1B63-433D-A9DD-AACED12D83F2@.microsoft.com...
> Is there a way to setup a SQL Agent backup job to backup the transaction
log and NOT truncate it.
> I can't seem to find any information on this.|||You can use the syntax Backup log dbname to device
with no_truncate.
Regards,
Paul Ibison
I can't seem to find any information on this.How about BACKUP LOG YourDatabase WITH NO_TRUNCATE? Why would you want to
back it up and never truncate it?
--
Andrew J. Kelly
SQL Server MVP
"mannie" <anonymous@.discussions.microsoft.com> wrote in message
news:C1903053-1B63-433D-A9DD-AACED12D83F2@.microsoft.com...
> Is there a way to setup a SQL Agent backup job to backup the transaction
log and NOT truncate it.
> I can't seem to find any information on this.|||You can use the syntax Backup log dbname to device
with no_truncate.
Regards,
Paul Ibison
Backup Transaction Job with NO truncate
Is there a way to setup a SQL Agent backup job to backup the transaction log
and NOT truncate it.
I can't seem to find any information on this.How about BACKUP LOG YourDatabase WITH NO_TRUNCATE? Why would you want to
back it up and never truncate it?
Andrew J. Kelly
SQL Server MVP
"mannie" <anonymous@.discussions.microsoft.com> wrote in message
news:C1903053-1B63-433D-A9DD-AACED12D83F2@.microsoft.com...
> Is there a way to setup a SQL Agent backup job to backup the transaction
log and NOT truncate it.
> I can't seem to find any information on this.
and NOT truncate it.
I can't seem to find any information on this.How about BACKUP LOG YourDatabase WITH NO_TRUNCATE? Why would you want to
back it up and never truncate it?
Andrew J. Kelly
SQL Server MVP
"mannie" <anonymous@.discussions.microsoft.com> wrote in message
news:C1903053-1B63-433D-A9DD-AACED12D83F2@.microsoft.com...
> Is there a way to setup a SQL Agent backup job to backup the transaction
log and NOT truncate it.
> I can't seem to find any information on this.
Subscribe to:
Posts (Atom)