Viewing 15 posts - 55,636 through 55,650 (of 59,072 total)
Like Jackie Chan's Uncle would say "Oh! One more thing"...
I keep a "Tally" table of 11,000 numbers as a permanent table... good for more than 30 years of...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2007 at 7:11 pm
Oh yeah... almost forgot... if you want a nice clustered primary key on both, the test and test results are as follows:
--===== Setup the test environment
SET NOCOUNT...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2007 at 7:06 pm
If you always want the numbers table to start at 1, this demonstrates both an alternative to the function and a comparison of run times from 10 rows to 10 million rows...
--Jeff Moden Change is inevitable... Change for the better is not.
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
July 26, 2007 at 6:46 pm
Uh-huh... so... whatcha gonna do with values that could look like this? ![]()
SELECT ISNUMERIC('13e05')
SELECT ISNUMERIC('13d05')
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2007 at 5:05 pm
Got part way there using a limited triangular join... it spawned 2 times as many rows as the original count of both tables and that's with just a couple of dates... I...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 8:39 pm
Eugene... wanna post some data from the file, please?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:43 pm
Guess you can't actually look into a book on Amazon anymore, huh ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:34 pm
Ummm.... not quite that simple... need to distribute a batch of QTY 15 issues against 4 batches of QTY 5 each and do the calculation and forward the remainder. Lot's...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:29 pm
That's why the stored proc method is better.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:25 pm
Thanks for the feedback, Kung Lao.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:23 pm
Is GROUP BY what you're looking for?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 7:33 am
This sounds like the text version of a "name/value" table... I'm with MrPoleCat... if you could post a bit of the text table, perhaps we could help. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 7:32 am
I don't know what sqlcomm1.ExecuteNonQuery() does because I'm no GUI programmer... UPDATE's are actually a form of a query and that may be your problem (but dunno for sure). But...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:54 am
Heh... and I just "assumed"... we all know what happens when you do that, eh ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:34 am
Well... that depends... do you want to shrink the file or not? The NOTRUNCATE causes the "freed file space to be retained in the files". If you want to actually...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:29 am
Viewing 15 posts - 55,636 through 55,650 (of 59,072 total)