Viewing 15 posts - 51,541 through 51,555 (of 59,091 total)
Yep... you're gonna have to put the result of the CTE into a temp table as a separate query... include a RANK column. Then, see the part about "Grouped...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 8:48 am
Chirag (3/24/2008)
My procedures get changed daily and i cant generate the alter script as iam using SQL 2005 RTM ( i cant change it).
Chirag,
I'd worry about that problem more...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 7:41 am
Jason Selburg (3/24/2008)
And there is probably an easier way to write this... 😀
That would be true, ol' friend... and, in this case, simpler means faster and easier to read to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 7:36 am
Just my 2 cents on this one... I've found that the WHERE NOT IN that Barry used is usually more performant than outer joins. The speed difference isn't huge...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 6:06 am
There is some merit to storing the following in separate files on separate drives if possible...
Static Tables and monthly archives
Audit Logs
Common utilities and functions, etc
Application stored procedures, functions, etc.
Non-static application...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 6:03 am
Proof is always good... gotta love BOL. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 5:46 am
Matt Miller (3/24/2008)
It's a bit like hitting a moskito using a 155mm Howitzer...
Hmmmm... might have to trade in the ol' slingshot... bet it works real good with porkchops...:D
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 11:48 pm
Let's see if I counted this right...
1 Cursor
30 separate SELECTs (many nearly identical) not including the cursor
1 Insert
... per row...
I wonder how long this puppy is going to take to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 10:55 pm
Matt's code is functionally perfect and identical in performance (< 15 seconds total duration) to the following code... the only difference is the following code uses a single CTE for...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 10:42 pm
The following URL seems to have the information necessary...
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1175067&SiteId=1
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 9:00 pm
I agree about SQLCompare by RedGate...
However, you have to ask why you want to do this. I find the typical application is to find the differences between a Development...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 8:34 pm
Something else to be keenly aware of... many databases have views that have no indication in the name that they are, in fact, views... see if the "cc_message" table is...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 8:31 pm
tymberwyld (3/24/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 8:17 pm
Nope... here's the example from BOL... and, I've tested it... works fine... and despite what it says about schema.ini, you don't need it for comma delimited files.
H. Use the Microsoft...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 5:46 pm
Heh... nothing to report on... that's "Cohen's Law". Cohen is the brother of Murphy and he states that "The more time you spend on reporting, the less time you...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2008 at 5:42 pm
Viewing 15 posts - 51,541 through 51,555 (of 59,091 total)