Post reply

'PRIMARY' filegroup is full

  • September 12, 2011 at 1:40 pm

    #1380295

    Krasavita (9/12/2011)

    So I will change

    1.FileGrowth in Megabytes from 500 to 1024 primary

    (2.FileGrowth in Megabytes from 100 to 500 filegroup=datafile2

    3.FileGrowth in Megabytes from 100 to 500 (enable autogroth is checked)filegroup=docs

    4.FileGrowth in Megabytes from 100 to 500 filegroup=indexes

    5.FileGrowth in Megabytes from 100 to 500 filegroup=userdata1

    Is this correct?

    Also my log file is 2,001 MB and is set to restricted growth to 2,097,152 mb and file growth is set 100 MB, should I change it?

    Are any of your data files set to "restricted" like your log file is ?

    130,209 GB .... Maybe meant to be 130.2 GB ?

  • September 12, 2011 at 2:10 pm

    #1380308

    LOGFILe is set to restricted and databases size is 134210.00 MB and available 1192.73 MB

  • September 12, 2011 at 2:27 pm

    #1380319

    Are any of your data files set to "restricted" like your log file is ?

  • September 12, 2011 at 2:34 pm

    #1380323

    Note that the restriction on the log file is actually not a restriction. It's 2048 TB, the maximum allowable size for a log file ever.

    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

  • September 12, 2011 at 2:41 pm

    #1380326

    No I don't have other files restricted

  • September 12, 2011 at 2:57 pm

    #1380330

    GilaMonster (9/12/2011)

    Note that the restriction on the log file is actually not a restriction. It's 2048 TB, the maximum allowable size for a log file ever.

    oops ... good catch

    So, if no files are restricted, all have autogrow and there's 200 G free on the drive, what is the cause of the error ?

  • September 12, 2011 at 3:02 pm

    #1380332

    Autogrow timeout maybe (it'll be in the error log) or autogrow took too long, query that needed space failed and rolled back.

    Autogrow's not something that should be relied on for database growth. File grows should be done manually based on data growth and need, autogrow should just be there for the cases where the DBA stuffs up and doesn't grow the file in time.

    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

Viewing 7 posts - 16 through 21 (of 21 total)

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