Viewing 15 posts - 19,066 through 19,080 (of 22,226 total)
Jeff Moden (12/15/2008)
Must be something else... I raised two kids... even did the Cub Scout and Boy Scout thing and a whole bunch of other things that gave me 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
December 16, 2008 at 5:25 am
Jeff Moden (12/15/2008)
Heh... here's my twit for the week... gotta love the arrogance...http://www.sqlservercentral.com/Forums/Topic619172-1291-1.aspx#619380
At least he made it easy for you:
Either help or don't bother.
"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 15, 2008 at 6:55 pm
Wait, wait... I'm confused.
We had tracks?
"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 15, 2008 at 6:53 pm
Itzik Ben Gan's new one, SQL Server 2008 T-SQL Fundamentals. Almost all of it will be applicable to 2005. After you finish that one, pick up his older book Inside...
"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 15, 2008 at 1:15 pm
Well, I didn't just tumble out of a Vault, you know.
"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 15, 2008 at 1:12 pm
I agree with Jack on this. SSMS is a pretty good tool, but you don't have to use it. As a matter of fact, you might be much better off...
"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 15, 2008 at 12:51 pm
It means the process itself still has work to do, but it's waiting on something. BOL refers to blocking as a possible cause.
"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 15, 2008 at 12:04 pm
Is the field a number field, int, bigint, numeric, decimal. If not, it won't allow you to create an identity.
"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 15, 2008 at 11:59 am
I'd strongly suggest you use Matt's solution. The one you have is going to perform pretty badly.
"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 15, 2008 at 10:18 am
Then you're just a little bit stuck. You can't refer to objects that don't exist in the query, even if it's just in an IF statement. Why couldn't you use...
"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 15, 2008 at 9:12 am
Depending on the data types in question, there's nothing inherently wrong with a compound natural key. I'm not sure why it would matter to the end user 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
December 15, 2008 at 9:08 am
If I understand the problem, then I'd suggest instead of having three queries for the three version, have three procedures and then, depending on the version, using your IF statement,...
"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 15, 2008 at 8:55 am
I'm pretty similar in approach, Profiler is my bestest buddy.
After that, since you're in 2005, you can look at sys.dm_exec_query_stats for an immediate picture into which queries are running...
"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 15, 2008 at 8:49 am
Absolutely. No issues at all.
"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 15, 2008 at 7:48 am
It sounds like you can do this with a trigger or with a stored procedure. While I'm not a fan of triggers, if you need one, you need one. It...
"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 15, 2008 at 6:50 am
Viewing 15 posts - 19,066 through 19,080 (of 22,226 total)