Viewing 15 posts - 8,986 through 9,000 (of 22,224 total)
That's also going to result in a scan because a leading edge wild card can't use an index key.
"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 3, 2014 at 11:32 am
My first thought is that you had a different plan in the cache and making the affinity change causes a recompile which helped the issue.
But... I'm not sure about 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 3, 2014 at 11:28 am
wolfkillj (2/3/2014)
Grant Fritchey (2/3/2014)
wolfkillj (2/3/2014)
Grant Fritchey (2/3/2014)
wolfkillj (1/29/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 3, 2014 at 8:09 am
wolfkillj (2/3/2014)
Grant Fritchey (2/3/2014)
wolfkillj (1/29/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 3, 2014 at 7:54 am
Sean Lange (1/31/2014)
wolfkillj (1/31/2014)
Ed Wagner (1/31/2014)
Luis Cazares (1/30/2014)
Would this help?http://www.sqlskills.com/blogs/kimberly/guids-as-primary-keys-andor-the-clustering-key/
http://blogs.msdn.com/b/sqlserverfaq/archive/2010/05/27/guid-vs-int-debate.aspx
Maybe even a post from a GUID lover:
http://blogs.msdn.com/b/sqlazure/archive/2010/05/05/10007304.aspx
Or even BOL on Using uniqueidentifier Data:
http://technet.microsoft.com/en-us/library/ms190215(v=sql.105).aspx
I especially like Kimberly's article Luis posted here....
"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 3, 2014 at 5:31 am
anand.ramanan (2/1/2014)
Your work around for delegating profiler access is intriguing. Could you please take a few moments to share this setup, so it would help 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 3, 2014 at 5:13 am
wolfkillj (1/29/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 3, 2014 at 4:46 am
Greg Edwards-268690 (1/29/2014)
GilaMonster (1/29/2014)
Ed Wagner (1/29/2014)
GilaMonster (1/29/2014)
Could use some of that chill down here. We had a couple of weeks of 35 C+ (high for JHB). Seriously unpleasant.
That sounds seriously...
"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 3, 2014 at 4:40 am
rodjkidd (1/29/2014)
Talking of Grant, did anyone see the picture of him on the SQLCruise yesterday- almost as red as the livery of that company he works for!Rodders...
Unless it was 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
February 3, 2014 at 4:37 am
Jeff Moden (1/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 3, 2014 at 3:48 am
Lynn Pettis (1/24/2014)
Has anyone else ever heard that it is a best practice to have enough server memory to hold your entire database in memory?
Yeah, it's called SQL Server 2014.
But...
"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
January 24, 2014 at 1:53 pm
Greg Edwards-268690 (1/24/2014)
Koen Verbeeck (1/24/2014)
Anyone with a better grasp of SQL Server security and auditing can take this one?http://www.sqlservercentral.com/Forums/Topic1534372-2799-1.aspx?Update=1
Trust Me, but audit all the other Admins!
Something missing in that picture.
Sounds...
"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
January 24, 2014 at 6:24 am
Like I said. Opinions differ.
"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
January 24, 2014 at 6:21 am
Another consideration is the width of the key. The wider it is, the fewer key values are stored per page, which means possibly deeper B-Trees on the index and more...
"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
January 24, 2014 at 6:15 am
I suggest you always set the max memory. You're right. Your server doesn't seem to be under stress and the chances are, it won't be. But, SQL Server will attempt...
"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
January 24, 2014 at 6:10 am
Viewing 15 posts - 8,986 through 9,000 (of 22,224 total)