Viewing 15 posts - 56,101 through 56,115 (of 59,072 total)
Well, not really... if you have a hundred million row table and you isolate a million of those rows in a temp table for some SQL prestidigitation, for example...
Or you...
--Jeff Moden
Change is inevitable... Change for the better is not.
Are you storing numbers that you will calculate with in that column??? World of hurt getting ready to happen there... $ won't let you do calcs unless you first convert to...
--Jeff Moden
Change is inevitable... Change for the better is not.
How's 'bout running Steve's riding lawnmower underwater?
I'm the luckiest guy in the world… my Dad made the coolest "gadget" I've ever seen except it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
Other queries did top/bottom 10% of the whole table which is why you got such a disparity in rows... Serqiy's does it correctly by the key column...
--Jeff Moden
Change is inevitable... Change for the better is not.
When you say the tables have "no indexes on them", I'm hoping that you at least have a primary key
If not, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
Part of the problem with table variables is they do not nor can they be made to use statistics... table variables should be kept relatively short... changing to a temp...
--Jeff Moden
Change is inevitable... Change for the better is not.
Or, just set if to off... won't produce an error if it's already off.
--Jeff Moden
Change is inevitable... Change for the better is not.
Thanks, Andy...
--Jeff Moden
Change is inevitable... Change for the better is not.
That's the ticket... Thanks, Lynn.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 15 posts - 56,101 through 56,115 (of 59,072 total)