May 4, 2006 at 1:50 pm
Question 1: I have an application that has a database that is 2,053,000 KB in size. I copied it over to a test machine, truncated the audit file, and its size dropped to 729,536. The audit file is pretty much useless.
Obviously smaller is better, and I'm thinking 2 gigs isn't that big for SQL Server ... but can someone with SQL knowledge comment on this. What benefits, considerations, etc would one expect having a significantly smaller database?
Question 2: There are a lot of test databases with a lot of data on this machine. My guess is there is 10 to 15 gigs of data in databases that are not used (old test stuff, etc). I'm not sure of the right questions to ask, but how much does having these large files hurt?
Thanks!!!!
May 5, 2006 at 6:02 am
An audit file indicate that c2 audit mode (a security setting I would guess is not used much) is enabled. If it's not required, you can turn it off with these statements:
USE master
EXEC sp_configure 'show advanced option', '1'
RECONFIGURE
EXEC sp_configure 'c2 audit mode', 0
RECONFIGURE
Those size database files don't hurt, other than to waste space if they are no longer needed. Of course, a lot of databases could slow SQL Server during startup, as it has to recover each one.
You might want to consider detaching some of the databases and see if it causes a problems or complaints from users. If not the files could be deleted at a later date. Another thing to do would be to back up the databases to disk, and then burn them to CD or DVD. I would personally hate to delete a database that was needed without having a backup.
May 5, 2006 at 7:17 am
The size of database really depends on what edition of SQL Server you are using. Some editions only allow 2 GB for the database. I currently have 207 GB using SQL Server 2000 Enterprise Edition.
-SQLBill
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply