Viewing 15 posts - 4,936 through 4,950 (of 22,219 total)
Yeah, only the compile values will ever be in cache. If you need the run-time values, you have to capture them using some mechanism.
Extended Events are much safer than trace...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 24, 2016 at 12:10 pm
Steve Jones - SSC Editor (3/24/2016)
WayneS (3/24/2016)
ChrisM@Work (3/24/2016)
Stage fright can hit anyone I suppose.
Yes it does... even those that speak frequently. I know of a fellow threadizen that is...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 24, 2016 at 10:12 am
But, but, but, we've ALWAYS done it that way.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 24, 2016 at 9:09 am
There's nothing wrong with triggers... used appropriately. Same thing goes for just about every other object within SQL Server (except multi-statement table-valued user-defined functions, those things are pure EVIL and...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 24, 2016 at 9:08 am
With the execution plan it'll be easier, but just looking at the query and the indexes, it can't use any of those indexes because the WHERE clause filters on Invalid...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 24, 2016 at 9:04 am
The query that was used to generate the execution plan is stored with the plan. So getting a runnable query is just a matter of retrieving that information. Same thing...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 24, 2016 at 9:00 am
But, something you've done or are doing on your server has grown the tempdb out to this size. Unless you know for certain what that was and that it won't...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 24, 2016 at 8:56 am
Post the execution plan and additional suggestions might come up. But that's a very good suggestion you already have from Chris.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 24, 2016 at 8:54 am
Alexander Suprun (3/23/2016)
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 24, 2016 at 4:33 am
Hugo Kornelis (3/23/2016)
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 24, 2016 at 4:28 am
I still don't understand the question. A nonclustered index is sorted. It has a key value. It gets sorted into a b+tree by that key value. The keys are ordered...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 23, 2016 at 11:06 am
The descriptions for those are here. For the most part, most people don't bother with putting backups into a set that way. Instead, most of the time, people will initialize...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 23, 2016 at 10:05 am
To see recent queries against a table, you can search sys.dm_exec_query_stats in combination with sys.dm_exec_sql_text. It will have the queries that are currently in cache. That should cover most of...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 23, 2016 at 10:00 am
Happy to help out. I'm rewriting the execution plans book. It should be done soon I hope.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 23, 2016 at 8:43 am
Right. Not a backup. That wouldn't work. BCP a SELECT statement against the cache using the DMVs.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 23, 2016 at 8:30 am
Viewing 15 posts - 4,936 through 4,950 (of 22,219 total)