Viewing 15 posts - 20,446 through 20,460 (of 22,219 total)
Take a look at INFORMATION_SCHEMA.PARAMETERS. It's a system view in your database.
"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
May 8, 2008 at 6:45 am
Ah, I see where the problem might be:
(SELECT DISTINCT con.[ConsultantID]
...
"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
May 8, 2008 at 6:44 am
Piling on at this point, but what the heck...
TSQL is easy. WAY TOO EASY.
Developers look at it, learn the syntax and, as far as they're concerned, they're done. What they...
"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
May 8, 2008 at 6:27 am
One guess. When running the query from Management Studio, do you have hard coded parameters like this:
DECLARE @MyParm int
SELECT...
FROM dbo.View
WHERE SomeColumn = @MyParm
Then of course the proc might look...
"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
May 8, 2008 at 6:11 am
VARCHAR(MAX) probably needs to be streamed to ODBC, but I would think the max value would be a page worth of data, 8000, not 256 characters. I haven't seen a...
"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
May 8, 2008 at 5:56 am
Don't bow. You're right. 100%.
I think most of us have been focused on the indexes. I'm still a bit bothered by the cluster being on such non-selective columns. It's not...
"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
May 8, 2008 at 5:36 am
GSquared (5/7/2008)
antonio.collins (5/7/2008)
user defined procs in master. ewww!Yeah, that's why I create a Common database for that kind of thing.
Same here. Don't put this stuff in master. Don't...
"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
May 8, 2008 at 5:31 am
Same here. Can you generate execution plans for the two queries? Estimated of course since you don't want to wait for 10+ minutes again.
"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
May 7, 2008 at 1:22 pm
Generally, don't use them. Ever. Yes, there are exceptions to that rule, but you need to be extremely careful when deciding you have an exception. You may not actually have...
"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
May 7, 2008 at 11:08 am
Nope. GO is an external construct for scripting within SSMS, not an actual part of TSQL as such. How about COMMIT TRAN?
"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
May 7, 2008 at 7:51 am
Oooh! I may have to try that just to see what happens. I'll bet you looked great on that one. But here's a question, how long did it take 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
May 7, 2008 at 7:48 am
OK. Jack's explanation is more clear. Go with that one.
"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
May 7, 2008 at 7:42 am
GO acts to close off open transactions.
"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
May 7, 2008 at 7:42 am
Thanks! I've been practicing.
"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
May 7, 2008 at 6:50 am
Whatever the DTS package is doing, the transaction is so large that it's filling the log file. Break the transaction down into more discrete parts so that you get...
"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
May 7, 2008 at 6:47 am
Viewing 15 posts - 20,446 through 20,460 (of 22,219 total)