Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
tcronines
Starting Member
8 Posts |
 Posted - 2014-06-05 : 09:48:23
|
| supporting 3rd party app, over weekend new patch put in. Performance took a dive, tempdb went from about 8 gig to stuck at 175 gig, any ideas where best place to look might be? |
|
|
James K
Master Smack Fu Yak Hacker
3873 Posts |
Posted - 2014-06-05 : 12:17:24
|
quote:
Originally posted by tcronines
supporting 3rd party app, over weekend new patch put in. Performance took a dive, tempdb went from about 8 gig to stuck at 175 gig, any ideas where best place to look might be?
Not to sound flippant, but the third party software vendor should be called on the carpet for releasing dangerous software on the unsuspecting public.This page might be very useful - there are a number of queries there that let you get some insight into what might be causing the problem. http://msdn.microsoft.com/en-us/library/ms176029.aspxIf their software and usage patterns have not be radically modified in the patch, ask the vendor if they have turned on RCSI on the database with this patch. Version store can sometimes take up a lot of space. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2014-06-05 : 12:46:52
|
| On top of what James said, run a trace/extended event session to capture the long-running queries. If it is due to RCSI, you also need to check for transactions left open too long.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
|
tcronines
Starting Member
8 Posts |
Posted - 2014-06-05 : 16:34:53
|
| may have found culprit sp which called another sp had a table variable created inside of it. Caused 111000 logical reads. Changed their code to use standard temp table insted of table variabel , went to 17 logical reads |
|
|
|
|
|
|
tempdb gone wild