[dba-SQLServer] SQL Server Database Replication Between Two Servers

Paul,
  If you can upgrade the servers to 2005 (do this first in dev), then you
can utilize database mirroring wich is much easier to setup than replication
and seems to handle collisions a lot better.


On 2/26/06, Arthur Fuller <artful at rogers.com> wrote:
>
> I've been a bit tardy replying to messages on this list due to work-load,
> but if you haven't already had a satisfactory answer, try using a trigger.
> You will have to reference the other database explicitly of course, using
> the standard dot notation: ServerName.DatabaseName.TableName.
> HTH,
> Arthur
>
> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Paul
> Hartland
> Sent: January 31, 2006 7:07 AM
> To: dba-sqlserver at databaseadvisors.com
> Subject: [dba-SQLServer] SQL Server Database Replication Between Two
> Servers
> Importance: High
>
> To all,
> We have two servers (for the purpose of security lets call them SRV_1
> and SRV_2) which both have a copy of SQL Server 2000 on them, onto which
> I have placed a test database (Dbase_Rep).  When a user updates the
> database on SRV_1 I need the changes to also be made on SRV_2 either
> instantly or at a desired time interval.  I know this can be done and
> have had a quick play and almost got it there.
> Does anyone have an idiot proof step by step guide starting from scratch
> or know where I can get one from.
> Thanks in advance for any help on this.
>
> PAUL HARTLAND
>
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
>


--
-Francisco
http://pcthis.blogspot.com |PC news with out the jargon!
http://sqlthis.blogspot.com | Tsql and More...