Viewing 15 posts - 54,301 through 54,315 (of 59,072 total)
David McFarland (11/6/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 9:44 am
karthikeyan (11/6/2007)
For example if i create # table then it will be stored in TempDatabase.
But...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 8:35 am
Matt Miller (11/6/2007)
Well - the test was for 3,540,000 records, and it ran in 34 secs...
Perfect... I'm at work right now... I'll try to set something up tonight... thanks, Matt!
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 8:31 am
Sure, John... kind of... hope you don't mind a bit of psuedo code because I don't ever use DTS except for ad-hoc transfers...
Create two identical tables to hold the data......
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 8:25 am
Kewl! Anyone interested in a million row duration test on this? 😀 I'd need some help 'cause I don't have 2k5...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 8:11 am
Thanks, Antares!
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 8:06 am
IF OBJECT_ID('sometablename,'U') IS NOT NULL
DROP TABLE sometablename
Lookup OBJECT_ID in Books Online... it's worth the read. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 7:37 am
Heh... you've basically pulled the wings off of any chance of performance by using outside code to do something inside the database... you said that you want to import 26MB...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 7:36 am
Heh... Michael, thank you for the high compliment! Made my day... 🙂
o1000, Michael is correct... what you want to do just seems tremedously odd and I want to see...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 7:20 am
Heh... if you're worried that it will affect the data returned, you need to test!
And the position of the AND somecol = someval code does make a difference...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 7:14 am
Since the numbers you want are 1 to 354 and not 0 to 353, you'll probably have to change John's code just a bit...
UPDATE Random_region_lookup_table
SET Place_key = Entry_key%354
... should probably...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 7:09 am
This is a fairly common request and it always amazes me that folks would have two identical tables and be worried about synching up their contents. The only time...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 6:55 am
Catcha,
Someone tried to force some serious tuning on that query... the FORCE ORDER tells the optimizer to only consider the tables in the same order as they appear in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 6:48 am
Are the random numbers allowed to repeat within a generation and are others allowed to be missing as would a true random number provide?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 6:24 am
Uh huh... sure does. Thanks, Matt 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2007 at 11:27 pm
Viewing 15 posts - 54,301 through 54,315 (of 59,072 total)