Viewing 15 posts - 12,811 through 12,825 (of 22,219 total)
David Burrows (4/6/2011)
Grant Fritchey (4/6/2011)
Our Starblazers
Thunderbirds Are Go
Hey, Hey, we're The Monkeys
I'll add two:
Jonny Quest
Space Ghost
How about
Fleegle, Bingo , Drooper and Snork 😀
Oh oh, Shongo!
"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 6, 2011 at 5:59 am
I'm sorry, I don't understand what you're asking. Can you clarify further?
"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 6, 2011 at 5:54 am
Each and every SQL Server installation is different. Different servers of different CPU speeds & numbers, with varying amounts of memory. Different databases with different applications and varying number 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
April 6, 2011 at 5:50 am
I wouldn't compare SSMS to your app. I presume they're doing different things. SSMS is loading all sorts of different bits of data as it opens and connects, stuff your...
"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 6, 2011 at 5:47 am
My favorite software for doing this is Embarcadero ERStudio. It meets all your requirements and quite a few more. If you're going to work on your databases through a modeling...
"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 6, 2011 at 5:43 am
Brandie Tarvin (4/6/2011)
Grant Fritchey (4/5/2011)
Brandie Tarvin (4/5/2011)
Grant Fritchey (4/5/2011)
"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 6, 2011 at 5:08 am
sqldba_icon (4/5/2011)
GilaMonster (1/18/2011)
Lee Forst (1/18/2011)
"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 5, 2011 at 2:54 pm
Jeffrey Williams-493691 (4/5/2011)
Grant Fritchey (4/5/2011)
"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 5, 2011 at 2:53 pm
What version of 2005 are you running. Apparently if you're not up to at least Sp2 this won't work.
"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 5, 2011 at 2:52 pm
Yeah, local variables is a mechnism for defeating some forms of parameter sniffing. What it means is, instead of using a specific value to arrive at an execution plan, it'll...
"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 5, 2011 at 2:48 pm
It sounds like you're experiencing what is known as bad parameter sniffing. There are several ways to fix this before you get to plan forcing. That should be the last...
"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 5, 2011 at 11:47 am
Lots can go wrong. Upgrading away from 2000 can be quite dangerous. It really depends on what kind of code was written against the 2000 server and how it was...
"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 5, 2011 at 11:44 am
Rich-403221 (4/5/2011)
"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 5, 2011 at 11:42 am
I don't know that there is a single best practice, but in general I would advocate for having a service account for SQL Server and have the jobs owned by...
"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 5, 2011 at 11:37 am
Stefan Krzywicki (4/5/2011)
Grant Fritchey (4/5/2011)
Brandie Tarvin (4/5/2011)
Grant Fritchey (4/5/2011)
"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 5, 2011 at 11:33 am
Viewing 15 posts - 12,811 through 12,825 (of 22,219 total)