Conductor4SQL is an advanced database management solution which permits organisations to effectively manage and synchronise a large number of Microsoft SQL instances with an unlimited number of databases, especially those which are dispersed over a large geographic area. A key advantage of this solution is that it can greatly reduce a lot of the frustration when managing multiple databases over erratic networks because of its automation capabilities.
You will encounter two terms that are used throughout this document and also when using Conductor4SQL. These terms are:
- Client - A Client is a remote instance of SQL server that is controlled by Conductor4SQL.
- Central server - A Central server is a standalone instance of SQL Server on which Conductor4SQL is installed. Typically, a Central server would be installed at a Head Office or Data Centre location that has the required network connectivity to all client servers. Details of the connectivity requirement is discussed in the Client pre-requisites topic.
Using Conductor4SQL offers considerable technical features that you can perform from a single point, including:
- Centralised Query Capabilities - You can retrieve data simultaneously from an unlimited number of dispersed SQL instances and consolidate, view or export the results.
- Centralised Command Capabilities - You can conduct database version control and make simultaneous metadata changes to an unlimited number of dispersed SQL instances, such as using DDL, DML.
- Centralised File Distribution Capabilities - You can send files of any type to an unlimited number of dispersed SQL instances simultaneously, such as DLL's, batch files and others. A concise record of files sent is maintained.
- Centralised Data Synchronisation - You can consolidate and synchronise data simultaneously on an unlimited number of dispersed SQL instances. This can also be used for central reporting purposes.
- Schema Comparison - You can obtain a concise and searchable list of differences between database structures (which includes tables, stored procedures, functions, views and constraints) — across all client servers.
- Centralised Auditing - You can audit all the above features plus DDL and security events that occur on an unlimited number of dispersed SQL instances. This is key to enforcing database version control including complete visibility of all activity occurring in your SQL environment.
- Data Recovery - Provides Disaster Recovery Management ensuring data is recoverable, even if no MS-SQL backups are available.
The content of this manual is intended to provide the user with the following information:
- What is required to install the Conductor4SQL system? — See the central server pre-requisites and the client server pre-requisites
- How do I install the Conductor4SQL system? - See the central server installation and client server installation guide
- How do I administer the Conductor4SQL system and edit settings? — See administration overview.
- How do manage, control and audit my installed clients? - See central console overview.
- How do I sync data from all my clients? - See data sync overview