SQL Server 2005 transaction log is always too big -


I have read other posts and have done many hours of research but are still not intelligent I have a database which is in the data file 65 gig, and currently there is 230 gig in the log file, I am trying to redesign the database, so it is more efficient, but while making schema changes, the log file becomes very large and it crashes windows That he is out of disk space

I have the file tries to shrink and it is the lowest ~ 220 Gig. Using DBCC Opinion, I can see that there is no active transaction. Using SeS.dm_tran_database_transactions, I can see that there is nothing interesting in it.

The interpretation of what I have read is that the log file should be only grown if there is an active transaction and all the transactions are committed once, the file should be theoretically capable of doing something very small. ?

I have done the backup log truncate_only with dbcc shrinkfile (dbname, 2)

What can I do to make this file more manageable?

Have you read the article of Kimberley Trip? (Very specific prescriptive on this topic):.

You may experience VLF fragmentation:. To find out, run this command:

  DBCC loginFO;  

Did you follow this standard procedure to log in:

1) Back up your transaction logs (even if you are in simple mode) To clear the activity

  for backup log [MyDB] disk = N'E: \ db.bak 'GO  

2) transaction log Go to UEE [MyDebi] Go DBCC SHRINKFILE ('MyDB_Log', TRUNCATEONLY) Go

3) Modify the size of the transfer log and your Configure Autograph:

  USE [My Ibi] Goaltr database [MyDB] modified file (NAME = N'MyDB_Log ', SIZE = 1024000KB, FILEGROWTH = 1024000KB) Go  

Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -