Viewing 15 posts - 6,256 through 6,270 (of 22,219 total)
Stephanie Giovannini (4/24/2015)
Suppose my table looks like...
"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
April 24, 2015 at 10:33 am
Why 100K rows? Is it an export? If it's not an export of data, 100K is not a reasonable number of standard evaluations.
"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
April 24, 2015 at 10:21 am
Then you might be running into resource issues, not enough memory, possibly contention in tempdb, the log file was growing over and over? Something along those lines.
"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
April 24, 2015 at 7:08 am
You could set up a trigger to capture inserts. That might cause some performance hits though. You could capture queries using extended events and sort out the INSERT statements. It...
"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
April 24, 2015 at 6:34 am
200 million rows isn't really that big and that's a long time for an index to run. I suspect you may have been experiencing blocking. The thing to do would...
"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
April 24, 2015 at 6:30 am
For an insert query, those are the full results. You're seeing exactly what you should. You inserted a row. It was completed successfully. An insert doesn't return data.
"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
April 24, 2015 at 6:28 am
The thing to do might be to hire a consultant to do the job description and the interviews for you. As Jeff says, you've split the difference between a BI...
"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
April 24, 2015 at 6:22 am
I've seen a 5 minute compile time on queries, so they can run for a very long time indeed. If you're looking at the plan, you can see the compile...
"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
April 24, 2015 at 6:15 am
Sounds great. Nicely done.
"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
April 23, 2015 at 10:09 am
Nesting views is a really common code smell and should be avoided. It's best to write each query as a stand-alone entity and not attempt code reuse through views or...
"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
April 22, 2015 at 2:14 pm
aaron.reese (4/21/2015)
They also have a data compare so that you can script config and static data
Their tools also integrate very nicely into SSMS and SQL compare can handle...
"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
April 21, 2015 at 11:09 am
More reasons why system_health is better.
"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
April 21, 2015 at 9:00 am
Your best bet if you want to capture parameters is to use Extended Events[/url]. You can't capture parameter values querying the cache.
For lost more on query tuning, see the books...
"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
April 21, 2015 at 6:44 am
I would absolutely advocate for using the mathematical calculations supplied by Microsoft in the link above. But, for a ballpark guess when doing initial evaluations, 3-5 times the data 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
April 20, 2015 at 9:18 am
SQLRNNR (4/19/2015)
Eirikur Eiriksson (4/19/2015)
Grant Fritchey (4/19/2015)
Eirikur Eiriksson (4/19/2015)
spaghettidba (4/19/2015)
"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
April 20, 2015 at 6:30 am
Viewing 15 posts - 6,256 through 6,270 (of 22,219 total)