These parameters are used by prepare, validate and remove with database=target dbtype=mssql (see Prepare Target Database, Validate Database and Remove Repstance Objects from Database). The login that is given in user needs the privileges that are described in Database Privileges.
| Parameter | Description |
|---|---|
| database | target. Required. |
| dbtype | mssql. Required. |
| generatesql | 1 makes prepare return the SQL script and change nothing. The default is 0: prepare creates the objects. validate does not use the parameter, and remove removes the objects whatever its value. |
| server | The host name or the IP address of the SQL Server. Required. |
| port | The TCP port of the SQL Server, usually 1433. Required. |
| user | The login that Repstance connects with. Required. |
| password | The password of the login. Required. |
| dbname | The database to prepare: the schema repi with the checkpoint tables is created in it. Give it always: without dbname the default database of the login is used, which is often master. |
A database that is not prepared:
repcli validate database=target dbtype=mssql server=db-tgt.example.com port=1433 dbname=testDB user=repuser password=Passw0rd123
[Invalid]: Database is not prepared for apply: [repi schema does not exist: 1]A prepared database:
repcli validate database=target dbtype=mssql server=db-tgt.example.com port=1433 dbname=testDB user=repuser password=Passw0rd123
[Valid]: Database TESTDB is validThe script that prepare returns with generatesql=1 is shown in Prepare Target Database.
The form “Database Settings” of an Apply Process for SQL Server has the fields “Server”, “Port”, “Username”, “Password” and “Database Name” (the list shows the databases of the server). “Copy Settings” takes the connection data of a process that exists already:
Fill in the form and click “Test connection”. The buttons that prepare the database are shown in Prepare Target Database:
Prev page:
Oracle as TargetNext page:
PostgreSQL as Target