Viewing 15 posts - 47,806 through 47,820 (of 59,102 total)
Except for things like what Marios pointed out, I avoid table variables like the plague not only because of their "single record" execution plan, but because they are also more...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2008 at 11:20 am
Guess I'll throw the testing I've done in the past into the ring... 🙂
The testing below takes the "display" out of the picture using a throw-away variable of the DATETIME...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2008 at 11:11 am
Chris Harshman (10/10/2008)
Gary Johnson (10/10/2008)
It would be interesting to see what performed better. 😉
Actually the DateAdd/DateDiff method seems to perform slightly better (like 6 milliseconds better over 25,000 rows) than...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2008 at 10:09 am
ggraber (10/10/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2008 at 7:43 pm
rbarryyoung (10/10/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2008 at 7:36 pm
J (10/10/2008)
"Thorn"wut?
"Thorn" is actually the name of a character in the ASCII character set. A good description and history of the character is found at the following URL...
http://en.wikipedia.org/wiki/%C3%9E
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2008 at 7:31 pm
Alex Grinberg (10/10/2008)
You could use select * from sys.objects where is_ms_shipped = 0 as well. I am not INFORMATION_SCHEMA fan. This is personal preference.:D
Heh... I forgot about that. I'm...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2008 at 7:24 pm
Micheal, Noeld... thank you very much for the help. You guys are the best. 🙂 I'll let you know how it all turns out if they actually follow...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2008 at 1:58 pm
Michael Earl (10/10/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2008 at 1:33 pm
noeld (10/10/2008)
or cook your own scripts to do it.
Cool... I can do that. Thanks for the heads up on that.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2008 at 1:17 pm
noeld (10/10/2008)
1. Take a full backup of each DB, Compress it and start log shipping it. You can d that "NOW".
2. After you are...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2008 at 11:12 am
Michael Earl (10/10/2008)
If so, keep everything simple. Stop the services on...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2008 at 10:59 am
My apologies... I forgot to say that they're all SQL Server 2000 Enterprise Edition servers which also means that I just posted to the wrong bloody forum... :blush: I don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2008 at 8:45 am
jcrawf02 (10/10/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2008 at 6:20 am
Just to give physical representation of Kenny's suggestions...
--===== Create a temporary demonstration table and populate it with duplicated info
-- This is not part of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2008 at 5:54 am
Viewing 15 posts - 47,806 through 47,820 (of 59,102 total)