Viewing 15 posts - 49,111 through 49,125 (of 59,099 total)
Sorry Gus, I have no idea what ORLY means...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 6:03 am
Lot's of good stuff there Gus... I just don't think any of it needs to audit the original insert... 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2008 at 3:20 pm
Thanks, Jack... must've been some latte in my coffee or sumthin':P
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2008 at 3:17 pm
Heh... that's what I was getting at... none of the methods has a huge advantage over the other which means it all becomes a personal preference for readability and understanding.
On...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2008 at 1:11 pm
I guess I don't understand why you would need to log the insert... if no changes occur at all, the original data is still available in the original table.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2008 at 1:08 pm
He was talking about me blazing through posts and missing stuff...:)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2008 at 1:05 pm
You're a very wise man, Mr. Jones. You sure I can't come to work for you? 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2008 at 1:04 pm
Heh... now that there's some funny stuff Mr. Young! 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2008 at 1:01 pm
Christopher Stobbs (7/22/2008)
HI All,Wow this has been fun:
I have tested all the solutions with 1Mil rows of Jack's Data and here is what happened:
Not trying to take anything away form...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2008 at 9:09 am
Jack Corbett (7/22/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2008 at 8:06 am
Christopher Stobbs (7/22/2008)
Results
Mine:
SQL Server Execution Times:
CPU time = 4219 ms, elapsed time = 9937 ms.
Yours:
SQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2008 at 8:02 am
jburkman (7/22/2008)
It's why every IT department should have one or two openings permanently available in case someone that's really valuable comes along. Identifying that person can be hard, and to...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2008 at 7:43 am
James Stover (7/22/2008)
Accounting says: IT = cost center.Shareholder says: maximize profits.
CIO says: freezing wages; outsourcing 1/2 the team.
And I'm supposed to be enthusiastic about this?
When it comes to losing good...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2008 at 7:37 am
Chris Morris (7/22/2008)
Top work, Jeff! It looks so much nicer in SQL2k5.
Top work yourself, Chris... it was a real bugger to pull off using 2k code, but you did it!...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2008 at 7:30 am
Chris Morris (7/22/2008)
I think this works but gosh it's pretty horrible...It would take another aggregated SELECT to bring in MAX or MIN DM_Source_Id.
Of course this is a SQL2k5 forum section...
Thank...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2008 at 7:17 am
Viewing 15 posts - 49,111 through 49,125 (of 59,099 total)