Dbvisit Replicate communicates with both source and target database to replicate data. This communication includes reading and writing data through Data Source Name (DSN) configured using ODBC data source and drivers. A DSN for SQL server on source system is required by Dbvisit Replicate to successfully execute configurational scripts that prepares the target MSSQL environment for replication. On target system, a DSN with same name as source system is required by the APPLY service which interacts with target database to replicate changes of source database.
...
4. Select SQL server authentication and enter credentials of SQL server's user with admin rights.
5. Keep the default values and click on Next for two steps and then Test the connection.
...
| Note |
|---|
Installation instructions are available on same page. This download includes a script (build_dm.sh) to build ODBC driver manager. Please read instructions carefully and configure your system according to your environment requirement. |
Installation of ODBC driver will insert following record in /etc/odbcinst.ini file.
| Section | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Crosscheck whether this specification are inserted or not.
Once the installation is done, DSN can be created. To create DSN, login as root and create a DSN entry in /etc/odbc.ini file.Following is an example of DSN named "mstest"
| Section | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Once DSN is created. "isql" command can be used to test DSN. If DSN is working properly then isql command will return SQL prompt from where you can execute SQL statements on target database running on Windows machine. Following is the example of testing DSN testdb1.
| Section | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|