Create a new server for MS SQL Server - Connect_CDC - aws_mainframe_modernization_service - connect_cdc_mimix_share - Latest

Name

Use alphanumeric characters to specify a unique server name for use in the model.

DBMS Type

Select Microsoft SQL Server from the dropdown list.

DBMS version

DBMS Edition

Displays the MS SQL Server edition; Developer, Enterprise, or Standard.

Server name 

Specify the name of the server you want to model. Often, the value you enter here is the same as the host name of the system where SQL Server is installed.

DBMS instance port

JDBC Driver

Microsoft SQL Server is preselected in this field.

Driver Version 

View the JDBC Driver version. This information is obtained each time a connection to the database is made (including a Test Connection).

DBMS logon IDs and DBMS logon password

When you specify Microsoft SQL Server as the DBMS type, rpuser is available from the dropdown list for the DBMS logon ID; rpuser is the owner of each meta­base on this server. You specify meta database names in the Meta database field shown below.

• DBMS logon IDs—When you select rpuser as the DBMS logon ID, rpuser is the Default user and default Rep user. Note that both of these checkboxes are checked and grayed out.

• The Default user is what Connect CDC Director uses to connect to the server.

• The Rep user is what the kernel uses to connect to the server.

• DBMS logon password—You must enter a valid password for rpuser. If you do not, the install metabase process will fail. If you do not enter a password and leave the field blank, you will receive an error when you attempt to exit the Server Properties, Server dialog.

Metabase schema

Set to the owner of the metabase. It is the qualifier of the metabase tables, in the format qualifier.tablename. You cannot edit this field. This field is pre-filled with dbo.

Meta database

The name of the database Connect CDC Director uses to create its metabase objects.

You can install multiple metabases on the same instance of MS SQL Server. To facilitate this, specify a meta database name. You can specify a maximum of 50 alphanumeric characters. The first character must be alphabetic. The default value is omnirep. You cannot use any special characters from the following set:

`,~!@#$%^&*()-_+={}[]|\;:”’<>./? space

Enable Prepared Statements

If selected, prepared statements are enabled for the entire database server. A prepared SQL statement is a statement in which the steps to parse, analyze, validate, and determine the access path are only done once, when the statement is first prepared. On subsequent executions of the statement, the database has this information stored in memory and can skip the initial preparation steps. After a statement is prepared, only the column values change from one execution of the statement to the next.

Each table can have as many as seven prepared statements: one for insert, up to five for update, and one for delete. The first time an insert, update, or delete is encountered, the statement is prepared, added to the cache, and is used to update the table. The statements are kept in the cache until removed.

Using prepared statements provides a significant performance improvement when the same SQL statement is executed over and over. However, in some cases data for unchanged columns will be captured and sent across the network.

Individual tables can disable prepared statements. This is useful for managing the size of the cache file.

Database limit

Displays the maximum size allowed by the database for open statements in the cache. The Specified limit, below, cannot exceed this value. The correct value is provided after you run a Test Connection. To do so, right-click the server name, then select Test Connection.

Specified limit

Enter the maximum size allowed for open statements in the cache. When the statement cache is full, the least recently used statement is removed from the cache, closed, and destroyed. If Journal batching is enabled, prior to removing the statement, pending batch updates are executed, If the statement that was removed is later referenced, a new prepared statement is created and added to the cache.

Note the following:

• The default is 700.

• The minimum value is 7.

• The maximum value is specified in Database limit, above. If you set the specified limit to a value lower than the number of prepared statements in the model, performance may decrease.

Enable CDC

Select the check box to enable Connect CDC Change Data Capture (CDC).

• If this is a “clean” installation of Connect CDC, Enable CDC replication is enabled by default. Deselect Enable CDC, to use the trigger-based replication method.

• If this is an upgraded metabase, you must select Enable CDC to use the CDC replication method. If you do not select Enable CDC, the replication method is trigger-based (the default).

Max TRANS row

The maximum number of transaction rows that can be allocated in each users pool of rp_trans rows. If the Max TRANS rows limit is reached, the trigger will fail. Each user is assigned a pool of rp_trans rows based on the user's session id in MS SQL server. When a new transaction is created in the trigger, the transaction attempts, when possible, to re-use the rp_trans rows already allocated in the pool. Rp_trans rows are marked as free and available for re-use after the transactions have been successfully applied on all mapped targets. If there are no free rows available, a new block of rp_trans rows is allocated and added to the user's pool. The default is 400000.

Remote Machine Name or IP

Select this checkbox if you are creating a new remote server for MS SQL Server. Refer to Create a New Remote MS SQL Server. Specify the remote machine name or IP address. The remote machine name or IP address must be a valid machine name or IP address of the machine hosting the remote SQL Server instance. The remote machine name (or IP address), and the Server name establish the connection with the remote server. This is a required field.

CredentialManagement

Select a credential management provider that contains the login credentials for DBMS user IDs. Possible values are None and CyberArk. Selecting CyberArk enables the CyberArk Settings tab.

Model using metabase

Displays the name of the model. (Informational only)

Model version

Displays the version number, updated after each commit. (Informational only)

Metabase version

Displays the version of the metabase (for example, 40d). (Informational only)

GMT offset(minutes)

Displays the amount of time, in minutes, that local time differs from Greenwich Mean Time (GMT). For example, Boston is 300 minutes less than GMT. (Informational only)

CyberArk Settings tab 

Login ID

Unique identifier for default, rep, PDB root container, and additional user IDs used for DBMS logon. All the login IDs are displayed here, whether or not they use a credential manager.

Type

Identifies the credential manager that applies for a login ID. Possible values are None and CyberArk.

Configure...

Click Configure... to open the CyberArk Options dialog, which accepts changes in 2 fields to configure the CyberArk connection required to connect to CyberArk:

• Application ID: an application ID registered in CyberArk

• Query String: query string listing CyberArk fields like Safe, Object, Address, PolicyID, etc.