RE: [Emerald] SQL Error 1105

Brad Teague ( )
Thu, 22 Apr 1999 10:14:14 -0500

Hello, I've been having problems with my EmeraldLog filling up
lately. I went to the database the other day and hit "Truncate Log" and it
worked. Well, today it had filled up again and I went to the Database and
hit "Truncate Log" and it wouldn't work. My current log size was 100MB and I
had to expand it to 200 MB just to get Emerald to start working again. No
one was able to create a new user or anything because it couldn't write to
the log I guess. It had obviously halted all such activity. Does anyone know
why my log is filling up so much? and how to manage it? I've worked with IEA
on this once and set all the standard scheduled tasks and what not, but this
is one that they said "they" didn't feel comfortable setting a scheduled
task to delete. From what I've read, i'm assuming it isn't suppposed to fill
up like it is now. It seems to be doing it very quickly and that is nothing
but bad.
The biggest problem is that I can't seem to delete (truncate) the
log now. Any ideas on this anyone?


> -----Original Message-----
> From: Josh Hillman []
> Sent: Thursday, April 22, 1999 9:15 AM
> To:
> Subject: Re: [Emerald] SQL Error 1105
> From: Darren Clissold <>
> I am getting this erro whenever we try to add a user, also call data isn't
> being kept.
> Can't allocate space for object 'syslogs' in database 'emerald' because
> the
> 'log-segment' segment is full.
> If you ran out of space in syslogs, dump the transaction log. Otherwise
> use
> ALTER DATABASE or sp_extend_segment to increase the size of the segment.
> Go into SQL Enterprise Manager.
> Double-click on the Emerald database.
> Click on the Options tab and check the following:
> Select Into / Bulk Copy
> No Checkpoint on Recovery
> Truncate Log on Checkpoint
> Click on the Database tab in the same window.
> Click on Truncate.
> After this is done, you should create a second "device" called
> "EmeraldLogs"
> or something along those lines. If you have a decent amount of drive
> space
> that you can use, allocate at least 35MB. I don't do call consolidations,
> so if you do that, you may need more space.
> Right-click on Database Devices and choose New.
> After the new device has been created:
> Double-click on the Emerald Database.
> Click on Expand.
> Data Device: (none)
> Log Device: EmeraldLogs (or whatever you named it)
> Size: (whatever it defaults to--it should display the size of
> device you just created)
> Click on Expand Now
> Periodically, double-click on the Emerald database in SQL Enterprise
> Manager
> and see what kind of space you have available for the data and the logs.
> Your "Log Space Available" will normally be nearly the amount allocated,
> so
> it'll appear as if it's not even being used much.
> Josh Hillman