Viewing 15 posts - 51,526 through 51,540 (of 59,091 total)
I just can't bring myself to believe in any test that uses RBAR as much as that :sick:
And, over a million rows, datatype isn't going to make much...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2008 at 12:01 am
Something less than a million rows at a time in order by the clustered primary key with a 10 second delay between million row updates.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 10:57 pm
I think I will stick with not in and not exists from now on.
Heh... Except on Tuesdays... that's when the "SQL Run Fast" button is automatically recycled to overcome all...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 9:26 pm
ALZDBA (3/25/2008)
Good old BOL did it again, thanks for the rectification.Here's a little test script I've found back from my test (sql7)
Just to demonstrate simple working of it.
Aye... nicely done,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 9:20 pm
BobAtDBS (3/25/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 9:15 pm
Thanks for the link, Adam... that reminded me where I put my test code... and I added "EXCEPTION" to it...
First, I just don't trust execution plans, estimated or actual... especially...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 8:53 pm
Matt Miller (3/25/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 7:36 pm
mrpolecat (3/25/2008)
It added ok but when I select from the file all the fields fall under one field with the field name being the first...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 7:33 pm
Heh... sure... Just ask Al Gore... he "built the internet" and he's a grandfather :P:P:P
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 6:12 pm
Carlos, your example would only fire the Insert Trigger once regardless of how many rows the Select returns. All inserted rows will be available in the INSERTED table available...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 5:02 pm
EDIT: Made a boo-boo... this originally said the following and I've corrected it below this white quote box... sorry for the mistake folks. :blush:
No... not with a linked...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 9:16 am
Heh... I'm the same way... Wise man once told me that "All claims require proof... extraordinary claims require extraordinary proof."
In the Navy, we said (cleaned up version) "Why sift through...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 9:10 am
Jason Selburg (3/25/2008)
Now...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 9:06 am
Adam Haines (3/25/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 9:05 am
Dunno if it's still true in 2k5, but when there are a large number of large image files as blobs, most folks recommend just storing the filename in the db...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 8:56 am
Viewing 15 posts - 51,526 through 51,540 (of 59,091 total)