Good place for white papers & tech content.

http://www.microsoft.com/windowsserver2003/technologies/clustering/resources.mspx

Tricky part is setting up hardware & shared drive array. Other than that it is pretty easy, plenty of...

Make sure erp vendor supports mirror. ADO.NET still needs to be mirror aware and special conn string config needs to be in place. Come time to failover to mirror, you...

Database mirroring is a nice addition to SQL2005 and definitely has it's place for acheiving high availability. However, I highly recommend the following for all my clients -

-Clustering for local/'perfectly...

Transactional replication isn't built for batch processing like this, hence the name 'transactional'. Your options are limited if you are forced to keep in trans repl. You will get...

I can only assume this is transactional repl? I would attempt the following:

1) remove indexes from table at subscriber - reapply when delivery complete

2) drop article from pub, when process...

changes will not be saved if any active subscriptions exist on that publication. you should drop subscription for table, then drop article.

then add article in script:

exec sp_addarticle @publication = N'DabaseSiteData',...

Ah ha - so your publisher is SQL 2000... yes - just uncheck that checkbox. When you script out your publication it will appear as @del_cmd = 'none'

Chris

looks ok - just change @del_cmd = N'none' in your sp_addarticle call

you may want to drop subscription for table, then drop article from publication, and finally add article (sp_addarticle) back...

Certainly - make sure all you repl stored procedures are in subscriber db. If lost you can recreate by executing the following on publisher, then take output and exec on...

When you add article you can specify 'none' for @del_cmd:

exec sp_addarticle @publication = N'PubName', @article = N'TableName', @source_owner = N'dbo'

, @source_object = N'TableName', @type = N'logbased', @description =...

No worries. You are almost there. I don't know if you are SQL2000 or 2005 - so I will include both scripts to create a no-sync subscription (see below). Kill...

Yes you can do this.

When you configure - do not allow snapshot agent to initialize. Select subscriber already has schema & data - do this for both publishers and...

What are you using - snapshot replication?

Consider transactional replication - you deliver a snapshot only once to sync or initialize the subscriber, after that only changes will replicate....

Snapshot repl will be tricky. I suggest using transactional replication - then only changes are delivered individually - you can even set distribution agent schedule to run once per day...

You have a view on both pub & subscribers exposing merge article info:

sysmergeextendedarticlesview

and a table w/ 1 row for each merge pub defined in pub & subscr db's

sysmergepublications

ChrisB MCDBA

MSSQLConsulting.com