Post reply

Could not allocate space for object 'dbo.plan_persist_runtime_stats'.'plan_persist_runtime_stats_cidx' because the 'PRIMARY' filegroup is full.

  • February 13, 2019 at 7:04 am

    #382719

    I'm seeing the following exception in traces: "Could not allocate space for object 'dbo.plan_persist_runtime_stats'.'plan_persist_runtime_stats_cidx' in database 'DBName' 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.".

    What/where is this?  I don't find it in system tables in the specified database or master.  It sounds like an internal table. 
    How can I correct the problem?

    Microsoft SQL Server 2017 (RTM-CU5) (KB4092643) - 14.0.3023.8 (X64)
    There is plenty of space on all drives.  The specified database does not limit growth.

    Thank you.

  • February 13, 2019 at 11:04 am

    #2021955

    RAThor - Wednesday, February 13, 2019 7:04 AM

    I'm seeing the following exception in traces: "Could not allocate space for object 'dbo.plan_persist_runtime_stats'.'plan_persist_runtime_stats_cidx' in database 'DBName' 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.".

    What/where is this?  I don't find it in system tables in the specified database or master.  It sounds like an internal table. 
    How can I correct the problem?

    Microsoft SQL Server 2017 (RTM-CU5) (KB4092643) - 14.0.3023.8 (X64)
    There is plenty of space on all drives.  The specified database does not limit growth.

    Thank you.

    plan_persist_runtime_stats is an internal table added in SQL Server 2014.

    A few things I can think of for the error if you have available space and there is no growth limit -
    If growth is a percentage, it may not have enough space for the growth increment. Or the filegrowth took too long.
    Express edition has size limitations
    If drives are formatted fat32, file size is limited
    The NTFS volume is heavily fragmented

    Sue

Viewing 2 posts - 1 through 1 (of 1 total)

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