Please have a look to our findings of DBCC CHECKDB WITH ESTIMATEONLY:
It will grow (in order to resize the SAN-LUN). These LUN is exact the size of the tempDB (30GB), so before configuring database files of tempDB as autogrowth we have to know how far TempDB is on a separate disk (respectively separated LUN on our SAN), separated from data and logs. What does the number of 140846049001472 indicate ?ĭoes it give hints to us to what size tempDB is to increase ? Could not allocate space for object 'dbo.SORT temporary run storage:ġ40846049001472' in database 'tempdb' because the 'PRIMARY' filegroup is full. The question is: What will be the right size for tempDB to allow DBCC CHECKDB come to an end. There is no doubt about what to do (increase size of tempDB, which has currently a maximal size of 20 GB). Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly." Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth onįor existing files in the filegroup.". Temporary run storage: 140846049001472' in database 'tempdb' because the 'PRIMARY' filegroup is full. Our weekly job for checking integrity of the databases failed the last two runs with message: "Failed:(-1073548784) Executing the query "DBCC CHECKDB WITH NO_INFOMSGS" failed with the following error: "Could not allocate space for object 'dbo.SORT We are running SQL-Server-2005 SP3 (64-Bit) in an Windows-2003-64-Bit-Cluster.
0 kommentar(er)
