Viewing 15 posts - 286 through 300 (of 5,103 total)
If A is already distributor all is not lost. You can create a PULL Subscription on B and republish B to C.
Now Republishing does have limitations. If a new...
March 20, 2009 at 8:16 am
Amith Vemuganti (3/19/2009)
March 19, 2009 at 2:27 pm
steve smith (3/19/2009)
March 19, 2009 at 1:16 pm
Thanks for sharing.
Actually there are no much more efficient ways to do it, you are on the right track. This is one of the reasons identity columns and replication are...
March 19, 2009 at 12:45 pm
Well there is only one Queue Reader but you won't get rid of the distribution agents.
Queue reader are to propagate changes FROM Subscriber to Publishers.
Distributors go From Publisher...
March 19, 2009 at 10:11 am
homebrew01 (3/18/2009)
March 18, 2009 at 4:36 pm
Starting Point: http://msdn.microsoft.com/en-us/library/ms345146.aspx
March 18, 2009 at 4:28 pm
SET PARSEONLY ON
SET NOEXEC ON
-- Do your thing
SET PARSEONLY OFF
SET NOEXEC OFF
March 18, 2009 at 11:29 am
700 replication jobs ?
Is all of that in just one server ?
March 18, 2009 at 8:52 am
The problem with "all of its associated tables, columns and values" is "how far" do you want to go with it because there could be an FK pointing to another...
March 17, 2009 at 10:35 am
Do you have "Recursive Triggers" Enabled ?
March 17, 2009 at 10:25 am
The update stats job that should already be in your maintenance plan is critical to the performance of your applications, possibly more so than the rebuild indices job
This has always...
March 17, 2009 at 10:18 am
If the table is very small you will see that effect.
How many pages does your table has?
March 17, 2009 at 10:14 am
From BOL:
The following table lists the minimal amount of new data that should be in a table before you drop indexes.
Indexes..............................................Relative amount of new data
Clustered index only...............................30 percent
Clustered and...
March 17, 2009 at 10:02 am
Viewing 15 posts - 286 through 300 (of 5,103 total)