Viewing 13 posts - 16 through 28 (of 28 total)
rgarrett (9/15/2015)
October 24, 2015 at 1:19 pm
Why did you like it? Has it helped you to solve issues?
What was bad in it?
I like critics... don't be shy.:hehe:
September 12, 2015 at 8:12 am
I would consider BULK INSERT command to use in such trivial cases.
It could be automated to populate many tables in parallel instead of running sequentially SSIS packages.
Thanks! Nice article though!
September 11, 2015 at 1:53 am
Thanks for the rating and comment.
Just to make clear:
1.Trustworthy db option is disabled by default. Also, it will be set to OFF after detach/attach db operations. Enabling this property can...
September 5, 2015 at 3:05 am
stacylaray (3/25/2015)
March 29, 2015 at 12:59 pm
Hi,
I like the article, but there is a drawback in your solution. There is no proper error handling in powershell and related sql job step. If monitoring server fails to...
December 5, 2014 at 9:56 am
joe.tj (11/28/2014)
I used SSMS to generate scripts of logreader,ditribution and snapshot on the old distributor.
Then I modified this scritpt content with variables(etc $(Publisher),$(Subscriber)) .And...
December 1, 2014 at 12:16 pm
Anders_ss (11/27/2014)
November 27, 2014 at 12:28 pm
joe.tj (11/27/2014)
I make a test on a push replication following you steps.but it doesn't work.
1.the distribute job occurs error msg:Agent message code 20044. The subscription to publication 'PubTest' has expired...
November 27, 2014 at 12:20 pm
Misha_SQL (11/21/2014)
November 23, 2014 at 10:30 am
Hi Vj,
If you try provided scripts in the article with correct server names then it should work for you.
KEEP_REPLICATION should do the trick.
V.U.
November 20, 2014 at 12:58 pm
ninety3cents (11/20/2014)
I find this a little more complicated then it needs to be. Why not just initialized from a back up? That's how i've done it and its been...
November 20, 2014 at 12:53 pm
Viewing 13 posts - 16 through 28 (of 28 total)