> For an object database of 100mb in size the transaction log > was 728mb, and filled the disk nearly completely (shared sql > server). > > Also a truncate and then DBCC shrinkfile does not reduce the > size of the transaction log, which indicates uncommitted > transactions (I think). > > Has anybody experienced this? > I am wondering if it is a spectra issue or some other rogue > code that I'm still to uncover.
This isn't out of the ordinary behavior with SQL Server 7 or higher, if you don't set up a maintenance plan for your database, or you don't enable the "truncate log on checkpoint" option (which you typically don't want to do on a production database). It doesn't have anything to do with Spectra, specifically, either, I don't think. When you run DBCC SHRINKFILE after truncating the log, you may not be able to reduce the size of the log file without running BACKUP LOG first. The discussion of this topic in SQL Server Books Online is a bit complex, so you might want to take a look at that. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. ------------------------------------------------------------------------------ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
