Post reply

'PRIMARY' filegroup is full.

  • September 20, 2012 at 8:38 am

    #267036

    Could not allocate space for object 'dbo.cmsPropertyData'.'PK_cmsPropertyData' in database 'HPPortal' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

    This is an error log

    please help me how to resolve

  • September 20, 2012 at 8:42 am

    #1540132

    You will have to do 1 or more of the below

    Drop objects

    Delete data

    Add more drive space

    Enable AutoGrowth if disabled

    Remove unnessesary files from the file system

  • September 20, 2012 at 8:46 am

    #1540135

    anthony.green (9/20/2012)

    You will have to do 1 or more of the below

    Drop objects

    Delete data

    Add more drive space

    Enable AutoGrowth if disabled

    Remove unnessesary files from the file system

    right now i am deleting rows from that table

    should it work?

  • September 20, 2012 at 8:48 am

    #1540138

    yes it will work after the ghost cleanup task has gone in and removed the data but your only buying yourself some time, you will need to get more disk space otherwise you will hit this issue again or setup a archiving routine.

    but have you checked that the data in the table is not needed before deleting it?

  • September 20, 2012 at 9:07 am

    #1540153

    anthony.green (9/20/2012)

    You will have to do 1 or more of the below

    Drop objects

    Delete data

    Add more drive space

    Enable AutoGrowth if disabled

    Remove unnessesary files from the file system

    Or add another file to the group on another volume and disable growth on the existing one.

  • September 20, 2012 at 10:12 am

    #1540217

    anthony.green (9/20/2012)

    yes it will work after the ghost cleanup task has gone in and removed the data but your only buying yourself some time, you will need to get more disk space otherwise you will hit this issue again or setup a archiving routine.

    but have you checked that the data in the table is not needed before deleting it?

    That table has all historic info.

    that table contains all user archive log entries for application. and it will starts from last 2 years. I already put red flag on this issue to my manager 2 months back. but she did not take it on her mine. so today we delete some of historic data for quick fix.

    Now , i think we need to think about better plan, something like need to keep only last 6 months data and we are fine.

    Thanks for Your help.

  • September 20, 2012 at 12:34 pm

    #1540306

    surma.sql (9/20/2012)

    That table has all historic info.

    that table contains all user archive log entries for application. and it will starts from last 2 years. I already put red flag on this issue to my manager 2 months back. but she did not take it on her mine. so today we delete some of historic data for quick fix.

    Now , i think we need to think about better plan, something like need to keep only last 6 months data and we are fine.

    Thanks for Your help.

    Data retention has to be a business decision. Yes, include your manager, but state that "the current system can only hold X months of data, and if more is needed we must"... and lay out options - delete old data, get more storage, export older records and store them in another place, etc.

    Do you have a recent backup in case someone suddenly needs these records?

  • September 20, 2012 at 12:49 pm

    #1540316

    tim_harkin (9/20/2012)

    surma.sql (9/20/2012)

    That table has all historic info.

    that table contains all user archive log entries for application. and it will starts from last 2 years. I already put red flag on this issue to my manager 2 months back. but she did not take it on her mine. so today we delete some of historic data for quick fix.

    Now , i think we need to think about better plan, something like need to keep only last 6 months data and we are fine.

    Thanks for Your help.

    Data retention has to be a business decision. Yes, include your manager, but state that "the current system can only hold X months of data, and if more is needed we must"... and lay out options - delete old data, get more storage, export older records and store them in another place, etc.

    Do you have a recent backup in case someone suddenly needs these records?

    Yes, I schedule backup 3 AM in morning and database down early in the morning somewhat around 9AM. so i did manually backup and then remove rows from that table.

    Right now Production Server is back with this quick fix. but still need to make some plan for future.

    Thanks for reply.

Viewing 8 posts - 1 through 7 (of 7 total)

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