Viewing 15 posts - 48,976 through 48,990 (of 59,099 total)
I think the correlation between lazy and incompetent is almost 100% 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2008 at 9:00 pm
Heh... thanks for the feedback... I've done the same thing, many times. Didn't know for sure if you were on to something that I wasn't aware of or not...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2008 at 8:46 pm
He already did... 😉
SELECT *
FROM #NewTempTable
ORDER BY ID
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2008 at 8:36 pm
...and, with NO indexes whatsoever on the table, it only took 289 milli-seconds...
Are you sure that the "table" you're looking at isn't a view? And, again, how many rows...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2008 at 4:56 pm
maruf24 (8/3/2008)
when i...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2008 at 4:53 pm
Jeffrey Williams (8/3/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2008 at 4:38 pm
Jeffrey Williams (8/3/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2008 at 4:34 pm
Sorry, was in a hurry. I should have posted them (more than 1) without even being asked.
There are a couple of ways to do it... the method with the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2008 at 10:23 am
koosubscriptions (8/3/2008)
Is there any performance cost compare with if the query already exists?Thank you.
Probably not... it would probably recompile even if it were hard coded just because of data changes...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2008 at 10:00 am
That will work just fine, but only if a single row is inserted at a time. If there's a chance that more than 1 row can be inserted at...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2008 at 9:54 am
For what? The original code you posted?
If so, why not just insert the header information in a set based manner and then use that information to control another set...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2008 at 9:41 am
Good point, Carl. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2008 at 9:28 am
Barry... you might want to look for the word "Cursor" in the above script... 😀 Heh, late nite posts get me, too! 😉
Other than that, nice conversion! 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2008 at 9:17 am
vkres1 (8/2/2008)
Jeff,rbarryyoung is telling it is eaier with identity column. Do you know how to figure out with
identity column?looks like clustered index is not guaranteed as you said. any idea
Thx
rbarryyoung...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2008 at 9:12 am
rbarryyoung (8/2/2008)
Jeff Moden (8/2/2008)
The DBA was nothing but a BSOFH.;)Uuuhh, ... "Big Stupid Old Fart-Head"?
Heh... Ummm... no... what's your user name again? 😉
http://members.iinet.net.au/~bofh/bofh/bofh2.html
http://members.iinet.net.au/~bofh/
The "SO" stands for "SysOP"... you can figure...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2008 at 11:05 pm
Viewing 15 posts - 48,976 through 48,990 (of 59,099 total)