Viewing 15 posts - 19,096 through 19,110 (of 22,219 total)
And even as you hit the limitations on a single table inside a single database on a single server, you can start to look at partitioning and parallel processing using...
"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 11, 2008 at 12:52 pm
It depends.
Is there going to be a lookup value:
08 A
As well as the value:
07 A
If so, then the year should probably be part of the PK of the lookup table...
"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 11, 2008 at 11:59 am
Yeah, maybe that's what I read too. I know I saw that it's going to more and more standard, if not required. So I'm working it into my code now....
"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 11, 2008 at 10:26 am
I'd say it's a good habit to get into. If you use CTE's you must use a semi-colon terminator on the statement preceding the CTE. Microsoft has said they're going...
"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 11, 2008 at 9:30 am
Roy Ernest (12/11/2008)
Kishore.P (12/10/2008)
Gauthama Kolivad (12/10/2008)
As Gail Shaw mentioned if...
"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 11, 2008 at 9:17 am
Lynn Pettis (12/11/2008)
"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 11, 2008 at 9:11 am
You might want to try using TOP(1) with an ORDER BY. If you're referencing an index, the TOP (1) is pretty consistently faster than the MAX.
"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 11, 2008 at 8:17 am
If it makes you feel better I've been hit, while stopped, not stopping, I've been sitting still, waiting, four times over the last 10 years. You're not alone.
Luckily, I drive...
"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 11, 2008 at 7:13 am
You can't really filter by table in a trace. You can filter by database, which should help. You can also filter by user, which again will help. After that, 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
December 11, 2008 at 6:58 am
Classic. Little Bobby Tables.
"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 11, 2008 at 6:30 am
Walking might be dangerous because when the car bounces off of Lynn... I don't have those ninja/cat reflexes. I'll just get hit.
"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 11, 2008 at 6:23 am
Suresh has a good example there. Perfect.
You just have to decide if the size of the index and the added cost of maintaining it are worth the benefits you'll derive...
"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 11, 2008 at 5:55 am
Yeah, what Jeffrey wrote is correct for the cast & conversion. However, I do agree with Jeff. Normally I wouldn't recommend doing this sort of formatting in SQL Server.
BTW, 2008...
"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 11, 2008 at 5:48 am
I'm going with the consensus on this one... we'll walk or I'll drive. 😛
"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 11, 2008 at 5:19 am
As long as it's datetime, you'll still get the time field. Try using the CONVERT with 101 and CAST to VARCHAR. That should do what you need.
"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 10, 2008 at 5:34 pm
Viewing 15 posts - 19,096 through 19,110 (of 22,219 total)