September 15, 2003 at 1:18 pm
Hi,
I saw few articals about using DBCC Loginfo for SQL Server 7.0 to check log information. I am using SQL Server 2000 and trying to find and learn DBCC Loginfo from BOL, however, it's not documented there.
Can someone tell me how to manage t-logs in SQL Server 2000? I found my 'model', 'ODS', 'SAK' and 'BSC' databases have less than 20% log free space and I wonder what's the best way to manage transaction logs while I have more than 30 databases in the server.
Thanks.
September 15, 2003 at 2:12 pm
Suggest you set your databases transaction log file grow automatically, backup the log regularlly if your databases need to be backed up for up to point-of-time recovery. If there is no such requirement, you could set your database in 'simple' recovery mode.
Because of many databases reside in same machine, you may have to plan which drives the log files go to. All log files go to one drive may affect performance if your databases are busy.
September 15, 2003 at 5:00 pm
If you want to check the available space in the t-logs use,
DBCC SQLPERF(LOGSPACE)
This will tell you the size and the % used.
Other than that, I'd go with Allen's suggestion. Assess what you need for each database and set the options accordingly. You shouldn't need to worry about model though, it should be pretty much static.
Hope this helps
Phill Carter
--------------------
Colt 45 - the original point and click interface
Edited by - phillcart on 09/15/2003 5:05:20 PM
--------------------
Colt 45 - the original point and click interface
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply