Viewing 15 posts - 9,301 through 9,315 (of 22,224 total)
prabhu.st (12/11/2013)
Hi G.F,yes,
it works as Charm..
Thanks,
Prabhu
Which, the cost threshold change?
"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
December 11, 2013 at 6:02 am
Obviously you're getting two different plans with two different execution times. I'd say the principal difference is in the hash keys residual that adds the CustomerSets data to the combined...
"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
December 11, 2013 at 5:20 am
GilaMonster (12/11/2013)
That's a formatting issue that should be dealt with in whatever application is reading this data.
Absolutely!
"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
December 11, 2013 at 5:06 am
yayomayn (12/11/2013)
Grant Fritchey (12/11/2013)
"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
December 11, 2013 at 4:06 am
If you understand that NUMERIC is a precision and then a scale, then you'd know that you need NUMERIC(10,5). Read up on it here. I'd also suggest, instead of NUMERIC,...
"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
December 11, 2013 at 3:49 am
It's probably your code, or your statistics, or the lack of an index. Those are much more likely than fundamental memory issues, but they can all lead to memory issues....
"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
December 11, 2013 at 3:46 am
Without seeing the execution plan I couldn't say for sure, but I'll bet the plan for the statement without the CASE is more accurate to your indexes and statistics while...
"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
December 11, 2013 at 3:41 am
What does the error log of the system being shut down say? Are there any entries in the Windows logs suggesting possible problems?
"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
December 11, 2013 at 3:37 am
Unless you've set up extended events (or a server-side trace) to capture that type of information, there's no way to get it just by querying SQL Server. It's not stored...
"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
December 11, 2013 at 3:35 am
PravB4u (12/10/2013)
as mentioned by Grant, parameter sniffing does make you query slow. I personally experienced it.go through below article.
http://blogs.technet.com/b/mdegre/archive/2012/03/19/what-is-parameter-sniffing.aspx
Be careful with statements like that. Parameter sniffing is an automatic process...
"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
December 10, 2013 at 5:47 am
Different servers makes it more difficult. In order to use a trigger you'd have to use a linked server. It sounds less viable now than it did. The different 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
December 10, 2013 at 5:45 am
Sounds like a situation that will be answered by a trigger. You can do a cross database query pretty easily if they're on the same server.
"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
December 10, 2013 at 4:29 am
Primarily as a measure of load you can look at page faults/sec. That will tell you how many times SQL Server had to go looking for pages within memory. 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
December 10, 2013 at 3:24 am
Shortest answer I can give you, start with a place that reasonably well known and legit. You're just getting started as an author. That means you're going to have to...
"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
December 9, 2013 at 12:47 pm
Another set of mechanisms for getting versioned data (the latest) are illustrated in this article[/url] I wrote for Simple-Talk.
"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
December 9, 2013 at 12:34 pm
Viewing 15 posts - 9,301 through 9,315 (of 22,224 total)