Viewing 15 posts - 8,836 through 8,850 (of 22,219 total)
RonKyle (2/25/2014)
"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
February 25, 2014 at 9:48 am
Yep. Those are the kind that I'd replace with some kind of parameterized query.
If you can't for some reason, then optimize for ad hoc, absolutely, and, possibly, forced parameterization. That...
"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
February 25, 2014 at 8:18 am
Or any integrity issues get introduced by the restore process, which can happen. I wouldn't do it that way. Paranoia runs way too deep.
"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
February 25, 2014 at 8:16 am
That's kind of nuts. I wouldn't even bother with log backups there. Just have the daily one since it's extremely likely you'll only ever be able to go to the...
"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
February 25, 2014 at 8:15 am
quackhandle1975 (2/25/2014)
SQL2008R2? Are you in correct forum?Rgds,
qh
+Infinity
You're much more likely to get a lot more help posting in the 2008 forum rather than the 2014 forum.
"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
February 25, 2014 at 8:10 am
And for the sake of clarity, comparing a "query" to a view is something of a misnomer. They're both queries. A view is nothing but a packaged query. When you...
"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
February 25, 2014 at 8:09 am
And if you don't want to or can't run sp_whoisactive, I would suggest getting familiar with the Dynamic Management Objects and run queries against them rather than using sp_who2. That's...
"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
February 25, 2014 at 8:07 am
Yeah, but it'll hit CPU and memory, not IO.
The question is, are all the queries the same, but varying by some parameter value? If so, then optimize for ad hoc...
"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
February 25, 2014 at 8:06 am
In general, you're going to have a hard time quantifying this precisely. The issue is that you're relying on one of two pieces of information, the login and the application...
"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
February 25, 2014 at 8:02 am
Ow!
Dry? Now way! I love it. Can't get enough. If you want a quick hit on what to look for in plans, I've got a short list here.[/url]
"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
February 25, 2014 at 7:12 am
OldCursor (2/25/2014)
"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
February 25, 2014 at 6:41 am
Nice article.
A couple of notes. You state that the plan is read from right to left. That's not completely true. The logical processing order of the plan is from left...
"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
February 25, 2014 at 6:39 am
That vendor needs to be burned at the stake.
And then we'll scatter the ashes at a cross-roads.
And then sow the ground with salt.
Although, I've seen scarier stuff generated by ORM...
"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
February 25, 2014 at 4:58 am
You have to restore with RECOVERY at the end of the log process too.
Looking at that, are they running a single log backup? Normally you'll see lots of log backups...
"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
February 25, 2014 at 4:55 am
Then you're stuck. You're trying to compare two different data types. SQL Server has to convert them in order to compare them. No choice there. To get index use assured,...
"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
February 25, 2014 at 4:52 am
Viewing 15 posts - 8,836 through 8,850 (of 22,219 total)