Viewing 15 posts - 1 through 15 (of 222 total)
A few random extra points: there are some issues with snapshots for reporting purposes - you can't back them up and you can't use FTI for your reporting. Conversely, FTI is supported...
Paul Ibison
Paul.Ibison@replicationanswers.com
August 11, 2006 at 9:50 am
Correct - the article was written 2 years ago and has been reposted.
I'll work on an update which brings database mirroring / database snapshots into the equation, and also...
Paul Ibison
Paul.Ibison@replicationanswers.com
August 11, 2006 at 9:47 am
Alternatively you could capture the update in a publisher trigger and write to an audit table, and then replicate this table as per usual. Not as performant as the previous...
Paul Ibison
Paul.Ibison@replicationanswers.com
May 4, 2006 at 6:37 am
If you're using transactional replication on SQL Server 2005, there is an alternative option that'll avoid the problems you face - you can initialize a subscriber using a backup of...
Paul Ibison
Paul.Ibison@replicationanswers.com
May 4, 2006 at 6:33 am
For the replication frequency, please look at the schedule of the synchronizing agent (merge or distribution, depending on your type of replication).
The agent history will tell you if there...
Paul Ibison
Paul.Ibison@replicationanswers.com
May 4, 2006 at 6:27 am
Please have a look at this article for more info: http://www.replicationanswers.com/AddColumn.asp
Rgds,
Paul Ibison, SQL Server MVP
Paul Ibison
Paul.Ibison@replicationanswers.com
April 13, 2006 at 5:34 am
You'll need to use queued updating subscribers.
Rgds,
Paul Ibison (www.replicationanswers.com)
Paul Ibison
Paul.Ibison@replicationanswers.com
June 23, 2005 at 2:05 pm
The three factors to consider are the transaction retention period, the publication retention and the history retention. If they're all longer than the timeout then you're ok. To check, run
sp_helpdistributor...
Paul Ibison
Paul.Ibison@replicationanswers.com
June 23, 2005 at 8:41 am
It depends on what your replication setup is like as to whether a complete snapshot is created. By default, using sp_addarticle in transactional replication, followed by running the snapshot agent,...
Paul Ibison
Paul.Ibison@replicationanswers.com
June 23, 2005 at 2:45 am
Merge replication relies on uniqueness of GUIDS so there is a unique index placed on the GUID column (having the rowguid attribute) but this is not the same as a...
Paul Ibison
Paul.Ibison@replicationanswers.com
June 22, 2005 at 3:09 am
The servername is hardcoded into too much metadata to be able to move the publisher from one server to another and have it work, unless the names are identical. In...
Paul Ibison
Paul.Ibison@replicationanswers.com
June 21, 2005 at 9:27 am
Recreating from scratch and having all the subscribers resubscribe would definitely work but would be my last resort. If you can create the new server with the same name as...
Paul Ibison
Paul.Ibison@replicationanswers.com
June 21, 2005 at 3:12 am
Have a look in BOL (Books on line) for unicode. Really the multiple language requirements are satisfied using unicode datatypes. The collation in this case will be relevant for specifying...
Paul Ibison
Paul.Ibison@replicationanswers.com
June 20, 2005 at 1:38 pm
As we can't put triggers on system tables, I would think that only polling solutions would be applicable.
Incidentally, you probably know this, but there are already applications (eg Redgate)...
Paul Ibison
Paul.Ibison@replicationanswers.com
June 20, 2005 at 1:27 pm
Replicating tables and stored procs is the same in SQL 2005 as it was in SQL 2000 - transactional, snapshot, merge etc. There are loads of new features, and one...
Paul Ibison
Paul.Ibison@replicationanswers.com
June 19, 2005 at 3:00 pm
Viewing 15 posts - 1 through 15 (of 222 total)