Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

File group is running out of space Expand / Collapse
Author
Message
Posted Wednesday, April 3, 2013 4:13 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, December 15, 2014 4:05 AM
Points: 173, Visits: 790
Hi,

I am getting below specified running out space alert even autogrowth option is enabled and disk got enough space.

Alert message :'The file group "PRIMARY" for the database "tempdb" in SQL instance "MSSQLSERVER" on computer "XXX" is running out of space.

Tempdb autogrowth option is enabled [500MB, Unrestricted Growth] and Tempdb files disk got 300 Gb free space. present Tempdb size is 55GB.

Please let me know if you need any other details to resolve this / help to resolve this .

Thanks in Advance,
Krishna

Post #1438243
Posted Wednesday, April 3, 2013 4:48 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, November 10, 2014 3:55 AM
Points: 64, Visits: 427
Hi Krishna,

You must be aware that restarting the Sql Server services can free up all the space for tempdb, but this is not a solution for a very busy 24*7 Production Server.

Can you check the recovery model that is set and the result of the below query for your temp db select name,log_reuse_wait,log_reuse_wait_desc from sys.databases where name like 'tempdb' ??
Post #1438253
Posted Wednesday, April 3, 2013 5:26 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, December 15, 2014 4:05 AM
Points: 173, Visits: 790
Thank you for your reply....

Temp DB recovery Model : 'SIMPLE'

log_reuse_wait_desc shows 'ACTIVE_TRANSACTION'

--Krishna
Post #1438266
Posted Wednesday, April 3, 2013 5:37 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 1:14 PM
Points: 40,615, Visits: 37,081
rollercoaster43 (4/3/2013)
Can you check the recovery model that is set and the result of the below query for your temp db select name,log_reuse_wait,log_reuse_wait_desc from sys.databases where name like 'tempdb' ??


Why are you asking for the recovery model (always simple for TempDB) and log reuse reasons when the error says that the *data* file is full, not the log?



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1438271
Posted Wednesday, April 3, 2013 5:37 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 1:14 PM
Points: 40,615, Visits: 37,081
The data file is the one that ran out of space, not the log, so looking at log reuse is a bit of a waste of time. Instead, you need to look at what's using tempDB (not currently, in general) and either tune those queries to not use so much tempDB space or add more space to TempDB (more files or larger file)

I recommend tuning the queries that run so that they use less TempDB space.

p.s. TempDB should not in general be autogrowing. You should be monitoring the space that TempDB uses and have manually set the data files to a size large enough to accommodate regular activity.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1438272
Posted Thursday, April 4, 2013 4:12 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, December 15, 2014 4:05 AM
Points: 173, Visits: 790
Hi Gail Shaw,

Thank you very much your valuable/clear reply.

Issue been resolved by identifying queries causing the growth using these DMV's 'dm_db_session_space_usage', 'dm_db_task_space_usage'.

Thank you,
Krishna
Post #1438708
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse