Post reply

Could not allocate space for object, the ''PRIMARY'' filegroup is full.

  • December 6, 2005 at 3:41 am

    #110955

    SQL 2000 SP4

    EventID 17052:

    Error: 1105, Severity: 17, State: 2

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

    The main database has 0.00Mb free, I suspect I'll have to manually increase the size of the database from Enterprise Manager, properties of DB, DataFile tab. However the database is configured to automatically grow the database size by 10%, has unrestricted file growth selected and disk space is aplenty.. Interestingly the none selected "greyed out radio button" for restricted file growth, I can see was set to 97Mb, the database has hit around this size. Is it possible it's not taken the selected option, or maybe SP4 (installed approx 1 month ago) might have a bug?

    Does anyone have any recommendations / ideas why auto growth is not working? Is a manual increase in size recomended....?

    Many thanks.

    Mike.

  • December 6, 2005 at 6:02 am

    #607906

    Can you add another file into the same filegroup.

    I have installed sp4 almost immediately after installation, and I dont have any issues like this.

    BTW,  do u have full access rights to the DB

     

    Cheers,
    Prithiviraj Kulasingham

    http://preethiviraj.blogspot.com/

  • December 6, 2005 at 7:55 am

    #607937

    It's possible there is a bug, but this would be the first I heard of it. I would manually grow the file and see if that works. Perhaps in the middle of some large transaction you ran out of space.

    How large is the db and how much disk space is free?

  • December 6, 2005 at 8:03 am

    #607941

    Thanks for the replies, the database is 99.1 MB with approx 23GB of free disk space.

    Thanks.

    Mike

  • June 21, 2006 at 7:22 am

    #645009

    I have been experiencing this problem on a couple of servers that have SQL Server 2000 SP4 installed.  There appears to be plenty of space on the drive and auto grow is enabled.  When I rerun the job it works fine.

    So any ideas why isn't the auto grow process being triggered when the primary group is full? 

    I would hope the auto growth process is triggered before the file runs out of space so the transaction does not have to wait for its completion.

     

    David Bird

  • July 24, 2006 at 11:38 pm

    #651253

    Hi David,

    Any breakthrough?? as I am also facing the same problem for one of my database.

  • July 25, 2006 at 6:47 am

    #651313

    Hi, Apologises for the delay in replying!

    Unfortunately, it was so long ago when I had this issue I cannot recall the full story of how I cured it !!!

    I suspect I manually adjusted it. We do have maintenance plans running on our databases now and I suspect that is also helping us!

    Not much use, sorry!

    Thanks.

    Mike

  • October 9, 2007 at 4:01 am

    #740276

    In this case it should be a log file full.When i had the same issue i shrink the log file and ran the below script to increase the database allocated space and then it worked try this it may be helpfull.

    Alter database techtesting

    modify file

    (Name = DB_data,

    size = 10MB)

    Go

    Alter database DB

    Add file

    (

    Name = DB_data_1,

    Filename = 'Location of the MDF file',

    size = 50MB

    MAXSIZE = 100MB,

    FILEGROWTH = 5MB

    GO

  • August 17, 2010 at 8:43 pm

    #1208246

    Hi,

    Did you try to Empty the file by using the dbcc shrinkfile(4,emptyfile)?

  • March 9, 2012 at 12:32 pm

    #1457354

    There is no room for work-around here. You must allocate more disk space by hook or by crook or your server will remain down.

    Jamie

Viewing 10 posts - 1 through 9 (of 9 total)

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