|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Transaction logI have a weird issue. I need to be able to see my transaction log for SOX
reasons. We have purchased Log Explorer from Lumigent to do this. However, on different databases, we see see differing lengths of data. Some we can see back several months, while our most important, we can only see a couple of days. I know that from time to time, SQL will shrink the database, how do I get it so that it will not truncate the log file, but compress it? Is there a database property that I need to set or a server setting. Any help would be greatly appreciated. If you need to keep history of your transaction log, you need to have the database in full recovery
mode and perform regular transaction log backups. Yo can now find what you are looking for either in the active transaction log, or any of your transaction log backup files. -- Show quoteTibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ Blog: http://solidqualitylearning.com/blogs/tibor/ "DBA" <D**@discussions.microsoft.com> wrote in message news:FA7D6522-25D0-4813-A463-30410BA8C9C7@microsoft.com... >I have a weird issue. I need to be able to see my transaction log for SOX > reasons. We have purchased Log Explorer from Lumigent to do this. However, on > different databases, we see see differing lengths of data. Some we can see > back several months, while our most important, we can only see a couple of > days. I know that from time to time, SQL will shrink the database, how do I > get it so that it will not truncate the log file, but compress it? Is there a > database property that I need to set or a server setting. Any help would be > greatly appreciated. but I look in the active trans log and it rarely goes back more than a couple
of days Show quote "Tibor Karaszi" wrote: > If you need to keep history of your transaction log, you need to have the database in full recovery > mode and perform regular transaction log backups. Yo can now find what you are looking for either in > the active transaction log, or any of your transaction log backup files. > > -- > Tibor Karaszi, SQL Server MVP > http://www.karaszi.com/sqlserver/default.asp > http://www.solidqualitylearning.com/ > Blog: http://solidqualitylearning.com/blogs/tibor/ > > > "DBA" <D**@discussions.microsoft.com> wrote in message > news:FA7D6522-25D0-4813-A463-30410BA8C9C7@microsoft.com... > >I have a weird issue. I need to be able to see my transaction log for SOX > > reasons. We have purchased Log Explorer from Lumigent to do this. However, on > > different databases, we see see differing lengths of data. Some we can see > > back several months, while our most important, we can only see a couple of > > days. I know that from time to time, SQL will shrink the database, how do I > > get it so that it will not truncate the log file, but compress it? Is there a > > database property that I need to set or a server setting. Any help would be > > greatly appreciated. > > What recovery model? If simple, it is cleared regularly (each time a checkpoint is performed). If
full, it is cleared when you do BACKUP LOG. -- Show quoteTibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ Blog: http://solidqualitylearning.com/blogs/tibor/ "DBA" <D**@discussions.microsoft.com> wrote in message news:4A7F0586-2EEC-42E6-8D92-5A533FD489AD@microsoft.com... > but I look in the active trans log and it rarely goes back more than a couple > of days > > "Tibor Karaszi" wrote: > >> If you need to keep history of your transaction log, you need to have the database in full >> recovery >> mode and perform regular transaction log backups. Yo can now find what you are looking for either >> in >> the active transaction log, or any of your transaction log backup files. >> >> -- >> Tibor Karaszi, SQL Server MVP >> http://www.karaszi.com/sqlserver/default.asp >> http://www.solidqualitylearning.com/ >> Blog: http://solidqualitylearning.com/blogs/tibor/ >> >> >> "DBA" <D**@discussions.microsoft.com> wrote in message >> news:FA7D6522-25D0-4813-A463-30410BA8C9C7@microsoft.com... >> >I have a weird issue. I need to be able to see my transaction log for SOX >> > reasons. We have purchased Log Explorer from Lumigent to do this. However, on >> > different databases, we see see differing lengths of data. Some we can see >> > back several months, while our most important, we can only see a couple of >> > days. I know that from time to time, SQL will shrink the database, how do I >> > get it so that it will not truncate the log file, but compress it? Is there a >> > database property that I need to set or a server setting. Any help would be >> > greatly appreciated. >> >> Ah. Thye may be my problem. I changed it to full. We however do not do sql
backups but rather user veritas. It backs up the physical files Show quote "Tibor Karaszi" wrote: > What recovery model? If simple, it is cleared regularly (each time a checkpoint is performed). If > full, it is cleared when you do BACKUP LOG. > > -- > Tibor Karaszi, SQL Server MVP > http://www.karaszi.com/sqlserver/default.asp > http://www.solidqualitylearning.com/ > Blog: http://solidqualitylearning.com/blogs/tibor/ > > > "DBA" <D**@discussions.microsoft.com> wrote in message > news:4A7F0586-2EEC-42E6-8D92-5A533FD489AD@microsoft.com... > > but I look in the active trans log and it rarely goes back more than a couple > > of days > > > > "Tibor Karaszi" wrote: > > > >> If you need to keep history of your transaction log, you need to have the database in full > >> recovery > >> mode and perform regular transaction log backups. Yo can now find what you are looking for either > >> in > >> the active transaction log, or any of your transaction log backup files. > >> > >> -- > >> Tibor Karaszi, SQL Server MVP > >> http://www.karaszi.com/sqlserver/default.asp > >> http://www.solidqualitylearning.com/ > >> Blog: http://solidqualitylearning.com/blogs/tibor/ > >> > >> > >> "DBA" <D**@discussions.microsoft.com> wrote in message > >> news:FA7D6522-25D0-4813-A463-30410BA8C9C7@microsoft.com... > >> >I have a weird issue. I need to be able to see my transaction log for SOX > >> > reasons. We have purchased Log Explorer from Lumigent to do this. However, on > >> > different databases, we see see differing lengths of data. Some we can see > >> > back several months, while our most important, we can only see a couple of > >> > days. I know that from time to time, SQL will shrink the database, how do I > >> > get it so that it will not truncate the log file, but compress it? Is there a > >> > database property that I need to set or a server setting. Any help would be > >> > greatly appreciated. > >> > >> > > Just be aware that you will need to monitor the log space usage carefully
under full recovery mode. The log will grow until you back it up or truncate it or until it runs out of disk space. If you run out of space then further updates won't be possible. >We however do not do sql backups Why not? Given the advantages of log backups I would personally favour developing a separate logging process and leaving the transaction log to get on with what it does best: backup and recovery. Proper backups are just as important as SOX audit compliance. -- David Portas SQL Server MVP -- What do you mean by compressing the log file,
-- Show quoteCathy B "DBA" wrote: > I have a weird issue. I need to be able to see my transaction log for SOX > reasons. We have purchased Log Explorer from Lumigent to do this. However, on > different databases, we see see differing lengths of data. Some we can see > back several months, while our most important, we can only see a couple of > days. I know that from time to time, SQL will shrink the database, how do I > get it so that it will not truncate the log file, but compress it? Is there a > database property that I need to set or a server setting. Any help would be > greatly appreciated.  
Other interesting topics
|
|||||||||||||||||||||||
