Viewing 15 posts - 32,146 through 32,160 (of 59,099 total)
Jim Murphy (10/26/2011)
With outlook, my wife didn't know where I was planning to be.
BWAA-HAAA!!!! Some fellows I know would consider that to be a feature! 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2011 at 11:09 pm
Actually, that's a better decision than the VIEW. Thanks for the feedback and glad to help.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2011 at 11:06 pm
Sure... you'll probably need to remove the WHERE clause in the first CTE. You can use such a WHERE clause when you select from the view. Be well...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2011 at 4:39 pm
Nope... I was going to suggest it but didn't think it would work in your situation... I though you were doing long haul stuff.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2011 at 2:16 pm
memostone86 (10/26/2011)
Jeff Moden (10/26/2011)
@memostone86,Are you all set on this or do you still need help?
Hello Jeff, thanks for reply. I am still working on this.
I understand your requirements and I'll...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2011 at 10:09 am
Why are you reposting your original post? Did you even try the code I posted?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2011 at 10:08 am
IIRC, CDs only handle about 750MB... it would take quite a few to handle a 200GB backup. Single layer DVDs can hold a bit over 4 GB. Double...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2011 at 7:01 am
steveb. (10/26/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2011 at 6:55 am
It splits the Hierarchy path back to ID's. Each ID can be a part of several "paths" and the only way to accumulate the total "cost" associated with each...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2011 at 6:52 am
Are you all set on this or do you still need help?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2011 at 6:23 am
I guess my recommendation would be BINARY(1) and BINARY(2).
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2011 at 8:22 pm
You can't BULK INSERT from a table simply because BULK INSERT wasn't designed to do such a thing.
What you need is a good splitter... please see the following...
http://www.sqlservercentral.com/articles/Tally+Table/72993/
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2011 at 8:04 pm
dajonx (10/21/2011)
Right now on our 100 Mbps WAN connection, it takes about six hours to transfer the full SQL backup to the backup site....
...
...
Does anyone have any suggestions?
Yep......
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2011 at 7:55 pm
Sorry for the delay... there were a couple of posts ahead of you...
--Pretend that this is your dbo.ApplicationBldTypes table...
IF OBJECT_ID('TempDB..#ApplicationBldTypes','U') IS NOT NULL
...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2011 at 7:45 pm
I hope "RestOfData" isn't too wide for you to add an index to in both tables. Here's your original test data and a non-RBAR solution...
Declare @OriginalTable table(OT_ID int identity...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2011 at 7:19 pm
Viewing 15 posts - 32,146 through 32,160 (of 59,099 total)