Viewing 15 posts - 48,991 through 49,005 (of 59,102 total)
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
vkres1,
Forget about the identity column... if you want to store the data in the correct physical order, then put a clustered index on the column(s) that you want the data...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2008 at 10:46 pm
rbarryyoung (8/2/2008)
Of course, the order problem can be easily remedied if you just add an Identity column. 🙂
I don't think it will, especially if parallelism kicks in. If...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2008 at 10:31 pm
Try your code, Barry. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2008 at 7:56 pm
Ummm... you're missing the point a bit. The order in which something is inserted doesn't really matter in an RDBMS. Why do you think you need a "natural...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2008 at 2:54 pm
That's why I put "new" in parentheses... haven't need MERGE in SQL Server 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2008 at 2:47 pm
The loop idea isn't actually a bad one (I refer to it as a "DELETE CRAWLER"), but deletes, by themselves, run pretty quickly depending on the criteria. I'd limit...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2008 at 11:26 am
PaulB (8/2/2008)
1 Brace for impact, keep your poker face no matter what you see.
2 All Oracle documentation is online and free... try http://www.oracle.com/pls/db102/portal.all_books
3 Subscribe a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2008 at 11:17 am
If it's only for two flights, then a simple join between destination of first flight and start of second flight for a given passenger number should do it.
If you want...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2008 at 11:00 am
I agree with Steve... doesn't matter what the insert order is, you should use ORDER BY in your queries and NOT rely on a physical order. You can force...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2008 at 9:51 am
What I think is interesting about that blog, is that it's the person writing the blog who is sometimes the "dumbass". One guy wrote about the ol' turbo button...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2008 at 8:43 am
That's correct... I missed that little "nuance"...
The code needs to look like this... Note the parentheses around @ExStr in the EXEC statement.
DECLARE @ExStr varchar(500)
SET @ExStr = 'CREATE TABLE dbo._X080805...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2008 at 8:19 am
jon.hart (7/30/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2008 at 11:09 pm
Viewing 15 posts - 48,991 through 49,005 (of 59,102 total)