I am a little confused. We have a 3.3GB database and it is only 2.9GB full. I have the properties on the database set to grow but I restrict file growth to 3.5GB.
While running our weekly DB Maintenance job to rebuild indexes I got the following error:
*** [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1105: [Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object 'gltrxdet' in database because the 'PRIMARY' filegroup is full. ***
It appears that while running this job it tried to use more than the 3.5GB that I have restricted the database to. The drive that the primary filegroup is on has about 10GB available so the drive itself didn't run out of disk space. So, to hopefully resolve the situation, I have expanded the database to 5GB since there is plenty of room on the drive and I will try to re-run the job again tonight.
Does it make sense that so much space is used while rebuilding indexes on a database?
Thanks in advance,
Bessebo
While running our weekly DB Maintenance job to rebuild indexes I got the following error:
*** [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1105: [Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object 'gltrxdet' in database because the 'PRIMARY' filegroup is full. ***
It appears that while running this job it tried to use more than the 3.5GB that I have restricted the database to. The drive that the primary filegroup is on has about 10GB available so the drive itself didn't run out of disk space. So, to hopefully resolve the situation, I have expanded the database to 5GB since there is plenty of room on the drive and I will try to re-run the job again tonight.
Does it make sense that so much space is used while rebuilding indexes on a database?
Thanks in advance,
Bessebo