April 30, 2004 at 8:44 am
I'm receiving the following error in the event logs on some of my remote SQL 2000 subscribers, and the replication jobs are failing:
Could not allocate space for object 'blah' in database 'blah' because the 'PRIMARY' filegroup is full.
I know that the disk that the database resides on is not full; it has 205 GB free and the database is 470 GB. The DB is set to auto grow by 300 MB, not by percentage. I am getting this error on the 2 largest tables in the database.
When I execute sp_spaceused on the database, I get a negative number of space available on both the user DB and the distribution/replication DB. The GUI shows 0 MB available, of course.
The backup job from last night failed, but the dump file is on disk, and it is the same size as the active file, so it looks to me like the ump completed successfully.
Suggestions on how to approach this? Should I change the auto grow to a percentage instead of a MB limit?Thanks.
April 30, 2004 at 3:21 pm
Run sp_Helpfile to really know where the data filers are.
Be sure that the disk has enough space for the data files.
Try expanding manually the file/s of the primary file group.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply