Viewing 15 posts - 2,236 through 2,250 (of 8,416 total)
The optimal index for the query given is:
CREATE INDEX [IX dbo.CoverageVersions CoverageKey,Effective (SourceKey,CovRefundKey,TypeKey,StatusKey)]
ON dbo.CoverageVersions (CoverageKey DESC, Effective DESC)
INCLUDE (SourceKey, CovRefundKey, TypeKey, StatusKey)
WITH ...
December 22, 2010 at 8:25 am
Brandie Tarvin (12/13/2010)
December 22, 2010 at 8:18 am
Help us to help you:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
Existing SSC articles that you may find helpful:
December 22, 2010 at 7:24 am
jteeter (12/21/2010)
December 22, 2010 at 7:18 am
stewartc-708166 (12/22/2010)
You could have used sys.syscolumns.colorder, which maintains the ordinal position of the columns per table.
How can you be sure? My copy of Books Online says sys.syscolumns is a...
December 22, 2010 at 7:05 am
So, my advice is:
1. Remain in 80 compatibility only as long as it takes you to update your code to be fully compatible with 2005.
2. Start using new...
December 22, 2010 at 6:38 am
KMPSSS (12/22/2010)
Right now sql compatibility level is 80.
But in this cross apply and CTE type are accepted. only the problem is pivot type.
...
December 22, 2010 at 6:33 am
You're right that there are no simple answers that are always applicable, but there are some guidelines.
First, using EXCEPT is almost never going to be the best way to accomplish...
December 22, 2010 at 5:02 am
Short answer: you can't, so you're going to have to make some changes.
Replace all the uses of *= and =* with the new syntax. No-one uses *= and =*...
December 22, 2010 at 4:32 am
Gianluca Sartori (12/22/2010)
December 22, 2010 at 2:28 am
Another natural option is the recursive one:
DECLARE @Example
TABLE (
ID INTEGER PRIMARY KEY,
...
December 22, 2010 at 2:04 am
Gianluca Sartori (12/21/2010)
MelS-512196 (12/17/2010)
CROSS APPLY -- try it you'll like it! 😀
... if you like Nested Loops! 😛
It's a great feature, but it often ends up with a Nested Loops...
December 21, 2010 at 11:32 pm
Revenant (12/21/2010)
December 21, 2010 at 11:19 pm
vinothraj (12/21/2010)
Could you explain me in detail? Quite stucking with "version-stamping rows".. Thanks for your help
Jokes very rarely benefit from being explained in detail, but take a look at the...
December 21, 2010 at 11:00 pm
vinothraj (12/21/2010)
Casting it as datetime, we are getting '1900-01-01 00:09:41.003'.. what is the use of this?
Mr Magoo was joking: in SQL Server timestamp is a mechanism for version-stamping rows. It...
December 21, 2010 at 10:30 pm
Viewing 15 posts - 2,236 through 2,250 (of 8,416 total)