Viewing 15 posts - 16,696 through 16,710 (of 22,226 total)
Lynn Pettis (8/20/2009)
Grant Fritchey (8/20/2009)
Lynn Pettis (8/20/2009)
Kit G (8/20/2009)
RBarryYoung (8/20/2009)
"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
August 20, 2009 at 12:36 pm
Lynn Pettis (8/20/2009)
Kit G (8/20/2009)
RBarryYoung (8/20/2009)
"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
August 20, 2009 at 12:11 pm
RBarryYoung (8/20/2009)
"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
August 20, 2009 at 10:37 am
I checked the output from the default trace when you script it, and for EventID 10, there was no Column 1. You might try using column 2. Here's what 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
August 20, 2009 at 8:47 am
ruancra (8/20/2009)
"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
August 20, 2009 at 8:16 am
I don't think anyone has mentioned it, but man, is that query going to run slowly. All those correlated sub-queries are going to be painful. You might want to explore...
"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
August 20, 2009 at 7:14 am
If you aren't already, I'd strongly suggest you start treating the database just like your code. Get it into source control and only do your builds & deployments from there...
"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
August 20, 2009 at 7:08 am
Also, you need to know, tempdb is used for a lot more than just temp tables. It's used for sorting data, frequently from ORDER BY statements. If you're using snapshot...
"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
August 20, 2009 at 6:50 am
To get them execution permissions, I'd suggest giving them execute on the schema:
GRANT EXECUTE ON SCHEMA :: Dude TO Somebody;
In order for them to create procedures, you have to give...
"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
August 20, 2009 at 6:45 am
GilaMonster (8/19/2009)
GSquared (8/19/2009)
Or video it, and review the video yourself. It's amazing what you'll note when you watch yourself in action. Sounds narcisistic, but it's really useful.
Do 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
August 20, 2009 at 5:44 am
GilaMonster (8/19/2009)
Jack Corbett (8/19/2009)
GilaMonster (8/19/2009)
*Woot* Just got TechEd evaluation scores. Bar one comment, very nice!Congrats, but of course exactly what I'd have expected for you, barring the one negative comment.;-)
Comment...
"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
August 19, 2009 at 10:53 am
GilaMonster (8/19/2009)
*Woot* Just got TechEd evaluation scores. Bar one comment, very nice!
Congrats
"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
August 19, 2009 at 9:09 am
I would say there's no advantage. The normal backup process is very light-handed. It's transactionally aware, so you get good, clean backups, all without interrupting user access. Why on...
"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
August 19, 2009 at 7:58 am
I'd be willing to do it. I like the general concept of a contract-to-hire position.
"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
August 19, 2009 at 7:52 am
I don't have a clue. It'd be fun to have that problem though.
"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
August 19, 2009 at 7:42 am
Viewing 15 posts - 16,696 through 16,710 (of 22,226 total)