Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mildkiller
Starting Member
1 Post |
 Posted - 2006-08-18 : 14:46:09
|
| Hi gurus,Recently I have a strange problem on my SQL application. It was developed under SQL 2000 and running perfectly. The database was not very big, about 11MB only, but the log was 150MB! The system was a little bit slow, but it was fine for a few months long.I upgraded the system to SQL 2005 and wanna setup database mirror. There's not any adjustment in the application, only change the recovery model from Simple to Full, because the Full recovery model is required by database mirror. I shrink the log to 81KB, but it's growing bigger and bigger so fast, 3-4 days later it will be 1MB. In the meantime, the system is slower and slower, at last, the system will be frequently time out and lose transaction data!! I have to shrink the log smaller, and the system will be fast again.I did setup auto shrink as True. No help. Do I need any other configuration on SQL 2005? The log keep going bigger and making system slower when it is in full recovery model, any possible bug in SQL application? It is fine in Simple model.Please advise me.Thanks.MK |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-08-18 : 14:55:19
|
| The log growing will not impact performance until you run out of disk space. Also, you will not lose transaction data either. You need to start backing up the transaction log since your database recovery model is set to FULL. This is not a bug.Tara Kizer |
 |
|
|
|
|
|
|
|
full recovery model and database mirror - SQL 2005