I'm in the process of setting up replication for our SQL Server 2000
database to an external site.
Let me explain what we have setup and what we want to do:-
We have one site as our main server that we want to replicate in real time
to a backup/mirror server. This main database is accessed via a web server
using ASP, etc. I've managed to setup a transactional replication so that
this database is published and pushed to our external mirror server. The
database has tables that contain IDENTITY values as primary keys. All was
working fine, until i setup the mirror database with identity rows too. I
did this because we want to be able to use the mirror database if the main
server goes down.
Can people explain what i need to setup to get this working correctly and if
it is possible?
I've looked into setting up our main server database with the identity
columns set to NOT FOR REPLICATION, but i'm not entirely sure if this is
correct.
We also need to make sure that any changes, additions, etc. done on the
mirrored database, are resubmitted/pushed back to the main server once its
back up. I take it i need to implement an updatable subscription to do this?
How do i do that? Also, do i need to setup the mirror database with NOT FOR
REPLICATION identity columns aswell for this to work?
Any advice is much appreciated.
Thanks in advance,
Dan Williams
"Dan Williams" <dan_wi...@newcross-nursing.com> wrote in message
news:aomlfu$9gj$1...@knossos.btinternet.com...