Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

sql replication

Has anyone attempted merge replication with the SQL backend? I understand the issues it would bring with multiple pollers, but I'm wondering about using it to synch the DB for a hot-standby poller in another geographical site.

Find more posts tagged with

Accepted answers

All comments

In theory it could be done, but you need to have some SQL experince to make it work.

The first problem you would run into would be the Node, Interface, and VolumeIDs. When you add a node to the Orion system, Orion lets the Database Server pick the next Identity number to represent that device. Be default, this "Identity" field, starts at 1 and is incremented each time a device is added to the table. If you let replication merge together two database, you would have overlap between the identity fields in the two Orion database.

The trick would be, before you added any devices to the database, to set the initial value for the Identity field to a high number, like 1,000,000 on the second database, 2,000,000 on the second database, 3,000,000 on the third database, etc This way when you let replication merge the databases together, there would not be any overload in the identity fields.

You would also need to change Identity type from Yes, to Yes, except for replication.

BK
Nobody Special