Viewing 15 posts - 41,926 through 41,940 (of 59,067 total)
Heh... no loops, please... not even in 2k. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2009 at 10:35 am
Heh... holy moly! I just now found this thread. Needless to say, a whole lot of water has passed under the bridge in the last two years... 3000...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2009 at 9:58 pm
From one "Jeff" to another, welcome aboard and I agree... pretty good job for a first post.
To follow up on Bob's good suggestion, take a look at the article at...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2009 at 3:55 pm
Please see my previous post above.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2009 at 3:32 pm
He might if we could find out what it was about and perhaps make a suggestion on the T-SQL side.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2009 at 3:05 pm
winterminute (9/13/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2009 at 2:55 pm
Fine... if you don't want to tell me what the CLR does so maybe I can come up with an alternate solution, then enjoy your memory problems. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2009 at 2:23 pm
James Stover (9/12/2009)
Irrelevant since we are all going to end up in the Cloud 🙂
BWAA-HAA!! Guess I'm going to have to start hoarding computers. Between the "Eatr" project and...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2009 at 5:46 am
pandeharsh (9/12/2009)
No ,Sql Server we do not use cursor and also in sql server we can do without cursor.
But in oracle I see that using cursor is must.
Also,I read here...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2009 at 10:27 pm
You might also want to lookup what OUTPUT does for you, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2009 at 4:51 pm
I don't have a very good answer for you but I can tell you that using @@IDENTITY, especially if triggers come into play, is a form of "Death by SQL"....
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2009 at 4:50 pm
it.tomar (9/12/2009)
I am agree with Speed's comment
In the posts above, who are you referring to as "Speed" because I don't see anyone with that particular handle.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2009 at 4:46 pm
Roy Oliver (9/12/2009)
Interesting... it'd be easier if SQL Server implemented triggers in the same way Oracle did.
Why? They are inherently RBAR. "For Each Row".
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2009 at 4:41 pm
Heh... Not sure what it'll take so I'll ask one more time for you to help me help you... please post the CRATE TABLE statement for the calendar table and...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2009 at 3:35 pm
Garadin (9/12/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2009 at 1:24 pm
Viewing 15 posts - 41,926 through 41,940 (of 59,067 total)