Viewing 15 posts - 49,036 through 49,050 (of 59,099 total)
Ross McMicken (7/31/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2008 at 4:54 am
Oh, yeah... almost forgot... "In the land of the blind, the one eyed man is King!"... That's why most people look at the Execution Plan and believe in it. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2008 at 9:32 pm
I may have to write an article about it someday... I've found that WHERE NOT IN beats the OUTER JOIN type of exclusion, WHERE NOT EXISTS correlated subqueries, and a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2008 at 8:50 pm
Heh... reminds me of a dictionary... how can you check the spelling on a word using a dictionary without a bit of luck?
I agree with Matt... UNPIVOT is...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2008 at 8:44 pm
Matt Miller (7/30/2008)
Jeff Moden (7/30/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2008 at 8:41 pm
usman.tanveer (7/30/2008)
Can using (Nolock) or (ReadPass) help gaining performance benefits for select queries?
In my point of view may be we could......like in my scenario......db is accessed by multiple...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2008 at 8:21 pm
steveb (7/30/2008)
No worries,you could use the Left and Right functions.
I am not aware of any performance difference between the two and couldn't find anything aobut it on BOL.
LEFT...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2008 at 7:47 pm
usman.tanveer (7/30/2008)
These tables are the main tables of the Db and contains alot of data. Also multiple...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2008 at 7:44 pm
Angelindiego,
If done incorrectly, your CASE statement will turn out to be RBAR on steroids in the form of a correlated subquery. If you want, please post your final code...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2008 at 7:36 pm
Since update does not qualify as a non-logging bulk operation, I'd say you'd have to temporarily put the DB in the SIMPLE recovery mode and do the update in, say,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2008 at 7:20 pm
Matthew O'Gorman (7/30/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2008 at 7:13 pm
Heh... someone asked me why I've tried to specialize in behind-the-scenes-batch-programing in SQL Server... I believe I'll refer them to this thread. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2008 at 6:41 pm
Heh... space used... the Tally or "Numbers" table only takes 136KB for an 11,000 row table and that includes the clustered index in the form of a primary key. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2008 at 6:00 pm
kannan (7/30/2008)
Use DISTINCT..!
Sure... let's see your code example... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2008 at 5:37 pm
DBA (7/8/2008)
thank you!, both functions would do the same as using unpivot?
No... unpivot needs a predefined number of columns... neither the Tally table method nor the XML method need to...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 29, 2008 at 7:56 pm
Viewing 15 posts - 49,036 through 49,050 (of 59,099 total)