Viewing 15 posts - 46,891 through 46,905 (of 59,095 total)
Put this at the beginning of your trigger...
IF @@ROWCOUNT = 0 RETURN
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 8:14 pm
Unless the output is directed at a format-defined file, date formatting should be done in the GUI.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 7:53 pm
Just curious... why do you need to do this?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 7:50 pm
rbarryyoung (11/30/2008)
Jeff Moden (11/29/2008)
Either that, or a partitioned view.
Heh. You know the first time I read this I thought that you said "Partitioned Table". I didn't realize until...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 7:38 pm
I know Steve will step in on very rare occasions, but, for the most part, nothing get's moderated out of the forums on SQLServerCentral.com. What you see, is what...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 7:35 pm
Jonathan Kehayias (11/30/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 7:21 pm
... and I was talking a bit more genericly...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 9:52 am
GilaMonster (11/30/2008)
Jeff Moden (11/30/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 9:51 am
Just in case you already read the above, I had forgotten the "END" for each CASE in the code. I've corrected the code.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 8:48 am
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
Viewing 15 posts - 46,891 through 46,905 (of 59,095 total)