Viewing 15 posts - 51,346 through 51,360 (of 59,091 total)
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
Marios Philippopoulos (4/1/2008)
Jeff Moden (4/1/2008)
But, the real key here is that CLR's are not necessary for 99.9% of anything you do in a database. It can all be done...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 11:50 am
srienstr (4/1/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 11:38 am
Are you going to do that from a GUI where parameters are normally passed as CSV's?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 11:36 am
Karl,
Would you be kind enough to post your cursor code? I'd like to take a peek at it becauase I think I've only written 2 in my life...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 11:33 am
To add to what Matt just said... if the server logs in as a domain super-user that can see all the machines and at least some "shares", using a little...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 11:25 am
rbarryyoung (4/1/2008)
Jeff Moden (4/1/2008)
You still haven't answer my other suggestion... instead of the DBA having to learn C# or whatever, what about the developers learning good T-SQL?
Why not both? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 11:18 am
Marios Philippopoulos (4/1/2008)
Jeff Moden (4/1/2008)
You still haven't answer my other suggestion... instead of the DBA having to learn C# or whatever, what about the developers learning good T-SQL?
Both are necessary....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 11:05 am
Viewing 15 posts - 51,346 through 51,360 (of 59,091 total)