Viewing 15 posts - 55,216 through 55,230 (of 59,072 total)
We had similar problems finding the CPR (cut, paste, replace) code liberally sprinkled in some of our apps. It was a bit time consuming and certainly required some regression testing,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 2, 2007 at 7:05 am
I'm not sure why you have data duplicated in two separate tables... that usually constitutes a violation of 3rd Normal Form... but it's your database...
... something like this will do...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 2, 2007 at 6:44 am
I've got to agree with David... I'm sick and tired of exams that have been written by folks that are simply not qualified to write exams. That includes the things...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2007 at 12:39 pm
Any of your processes or stored procedures using Cursors, While loops, or other RBAR?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2007 at 12:21 pm
The problem is likely not the Dynamic SQL... nor is it likely the fact that you are joining 6 tables... but it's real hard to figure out what it could...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2007 at 12:18 pm
Now. THAT's what I'm talking about! Thanks, Colin!
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2007 at 7:54 am
Good information... thanks, Bob. Tracey may not be acknowledging my requests but I hope (s)he is getting something out of this...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2007 at 7:51 am
Heh... good catch... I "pasted" the wrong key ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2007 at 7:45 am
Heh... yeah... and I'm still wondering why anyone would even use the term "bashing" in relation to what I posted. And I certainly wasn't trying to "eat at" anyone.
So, James,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2007 at 7:32 am
Heh... sorry about that... saw the recent post and didn't check the dates on the history. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 1, 2007 at 7:27 am
You feel "bashed" by anything on this thread?
Most folks express some urgency when they post a question and your's is likely interesting... All...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 31, 2007 at 9:47 pm
He's gotta load all the data into a staging table, anyway... why not use it? End result will be the same except the switch will be much, much faster...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 31, 2007 at 9:44 pm
You bet... thanks, for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 31, 2007 at 9:40 pm
I'm not sure you're telling the whole story... if the 800 million rows is a staging table, of sorts, why not just add a "present" column to it and update...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 31, 2007 at 9:19 pm
Johnathan's code is good... but check the performance and resource usage when compared to the numbers-table solution that Remi squeezed off...
Hey Remi... nice loop on the table creation 
--Jeff Moden
Change is inevitable... Change for the better is not.
August 31, 2007 at 9:13 pm
Viewing 15 posts - 55,216 through 55,230 (of 59,072 total)