<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Administering
»
Process not releasing tempdb space
Process not releasing tempdb space
Rate Topic
Display Mode
Topic Options
Author
Message
curious_sqldba
curious_sqldba
Posted Monday, October 22, 2012 3:57 PM
Ten Centuries
Group: General Forum Members
Last Login: Yesterday @ 8:11 PM
Points: 1,172,
Visits: 2,686
Any suggestions on how to check why tempdb space is NOT being released?
Post #1375763
Vegard Hagen
Vegard Hagen
Posted Monday, October 22, 2012 4:04 PM
SSC-Addicted
Group: General Forum Members
Last Login: Sunday, May 12, 2013 11:41 PM
Points: 494,
Visits: 325
Most likely you've come across a piece of bad application code that doesn't clean up after itself.
All temporary objects created in tempdb must be
dropped
when you're done with them.
You can check this by running a trace and looking at the actual SQL code. Anything that's created and not dropped at the end of a transaction is part of the problem.
Vegard Hagen
Norwegian DBA, blogger and generally a nice guy who believes the world is big enough for all of us.
@vegard_hagen on Twitter
Blog: Vegard's corner
(No actual SQL stuff here - haven't found my niche yet. Maybe some day...)
"It is better to light a candle than to curse the darkness."
(Chinese proverb)
Post #1375767
curious_sqldba
curious_sqldba
Posted Monday, October 22, 2012 9:47 PM
Ten Centuries
Group: General Forum Members
Last Login: Yesterday @ 8:11 PM
Points: 1,172,
Visits: 2,686
Vegard Hagen (10/22/2012)
Most likely you've come across a piece of bad application code that doesn't clean up after itself.
All temporary objects created in tempdb must be
dropped
when you're done with them.
You can check this by running a trace and looking at the actual SQL code. Anything that's created and not dropped at the end of a transaction is part of the problem.
So within a stored procedure, if i am creating any temp tables they should also be dropped? My understanding was temp tables are dropped after the session is completed?
Post #1375813
SQLRNNR
SQLRNNR
Posted Monday, October 22, 2012 10:32 PM
SSCoach
Group: General Forum Members
Last Login: Yesterday @ 1:07 PM
Points: 18,733,
Visits: 12,332
sqldba_newbie (10/22/2012)
Vegard Hagen (10/22/2012)
Most likely you've come across a piece of bad application code that doesn't clean up after itself.
All temporary objects created in tempdb must be
dropped
when you're done with them.
You can check this by running a trace and looking at the actual SQL code. Anything that's created and not dropped at the end of a transaction is part of the problem.
So within a stored procedure, if i am creating any temp tables they should also be dropped? My understanding was temp tables are dropped after the session is completed?
In many cases that is true. Sometimes the temp table will not clean up after the session is closed. It is typically good practice to clean up these objects - it's only an extra line of code.
That said, what do you mean by tempdb space not being released?
Do you mean that tempdb data files and log file are full and the space is not being released internally or do you mean that tempdb is not shrinking and releasing space to the OS?
Jason
AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server 2008
SQL RNNR
Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #1375820
curious_sqldba
curious_sqldba
Posted Tuesday, October 23, 2012 6:32 PM
Ten Centuries
Group: General Forum Members
Last Login: Yesterday @ 8:11 PM
Points: 1,172,
Visits: 2,686
SQLRNNR (10/22/2012)
sqldba_newbie (10/22/2012)
Vegard Hagen (10/22/2012)
Most likely you've come across a piece of bad application code that doesn't clean up after itself.
All temporary objects created in tempdb must be
dropped
when you're done with them.
You can check this by running a trace and looking at the actual SQL code. Anything that's created and not dropped at the end of a transaction is part of the problem.
So within a stored procedure, if i am creating any temp tables they should also be dropped? My understanding was temp tables are dropped after the session is completed?
In many cases that is true. Sometimes the temp table will not clean up after the session is closed. It is typically good practice to clean up these objects - it's only an extra line of code.
That said, what do you mean by tempdb space not being released?
Do you mean that tempdb data files and log file are full and the space is not being released internally or do you mean that tempdb is not shrinking and releasing space to the OS?
tempdb data files and log file are full and the space is not being released internally
Post #1376289
SQLRNNR
SQLRNNR
Posted Tuesday, October 23, 2012 8:24 PM
SSCoach
Group: General Forum Members
Last Login: Yesterday @ 1:07 PM
Points: 18,733,
Visits: 12,332
sqldba_newbie (10/23/2012)
SQLRNNR (10/22/2012)
sqldba_newbie (10/22/2012)
Vegard Hagen (10/22/2012)
Most likely you've come across a piece of bad application code that doesn't clean up after itself.
All temporary objects created in tempdb must be
dropped
when you're done with them.
You can check this by running a trace and looking at the actual SQL code. Anything that's created and not dropped at the end of a transaction is part of the problem.
So within a stored procedure, if i am creating any temp tables they should also be dropped? My understanding was temp tables are dropped after the session is completed?
In many cases that is true. Sometimes the temp table will not clean up after the session is closed. It is typically good practice to clean up these objects - it's only an extra line of code.
That said, what do you mean by tempdb space not being released?
Do you mean that tempdb data files and log file are full and the space is not being released internally or do you mean that tempdb is not shrinking and releasing space to the OS?
tempdb data files and log file are full and the space is not being released internally
Ok. So you will need to find what long running queries are consuming the space and holding onto the objects in tempdb.
Jason
AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server 2008
SQL RNNR
Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #1376300
Noetic DBA
Noetic DBA
Posted Wednesday, October 24, 2012 3:33 PM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Thursday, May 16, 2013 7:14 AM
Points: 117,
Visits: 184
I work with several PowerBuilder developers and have the same issue. It is generally an open transaction on the tempdb. Tempdb will usually check point after I kill the open tran. I also use this script to quickly check free space.
use tempdb
DBCC OPENTRAN
use tempdb
SELECT DB_NAME() AS DbName,
name AS FileName,
size/128.0 AS CurrentSizeMB,
size/128.0 - CAST(FILEPROPERTY(name, 'SpaceUsed') AS INT)/128.0 AS FreeSpaceMB
FROM sys.database_files;
Post #1376698
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
