Viewing 15 posts - 53,206 through 53,220 (of 59,072 total)
I appologize for the semantics... but, in SQL Server 2000, unless you take on the TEXT datatype as an input parameter, the largest character based variable you can define is...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 12:39 pm
Steve Jones - Editor (1/1/2008)
Or this: http://www.sqlservercentral.com/articles/Stored+Procedures/2977/
Heh... you think that's going to work on SQL Server 2000? This is a 2k forum, ya know 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 12:19 pm
Heh... if it's a very well written query, it will always run the CPU to 100%... just for a very, very short time... and that's the goal... get everything done...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 12:13 pm
Actually... good... typing on a blog lickety-split is one of the things that I'd like to get away from during an NCAA game. Leave your bloody laptops at home....
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 9:02 am
-- Plz close this post
First, thank you very much for posting your hard earned solution... that's what this forum is all about.
The only problem that I see with your solution...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 8:58 am
I've found that the single best improvement you can make in this area is to find and remove all hidden RBAR... "touch" each row only once, if possible, and as...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 8:48 am
Another great summary! Great work, Gail.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 8:43 am
Yes, but you need to do it through "OSQL". Lookup "OSQL" in Books Online for full details about usage.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 8:40 am
Nice blog, Gail...great explanations!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 8:39 am
I'll say, "it depends"...
If I'm looking to hire an "entry level" developer, there may be little or no experience to go on in which case education (math background preferred)...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 8:27 am
Still, ya gotta admit, Phil... that's 5 times faster... if you make those types of small improvements in many areas of a whole batch that makes multiple passes on a...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 8:18 am
Heh... thanks Mike, but you didn't read the code block just before the conclusion 😉 Like Ragu... "It's in there". 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2008 at 12:08 am
Thanks, Chirag. Appreciate the compliment!
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2007 at 10:40 pm
What a great way to start the year! Thank you for the awesome compliments, Paul!
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2007 at 10:09 pm
Jason! Hey! How's the new job???
I'll bet I know why he wants it... it's probably to find missing ID's in a table. My first reaction would be...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2007 at 7:32 pm
Viewing 15 posts - 53,206 through 53,220 (of 59,072 total)