February 3, 2004 at 10:15 am
I ran a number of DTS text imports (large files) on my home system. Later I wanted to move the database to another server so I detached it but received an error saying that the trans log was full. I checked -- the trans log is set to autogrow, I had 20GB free on drive C (FAT32), and the trans log was about 3.8GB in size. How could it be full?
TIA,
Bill
February 3, 2004 at 10:31 am
I believe that growth is a logged event and if the log is full, then you need to clear space before it can grow. Running a "backup transaction with no_log" will get you space. Then run a full backup before you do anything.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
February 3, 2004 at 11:11 am
A growth event is not logged, it used to be that way in SQL 6.5. You can sometimes get this error when your process is moving faster than your disks as they allocate new space. You might look into increasing the growth increment of your tran log, this can be true in the tempdb as well if you are doing some heavy lifting (querying/thinking)
As Steve said, doing the no_log will truncate all inactive transactions in the log, you can then run dbcc shrinkfile on the log to decrease the footprint. If you do not require point in time recovery on this db, I reccomend setting it to simple recov mode.
HTH
------------
Ray Higdon MCSE, MCDBA, CCNA
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply