Could not allocate space for object 'MSmerge_tombstone' in database ' ' because the 'PRIMARY' filegroup is full.

Question

Could not allocate space for object 'MSmerge_tombstone' in database ' ' because the 'PRIMARY' filegroup is full.

dakshinamurthy-655138

SSCertifiable

Points: 5172
More actions
February 26, 2008 at 5:58 am

#74052

Will any one please help me regarding this.
I am getting the following error, while i try to execute a delete query against a table in a database, i have checked the option of auto shrink, simple recovery model, unsrestriced growth and growth of size in terms of MB , even then i am getting the following error please help me
Could not allocate space for object 'MSmerge_tombstone' in database ' ' because the 'PRIMARY' filegroup is full.

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

Carolyn Richardson SSCrazy Eights Points: 8357 More actions · Answer 1

Look at the space on the drive where your PRIMARY filegroup resides, and filespace on drive where the tempdb files reside.

Facts are stubborn things, but statistics are more pliable - Mark Twain
Carolyn
SQLServerSpecialists[/url]

Mh-397891 SSCertifiable Points: 6704 More actions · Answer 2

In the past I had this issue and increasing the space allocated resolved the issue, also check your disk space.

Uncheck AUTOSHRINK! Autoshrink should not be turned on for any production databases, you do'nt want to have perf problems.

SQL ORACLE One Orange Chip Points: 27807 More actions · Answer 3

I agree with others' inputs. You may also check AutoGrowth for databases in this filegroup.

dakshinamurthy-655138 SSCertifiable Points: 5172 More actions · Answer 4

Hi Thanks for the reply, i have checked the option autogrowth, couldnt come out of this error. Few more sugestions or tips please

dakshinamurthy-655138 SSCertifiable Points: 5172 More actions · Answer 5

Hi as per your sugesstion, i checked the space and it is as follows,

Size of HD remaining is 169 GB free and the all the db files stay in the same drive, even after the size free is as mentioned above.

Total Database Size

size 45011.91 MB

Space Avlbl 98.76 MB

.ldf size is 5.44 GB size on disk is 2.45 GB

.mdf file is 38.5 GB size on disk 17.2 GB

dakshinamurthy-655138 SSCertifiable Points: 5172 More actions · Answer 6

Hi thanks for the reply,

Even i checked with increasing the filegrowth size interms of MB , earlier it was 100 MB and i made it to 200 MB even then it is not working. Can i uncheck the check box of auto shrink is it okay to do that.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 7

Check the space available and space on disk for the distribution database.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

dakshinamurthy-655138 SSCertifiable Points: 5172 More actions · Answer 8

Hi,

I checked the space available in the disk for database and it is as follows:

Total Database Size

size 45011.91 MB

Space Avlbl 98.76 MB

.ldf size is 5.44 GB size on disk is 2.45 GB

.mdf file is 38.5 GB size on disk 17.2 GB

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 9

dakshinamurthy (2/26/2008)
Can i uncheck the check box of auto shrink is it okay to do that.

Absolutely. Uncheck it now. Autoshrink should never be enabled on a production server. See here for why - Autoshrink Turn It OFF

Is the distribution db set to auto grow?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

dakshinamurthy-655138 SSCertifiable Points: 5172 More actions · Answer 10

Hi Thanks for the information, i will uncheck the auto-shrink option in the production database and will let you know regarding whether the problem has solved or not. Thanks once again to let me know the reason why we should not check the auto-shrink option.

dakshinamurthy-655138 SSCertifiable Points: 5172 More actions · Answer 11

Hi,

I restarted the SQL server agents and i found the DB is Suspect Mode, so could you let me know how to recover the DB from Suspect mode to normal mode.