But I don't WANT a transaction log!!

[RRinTetons]

I have some lengthy scripts (vendor-supplied) that I need to run as part of a database conversion from SQL Server 2000 to SQL Server 2005. I created the new 2005 database and set the Recovery Model option to Simple with the goal of not logging all the updates the script would perform.

It doesn't seem to have worked. I have a log, and it's outgrown the log volume and the script failed.

How can I get SQL Server 2005 to run this script without logging?

-
Richard Ray
Jackson Hole Mountain Resort

 

[mrdenny]

There is no way to run commands on a SQL Server database without logging. You'll need to either increase the size of the transaction log, or run the update is smaller batches.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[RRinTetons]

Hmph.

Easy. Not what I wanted, but easy enough. Thanks.

-
Richard Ray
Jackson Hole Mountain Resort

 

[JayKusch]

Also, if your current Tlog file (LDF) is on a small drive and you have another larger disc in the server, you could try detaching and reattaching just the log file to the larger drive.

Then run your process, shrink the tlog back down and after the process and then move (detach/reattacjh) the LDF back to its original location/disc.

Maybe this would give you a temporary fix of the log outgrwoing its current volume.

Thanks

J. Kusch