RE: [Emerald] Re: HElp

Darin Spence ( (no email) )
Fri, 4 Jun 1999 02:39:47 -0700

This is the exact error SQL is giving us when we try to save incidents:

SQL Server Error: 1105 Can't allocate space for object 'Incidents' in
database 'Emerald' because the 'default' segment is full. If you ran out of
space in Syslogs, dump the transaction log. Otherwise, State= 1, Severity=
17

^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ Darin Spence
darin@radio-inc.com
Director of Information Technology > R A D I O, INC
(785) 628-1064, ext. 22 > Phone
http://www.media-net.net

> -----Original Message-----
> From: emerald-request@iea-software.com
> [mailto:emerald-request@iea-software.com]On Behalf Of Darin Spence
> Sent: Friday, June 04, 1999 2:39 AM
> To: emerald@iea-software.com
> Subject: RE: [Emerald] Re: HElp
>
>
> Our SQL database is spitting out an error whenever we try to save
> incidents
> saying that we are out of space. How do we increase? We have
> TONS of Hard
> Drive space...
>
> Also, my Application Log keeps filling up with the following error:
>
> Getting this error in my application log in SQL:
> Error: 1105, Severity. 17 State:1
> Can't allocate space for object 'Calls' in database 'Emerald' because the
> 'default' segment is full. If you ran out of space in Syslogs, dump the
> transaction log. Otherwisee, use ALTER DATABASE or sp_extendsegment to
> increate the size of the segment.
>
> What do I do?!?
>
> ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ Darin Spence
> darin@radio-inc.com
> Director of Information Technology > R A D I O, INC
> (785) 628-1064, ext. 22 > Phone
> http://www.media-net.net
>
> > -----Original Message-----
> > From: emerald-request@iea-software.com
> > [mailto:emerald-request@iea-software.com]On Behalf Of Dale E. Reed Jr.
> > Sent: Friday, June 04, 1999 9:26 AM
> > To: emerald@iea-software.com
> > Subject: Re: [Emerald] Re: HElp
> >
> >
> > Darin Spence wrote:
> > >
> > > So before rebooting an SQL server, one should stop the service,
> > then reboot?
> >
> > Under heavy load, SQL Server may not be able to orderly shut down in
> > time before NT says "Die, you, DIE!". In that case, your database will
> > be in a recovery mode when you restart SQL Server. If you manually
> > stop SQL Server before rebooting (and wait for it to stop), then you
> > are guranteed an orderly shutdown and can avoid the recovery issue.
> >
> > --
> >
> > Dale E. Reed Jr. Emerald and RadiusNT
> > __________________________________________
> > IEA Software, Inc. www.iea-software.com
> >
>
>