Viewing 15 posts - 51,346 through 51,360 (of 59,098 total)
Preet (4/1/2008)
Really!Do you think we got nothing better to do than read pointless articles?
Heh... well at least we know of one person who was going to buy it right...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 2:42 pm
Matt Miller (4/1/2008)
Jeff Moden (4/1/2008)
Matt,Awesome. Can you post the test code? That sure sounds like a "keeper" to me.
You've already seen it... right here (sorry - forgot to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 2:34 pm
Rags, I've got one more "by the way"... you are using this just for a GUI passing parameters, aren't you?
If you're trying to split a whole column of CSV's, then...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 2:31 pm
Rags (3/31/2008)
Jeff Moden (3/31/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 2:28 pm
J (4/1/2008)
Jeff Moden (4/1/2008)
Are you going to do that from a GUI where parameters are normally passed as CSV's?Er, is the question addressed to "Rags" or to "J" ?
Sorry... I...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 2:25 pm
Outstanding set of posts on this thread, both pro and con! Thanks for the very interesting conversation and the testing that some of you have done! You guys...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 2:19 pm
John Rowan (4/1/2008)
You should see how fast things run in the NV tables when you've had the time to add the proper indexes.
Thanks. For my example, I've only added...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 2:17 pm
Moral: even if you decide to combine subtypes in the transaction table, write your SQL as if they were separate tables.
Heh... moral of the story should be that if...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 2:15 pm
TheSQLGuru (4/1/2008)
1) most code doesn't actually GET reused because a) all devs don't know about it, b) devs don't bother checking to see if their...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 2:11 pm
SQLZ (4/1/2008)
The trick is in knowing when to use them.
That is absolutely correct! The problem is that most people simply give up too soon!
When a developer comes to me...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 2:01 pm
Heh... Karl... no wonder that it appears that your cursor beats the function... your cursor doesn't do the same thing/produce the same row set... I'm working on it...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 1:35 pm
This will sound a bit like sacrilege on my part... I agree that for some management tasks, they're probably ok... but those types of cursors aren't usually all "RBAR"... normally...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 12:32 pm
Thanks Matt. Learned something new today! 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 12:29 pm
Absolutely no hard feelings here, my friend! 🙂 Good heated debates like this either bring out the best in folks or the worst. You've easily been in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 12:17 pm
Matt,
Awesome. Can you post the test code? That sure sounds like a "keeper" to me.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 11:57 am
Viewing 15 posts - 51,346 through 51,360 (of 59,098 total)