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


Has tempdb grown since the last restart?


Has tempdb grown since the last restart?

Author
Message
Orlando Colamatteo
Orlando Colamatteo
SSC Guru
SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)

Group: General Forum Members
Points: 88124 Visits: 14501
Comments posted to this topic are about the item Has tempdb grown since the last restart?

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
BLOB EATER
BLOB EATER
SSCertifiable
SSCertifiable (7.2K reputation)SSCertifiable (7.2K reputation)SSCertifiable (7.2K reputation)SSCertifiable (7.2K reputation)SSCertifiable (7.2K reputation)SSCertifiable (7.2K reputation)SSCertifiable (7.2K reputation)SSCertifiable (7.2K reputation)

Group: General Forum Members
Points: 7199 Visits: 5100
Can you use Extended Events to track TempDB growth? I have read Jonathan Kehayias's article on tracking database growth, I wonder if that can be applied to tempdb too?

p.s. Nice article, flows and reads well.
dineshvishe
dineshvishe
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1110 Visits: 342
tempdb tempdev N:\Tempdb\tempdb.mdf 446.50 719.19 10% 272.69
tempdb templog N:\Tempdb\templog.ldf 294.38 294.38 50% 0.00
can this data is proper ???
Caruncles
Caruncles
UDP Broadcaster
UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)

Group: General Forum Members
Points: 1483 Visits: 244
Would timing-out errors be a symptom of improper TempDB settings? Especially, during peak times. We are in our busy season right now there is a lot of data entry and updating going on.

Wallace Houston
Sunnyland Farms, Inc.

"We must endeavor to persevere."
james.johnson 22741
james.johnson 22741
SSC Rookie
SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)

Group: General Forum Members
Points: 25 Visits: 8
When I tried to modify the size of the tempdb on my system the results suggested that I was unable to specify the size of something smaller than their current size. A conservative move to make their initial size large, like suggested by the author, would require me to schedule an outage of a production system.
Orlando Colamatteo
Orlando Colamatteo
SSC Guru
SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)

Group: General Forum Members
Points: 88124 Visits: 14501
sql.com (11/20/2012)
Can you use Extended Events to track TempDB growth? I have read Jonathan Kehayias's article on tracking database growth, I wonder if that can be applied to tempdb too?

p.s. Nice article, flows and reads well.

Thanks. I haven't tried it myself but I cannot think of a reason why Extended Events could not be used. I think watching for event sqlserver.databases_log_file_size_changed with filter database_id = 2 so the session only watched tempdb would be where I would begin.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Orlando Colamatteo
Orlando Colamatteo
SSC Guru
SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)

Group: General Forum Members
Points: 88124 Visits: 14501
dineshvishe (11/20/2012)
tempdb tempdev N:\Tempdb\tempdb.mdf 446.50 719.19 10% 272.69
tempdb templog N:\Tempdb\templog.ldf 294.38 294.38 50% 0.00
can this data is proper ???

It seems plausible. It appears tempdev has grown 5 times since the last restart, by 10% each time.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Orlando Colamatteo
Orlando Colamatteo
SSC Guru
SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)

Group: General Forum Members
Points: 88124 Visits: 14501
Caruncles (11/20/2012)
Would timing-out errors be a symptom of improper TempDB settings? Especially, during peak times. We are in our busy season right now there is a lot of data entry and updating going on.

It could, in extreme conditions. I have seen it happen during peak times where the log file was already very large, it was still set at default to grow at 10% and an autogrow was invoked causing the log file to need to grow by many gigabytes. Log files must be zero-initialized and on an already busy I/O subsystem a large autogrow operation can be quite disruptive. What were the results from the query in the article on your system?

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Orlando Colamatteo
Orlando Colamatteo
SSC Guru
SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)

Group: General Forum Members
Points: 88124 Visits: 14501
james.johnson 22741 (11/20/2012)
When I tried to modify the size of the tempdb on my system the results suggested that I was unable to specify the size of something smaller than their current size. A conservative move to make their initial size large, like suggested by the author, would require me to schedule an outage of a production system.

Modifying the size of tempdb to something larger then their current size does not require a restart, i.e. a grow operation will occur immediately upon running the ALTER DATABASE statement. From the error message you posted it sounds as if you are trying to set the value to something smaller than the current size. What were the results of the query in the article on your system and what is the ALTER DATABASE statement you are trying to run?

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Caruncles
Caruncles
UDP Broadcaster
UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)

Group: General Forum Members
Points: 1483 Visits: 244
Here are the results. Looks like quite a difference from the intital settings.
name db_filename
tempdb tempdev
tempdb templog initial_size_MB actual_size_MB auto_grow_setting change_in_MB_since_restart
8.00 541.31 10% 533.31
0.50 74.94 10% 74.44

Wallace Houston
Sunnyland Farms, Inc.

"We must endeavor to persevere."
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