Viewing 15 posts - 55,816 through 55,830 (of 59,072 total)
From the FROM clause down, updates with joins look pretty much like what you'd find in a SELECT...
UPDATE t1
SET somecol =t2.somecol
FROM @Table1 t1,
@Table2 t2
WHERE t1.someothercol...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2007 at 8:31 pm
There's some sort of nasy ol' timeout... I always do a select-all and copy before I try to post... just in case...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2007 at 3:52 pm
Heh... good thread, huh?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2007 at 3:49 pm
You bet... thanks for the feedback!
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2007 at 2:02 pm
Better have a good list of logins and passwords, then
And figure out a really good way to change them in the code...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2007 at 7:11 am
| I followed the steps provided by Moden. I executed the bulk insert... |
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2007 at 6:55 am
If you really want to impress them, create an "External Data Range" that queries the database using a well written view and set it up to automatically update every ten...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2007 at 6:50 am
Heh... geek... ![]()
![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2007 at 12:07 am
Heh... then there's that ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2007 at 9:36 pm
And, just in case anyone is curious about how much the function will slow things down...
--===== Find a safe place to do this test using "real tables" because...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2007 at 8:31 pm
There IS a single magical update and you sure don't need a cursor ![]()
First... here's a little test data to play with as you...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2007 at 7:53 pm
Carsten,
Thanks for the detailed feedback. Hard to believe that someone has that particular attitude.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2007 at 7:08 pm
Thanks for the confidence, Bledu... not sure it would do any good, though... if I were to give a general example, someone would fail to apply the knowledge to a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2007 at 7:06 pm
So, Hickymanz... any feedback on the code I provided?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2007 at 7:05 pm
No... wasn't talking about external security... it's an internal security risk that would fail a PCI audit.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2007 at 6:24 am
Viewing 15 posts - 55,816 through 55,830 (of 59,072 total)