Message-ID: <297DCD5CCA4AD411A246009027F646B3016C117E@netmail> From: Graeme Slogrove <Graeme@na.co.za> Subject: RE: [RadiusNT] RadiusNT and SQL Server Replication Date: Thu, 30 Nov 2000 07:56:31 +0200
Sure - you have to ensure your database tables have "NOT FOR REPLICATION"
set on each of the index keys that may be affected in both locations.
You then also need to seed the indexes on each side using different values.
SQL Server 2000 does this automatically now, but for 7.0 it's still a manual
--- Graeme Slogrove, BSc (Eng) Elec (Wits) Chief Information Officer, NetActive Internet Tel: 011-719-0333 Fax: 011-719-0444 Support: 011-719-0300
-----Original Message----- From: Chris Stone [mailto:firstname.lastname@example.org] Sent: 30 November 2000 02:15 To: 'email@example.com' Subject: [RadiusNT] RadiusNT and SQL Server Replication
Anyone have this setup and running - RadiusNT 3 and SQL Server 7.0. Have 2 radius and 2 SQL servers - a pair of each at 2 separate locations. Each Radius server uses it's local SQL server for the primary database connection. In setting up SQL merge replication, the initial snapshot goes fine and the replication will work quite nicely for a few days and then we start getting replication failures - primarily due to violations of index keys.
Anyone have this type of configuration running successfully that might be able to provide a bit of insight into how to resolve these issues?
Chris Stone, MCSE WebConnects, Inc. email: firstname.lastname@example.org web: http://www.wcox.com
This is a user supported list. If you require assistance from IEA Software's Support Engineers, please check out our Support resources at http://www.iea-software.com/support.
For more information about this list (including removal) go to: http://www.iea-software.com/support/maillists/liststart .