Are your data and logs shared? (using the same device)
If they're separate and there's 130/150 MB being used in the log device,
then chances are, there's something running in the background (or was at the
time) that was processing a ton of data (Calls??) in one big chunk and
that's why it got so big. If you have "Truncate Log on Checkpoint" checked
in the options, then this should clear itself out when SQL verifies that it
processed the information correctly (usually, right after it finished
processing).
Josh
*********** REPLY SEPARATOR ***********
On 9/30/99, at 11:17 AM, Josh Hillman wrote:
>From: PowerNet <psc5@powersupply.net>
>When I click on truncate I get the message to immediately do a database
>dump.
>Is that what we are doing in this second procedure you sent?
>
>
>You can do the diskdump afterward if you want. It can't hurt--it's just a
>backup. The diskdump that it wants you to do isn't really directly related
>to anything else I mentioned. SQL just wants you to do it as a saftey
>measure. I have nightly scheduled tasks that run my diskdumps (unrelated
to
>the one you mentioned).
>
>Josh
>
>
>*********** REPLY SEPARATOR ***********
>
>On 9/30/99, at 10:54 AM, Josh Hillman wrote:
>
>>> From: PowerNet <psc5@powersupply.net>
>>> Msg 1105, Level 17, State 2
>>> Can't allocate space for object 'Syslogs' in database 'Emerald' because
>>the
>>> 'logsegment' segment is full. If you ran out of space in Syslogs, dump
>the
>>> transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>>> increase the size of the segment.
>>> Msg 1105, Level 17, State 2
>>> Can't allocate space for object 'Syslogs' in database 'Emerald' because
>>the
>>> 'logsegment' segment is full. If you ran out of space in Syslogs, dump
>the
>>> transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
>>> increase the size of the segment.
>>>
>>From: Josh Hillman <admin-maillist@talstar.com>
>>> Go into SQL enterprise manager
>>> find the Emerald database and double-click on it.
>>> Click on Truncate Log.
>>>
>>> I'll send other suggestions for what to do after this in a few minutes.
>>
>>Here's part 2, from a message I sent to the list sometime last year:
>>
>>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 35MB 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
>>
>>
>>For more information about this list (including removal) go to:
>>http://www.iea-software.com/support/maillists/liststart
>
>For more information about this list (including removal) go to:
>http://www.iea-software.com/support/maillists/liststart
>
>
>
>For more information about this list (including removal) go to:
>http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart