msdb database problem with MS SQL Server 6.5

Hi
I have a problem creating a backup in SQL Server 6.5. Although, the
backup produced does restore ok, I want to stop this error message
appearing everytime I make a backup. The error message is:

"
[SQL Server ]Can't allocate space for object 'sysbackupdetail' in
database 'msdb' because the 'default' 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.
"

this articles appears to describe the problem and the solution:

http://support.microsoft.com/defaul...kb;EN-US;152354

It recommends creating a stored procedure to delete old entries. The
stored procedure cannot be created due tro a memory problem. What I
was wondering, although the article doesn't mention it, can a new
device be created and added to the msdb database. This should fix the
problem or is there problems doing this ?

Thanks in advance"John Mullan" <smurf010@.hotmail.com> wrote in message
news:92554ef7.0402040935.6fce79f1@.posting.google.c om...
> Hi
> I have a problem creating a backup in SQL Server 6.5. Although, the
> backup produced does restore ok, I want to stop this error message
> appearing everytime I make a backup. The error message is:
> "
> [SQL Server ]Can't allocate space for object 'sysbackupdetail' in
> database 'msdb' because the 'default' 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.
> "
> this articles appears to describe the problem and the solution:
> http://support.microsoft.com/defaul...kb;EN-US;152354
> It recommends creating a stored procedure to delete old entries. The
> stored procedure cannot be created due tro a memory problem. What I
> was wondering, although the article doesn't mention it, can a new
> device be created and added to the msdb database. This should fix the
> problem or is there problems doing this ?
> Thanks in advance

I think (from memory) SQL6.5 already has a system stored procedure to clean
up the history for you - look for one called sp_purgehistory or something
similar, and check what the code does. Otherwise, extending the device
should work.

Simon