Originally posted by Coolberg
Set the recovery mode to Bulk-Logged.
(Properties of database, Options tab in Enterprise Mgr)
That doesn't turn the log entirely off, does it? I believe I've tried that and the log still grows.
The thing is that this is a performance issue realy. We are trying to write large amounts of data to our tables in SQL Server and this happens in intervals of 5 sec. It's a single client application and we try to use the bcp utility with the 'xp_cmdshell' stored procedure. I've been tweaking on this for a week now and I think the logs are the bottle-neck.
True, does not turn logging off, don't know if it's possible to turn it off.
Maybe you could reduce the size by backing up the logg and shrinking?
Of course, that would be a big performance issue too...
Do you need to preserve your transaction logs? You can set your recovery model to 'simple', which releases your transaction log. All used space becomes reserved. Then shrink your transaction log, take a full database backup, re-set your recovery model to the desired model and take another full database backup. This is a fairly long process if your database is large, but ensures you won't lose any data as long as you don't delay between the steps.