Viewing 15 posts - 53,866 through 53,880 (of 59,072 total)
Yeap... even on my 4 year old 1.8GHz desktop... not much of a difference... remember, this is to "return" a million rows out of 2 million...
==============================================================================
Testing lookup for non-0 Ints...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 11:51 am
Are you using any of the sp_OA* stored procedures? Are you closing GUI (and other) connections to the data base when they are no longer needed?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 10:11 am
Matt beat me to it... using a cursor for this is a sure fire way to make code run slow. Lose the cursor and do it in the setbased...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 10:07 am
They would be in "Books Online" which is the T-SQL help that comes free with SQL Server... learn to love it...
Lookup "Functions" after you find "Books Online"... I'm not sure...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 10:00 am
My real purpose here is to determine if there really is a performance advantage to not allowing nulls, as I was told, or if our lead designer is blowing smoke...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 9:56 am
majorbloodnock (11/28/2007)
Jeff Moden (11/28/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 8:47 am
In a trigger? It'll only work within the trigger... trigger is at a different scope... you may want to try @@IDENTITY if you're interested in the last ID that...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 8:32 am
Ananth (11/27/2007)
Jeff,I got the solution. ....
Thanks.
Thanks, Ananth... Just curious, though... did the solution you get have a "<=" anywhere in the code? If so, you may have a...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 8:17 am
That's better, Karthik...
I would also add a couple of things to that...
Reason 3:
SELECT * will normally cause a table scan (even if it looks like an index scan on the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 8:06 am
A location is a code varchar(10) and currently consists of 6 numeric digits where the first three are always zeros.
First, leading zeros tend to be for display and I...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 7:38 am
David Burrows (11/28/2007)
What? Oh? OH? OOOOOHHHHH!!! BWAAAA-HAAAAAA.....
Sorry Jeff...
Did not know if you were laughing at me :crying:
or at my question 🙁
or was it that I actually posted one :blink:
Oh, bugger......
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 7:07 am
Heh... the only Latin I know is "Non Illigitimi ie Carborondum" (very loosly translates to "Don't let the ba----ds grind you down". What does your tag line mean? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 7:01 am
Heh... speaking of "details"... once done and you go to format it, you wanna use commas or periods for the thousand separators? 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 6:53 am
but I am still waiting for a good friend to help me out
Ummm.... I wouldn't wait... take the bull by the horns and get to where you want...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 12:30 am
Nicely done, Brandie. Great success story and a great motivational story. I'll throw in that whether you have the schooling or not, you can get there if you...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 12:24 am
Viewing 15 posts - 53,866 through 53,880 (of 59,072 total)