Viewing 15 posts - 46,906 through 46,920 (of 59,101 total)
Not sure why they're exactly doubled because you've created an "accidental cross-join" and they should be a lot more than just doubled. Moot point, though. Let's fix...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 8:44 am
Yes... all joins basically fall into 3 categories behind the scenes... Hash, Merge, or Looping. A 10,000 foot overview for each is availbable in Books Online (BOL) and the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 8:23 am
I agree with Gail... those are about the only things I use triggers for. That includes the ability to keep people from changing DateCreated/Modified or CreatedBy/ModifiedBy columns. Other...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 8:02 am
The cool part about your solution, Chris, is...
... it's not dynamic SQL... just good, clean, hard-coded concatenation.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 7:45 am
GilaMonster (11/30/2008)
Jeff Moden (11/29/2008)
Your good explanation is, of course, the most accurate... I was just trying to give a 30,000 ft overview.
No prob. I was just worried that...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 7:43 am
Great information, one and all... but I still want to know what the CLR(s) the op wants to write do. We all know that too many people give up...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 7:42 am
Chris Morris (11/30/2008)
Jeff Moden (11/29/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 7:39 am
Grant Fritchey (11/30/2008)
The broke chain wipped around and touch my face & shirt.
Wow... last guy I heard of that happening to had to have major reconstructive surgery... you're a lucky...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 7:36 am
Jonathan Kehayias (11/29/2008)
Jeff Moden (11/29/2008)
Jonathan Kehayias (11/29/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 7:31 am
What's really amazing to me is that this thread has taken over 5,000 hits. D'ya s'pose anyone is actually learning anything for this? We can only hope.
Good chattin'...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 7:32 pm
brijbmishra (11/28/2008)
Can we develop a CLR based Stored Procedure without using Visual Studio?
What do you intend the CLR to do?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 7:17 pm
Heh... not trying to be a smart guy here... FEDEX overnight. Works great.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 7:00 pm
Lynn Pettis (11/29/2008)
Sometimes even those of us with lots of points to left need help. Heck, I think I even have seen Jeff post a question or two here.
Yep......
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 6:54 pm
Either that, or a partitioned view.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 6:11 pm
Charles Kincaid (11/29/2008)
Best to store unknown dates as NULL anyway.
I agree... if you don't know a date, store it as a NULL and convert it in the GUI.
Some folks store...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 5:52 pm
Viewing 15 posts - 46,906 through 46,920 (of 59,101 total)