Viewing 15 posts - 61 through 75 (of 109 total)
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...
Chris Becker bcsdata.net
November 27, 2007 at 3:43 pm
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...
Chris Becker bcsdata.net
November 27, 2007 at 2:52 pm
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...
Chris Becker bcsdata.net
November 27, 2007 at 11:47 am
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...
Chris Becker bcsdata.net
November 27, 2007 at 11:12 am
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...
Chris Becker bcsdata.net
November 27, 2007 at 10:48 am
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',...
Chris Becker bcsdata.net
November 26, 2007 at 4:33 pm
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
Chris Becker bcsdata.net
November 26, 2007 at 3:56 pm
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...
Chris Becker bcsdata.net
November 26, 2007 at 3:49 pm
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...
Chris Becker bcsdata.net
November 26, 2007 at 3:27 pm
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 = N'', @creation_script...
Chris Becker bcsdata.net
November 26, 2007 at 3:22 pm
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...
Chris Becker bcsdata.net
November 20, 2007 at 12:16 pm
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...
Chris Becker bcsdata.net
November 20, 2007 at 8:23 am
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....
Chris Becker bcsdata.net
November 19, 2007 at 12:55 pm
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...
Chris Becker bcsdata.net
November 19, 2007 at 12:50 pm
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
Chris Becker bcsdata.net
November 19, 2007 at 12:42 pm
Viewing 15 posts - 61 through 75 (of 109 total)