October 25, 2007 at 11:39 am
I have a DB that is in simple mode and the transaction log seems to be growing out of control and I can not find out why. Today I ran DBCC SHRINKFILE ('databasename' , 0, TRUNCATEONLY) and that brought the size down to 1MB but within 2 hours it is back up to 2554MB. Does anyone know of a setting that maybe I overlooked or something I can do to keep the size managable.
October 25, 2007 at 11:51 am
Is there a reindexing/rebuild/shrink operation going on the database?
You can find the current connections using the stored procedure sp_who2.
You can also start a trace with the profiler to monitor the commands that sqlserver is running.
October 27, 2007 at 11:47 pm
Refer the below links, this may help you.
How to avoid using shrink in SQL Server 2005?
Here's a good reason not to run SHRINKDATABASE
Why you want to be restrictive with shrink of database files
Regards..Vidhya Sagar
SQL-Articles
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply