Viewing 15 posts - 51,541 through 51,555 (of 59,102 total)
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
Yep... you're gonna have to put the result of the CTE into a temp table as a separate query... include a RANK column. Then, see the part about "Grouped...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 8:48 am
Chirag (3/24/2008)
My procedures get changed daily and i cant generate the alter script as iam using SQL 2005 RTM ( i cant change it).
Chirag,
I'd worry about that problem more...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 7:41 am
Jason Selburg (3/24/2008)
And there is probably an easier way to write this... 😀
That would be true, ol' friend... and, in this case, simpler means faster and easier to read to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 7:36 am
Just my 2 cents on this one... I've found that the WHERE NOT IN that Barry used is usually more performant than outer joins. The speed difference isn't huge...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2008 at 6:06 am
Viewing 15 posts - 51,541 through 51,555 (of 59,102 total)