Viewing 15 posts - 40,876 through 40,890 (of 59,069 total)
Heh... nah... it's just the human element on a (thankfully) open forum. Sometimes ya just gotta play the ol' Jedi mind trick on your self... "These are not the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 2:36 pm
Now you're talking... Beer fixes everything especially when war stories about work are involved. :w00t: Add a pool table and some good company and there are no problems that...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 1:49 pm
G33kKahuna (12/1/2009)
Heh... man... you don't need be to be so rude. Most everything that folks write an article having to do with SQL Server are all "age old dilemma's" and...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 1:30 pm
ezlikesundaymorning-573799 (12/1/2009)
I was trying to make a point.
Heh... me too, Luther. Hit the showers and cool down. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 1:15 pm
To add to that, do you have persited calculated columns, indexed views, or a wad of constraints?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 12:54 pm
That's only 136 Mega bytes... why the concern?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 12:46 pm
Heh... clever startup procedure trick by a laid off employee???
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 12:41 pm
Consider the faster/sometimes easier alternative to Pivot...
http://www.sqlservercentral.com/articles/T-SQL/63681/
http://www.sqlservercentral.com/articles/Crosstab/65048/
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 12:34 pm
but I don't see this job as my great passion
You know full well why I usually don't post anywhere else but SSC... I'll reiterate what has already been said... it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 12:24 pm
I'n not sure how complicated your code is but if it's not too long, you could post it and we might have an even better suggestion.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 12:10 pm
I agree with GSquared. The newly "INSERTed" row is in the original table. All you're doing with capturing INSERTs is effectively doubling the data. With some rare...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 12:07 pm
You should still post the code.... you might be surprised what else folks can help on especially if it turns out to be a RBAR trigger. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 11:48 am
stewsterl (11/30/2009)
Jan Feb ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 11:43 am
G33kKahuna (12/1/2009)
this is an age old dilemma and was put to rest with many variations like JP de Jong-202059 pointed out. In fact this site has articles with script to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 11:38 am
Sorry, Pren... I lost track of this one. Does khawaja.irfan's solution work for you?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 11:24 am
Viewing 15 posts - 40,876 through 40,890 (of 59,069 total)