Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can't allocate space for object 'sysprocedures' in database

Status
Not open for further replies.

seosamh

Programmer
Aug 2, 2000
29
IE
I got a copy of a client's database and having done an object transfer so as to make it work on my server I discovered that only one stored procedure was copied. I scripted their sp's and tried to run these but was confronted with a massive list of
"Msg 1105, Level 17, State 1
Can't allocate space for object 'sysprocedures' in database 'XXX' because the 'system' 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.

I tried DUMP TRANSACTION 'database' with no_log, but this had no effect. I also increased the size of the log and data files but that did not help either.

What am I doing wrong?
 
What it is is that your device has run out of space. Consider expanding it. If you are using sql7, you may have created the database without autoexpand, so exppand the database. But it sounds as if you are using sql 6.5
 
There is a bug where the dump doesn't always work the first time. If you run the DUMP, then DBCC CHECKDB, then the DUMP again, it should work and clear the TempDB.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top