Re: Transaction Log

Josh Hillman ( (no email) )
Wed, 6 May 1998 14:01:38 -0400

Go into SQL Enterprise Manager
Click on the "+" next to your SQL server name.
Right-click on Database Devices and choose New Device.
Name: Emeraldlogs (or whatever you want)
Size: ?? (mine is 25MB but 99% of the time, only about 1MB is
being used because I have the Transaction Log
"truncate on checkpoint" each night at 3:15am when the
database is backed up (diskdump))
Click on Create Now
Click on the "+" next to Databases
Double-click on Emerald
Click on Expand
Data Device: (none)
Log Device: Emeraldlogs (or whatever you named it above)
Size: (same as the value you selected above)
Click on Expand Now
Click on the Options tab.
Check "Truncate Log on Checkpoint" to keep the logs small.
Note: by doing this, you won't be able to backup the
transaction logs when doing a diskdump (backup).
Click Ok.

I don't remember if you have to stop/restart MSSQL service or not.

This will prevent your transaction logs from causing problems with running
out of space for your data.

Josh Hillman

> From: Jeff Cummings <>
> I have a general question about SQL Transaction Logs.
> I'm attempting to do consolidation on about 850,000 call records and I
> continue to get good old error 1105, (transaction log) on my TEMPDB.
> My question pertains to this:
> When I go into the TempDB and click Edit, it shows the Log as (shared
> data)
> Do I need to specifically define a log file for the TempDB? I have a log

> device for my other databases, but I am unclear if TempDB uses the log
> device of the database, or does it require it's own.
> I have run all of the DBCC maintenance I can think of to correct the Log
> devices, and that worked great, but continue to receive Error 1105 on
> Jeff
> _______________________
> Jeff Cummings
> Systems Analyst
> Fox Communications
> ----------------------------------------------------------
> Emerald Mailing List