SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


File group is running out of space


File group is running out of space

Author
Message
krishnaprasad14
krishnaprasad14
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1173 Visits: 1043
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
rollercoaster43
rollercoaster43
SSC-Addicted
SSC-Addicted (407 reputation)SSC-Addicted (407 reputation)SSC-Addicted (407 reputation)SSC-Addicted (407 reputation)SSC-Addicted (407 reputation)SSC-Addicted (407 reputation)SSC-Addicted (407 reputation)SSC-Addicted (407 reputation)

Group: General Forum Members
Points: 407 Visits: 435
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' ??
krishnaprasad14
krishnaprasad14
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1173 Visits: 1043
Thank you for your reply....

Temp DB recovery Model : 'SIMPLE'

log_reuse_wait_desc shows 'ACTIVE_TRANSACTION'

--Krishna
GilaMonster
GilaMonster
SSC Guru
SSC Guru (370K reputation)SSC Guru (370K reputation)SSC Guru (370K reputation)SSC Guru (370K reputation)SSC Guru (370K reputation)SSC Guru (370K reputation)SSC Guru (370K reputation)SSC Guru (370K reputation)

Group: General Forum Members
Points: 370978 Visits: 46966
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, 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


GilaMonster
GilaMonster
SSC Guru
SSC Guru (370K reputation)SSC Guru (370K reputation)SSC Guru (370K reputation)SSC Guru (370K reputation)SSC Guru (370K reputation)SSC Guru (370K reputation)SSC Guru (370K reputation)SSC Guru (370K reputation)

Group: General Forum Members
Points: 370978 Visits: 46966
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, 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


krishnaprasad14
krishnaprasad14
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1173 Visits: 1043
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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search