SQL Server metabase

Data Integrity Suite
Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2025
Option Description
Data connection

Select the name of the data connection to associate with the metabase. If there is only one SQL Server JDBC data connection, it displays by default.

When you are adding a new metabase from a data connection, this value is automatically populated with the data connection's source selection.
Database server The address of the database server where the metabase will be created. This value is automatically populated with the database server value from the data connection.
SQL server administration user ID and password
  • SQL server administrator user ID: Specify the SQL Server system administrator user ID for the source server, which is used to create the metabase. The default is sa. This user must have privileges to create a database on the source system.
  • Password: Specify the SQL Server administrator password credentials. The password is not stored and is protected using Secure Sockets Layer (SSL).
Replication user ID and Password
  • Replication user ID: The replication user name associated with the database that contains the metabase. The default is rpuser for each metabase installed and cannot be changed. The first metabase installed creates the rpuser login and sets the default database context for rpuser. After the metabase is created, the replication user credentials will be used to connect to the database and will be associated with replicating data to the target.
  • Password: Specify the replication user password credentials. The password is masked by default. To see the password, click Show. To mask the password again, click Hide.
Metabase name The name of the metabase. By default, this is omnirep. You cannot have two metabases with the same name in the SQL Server instance.
Maximum transaction rows per user pool When the trigger-based capture type is selected, click this drop-down list and select the maximum number of transaction rows that can be allocated in each user's pool of rp_trans rows. The default is 400000.

If the maximum transaction rows limit is reached, the trigger fails. Each user is assigned a pool of rp_trans rows based on the user's session ID in SQL Server. When a new transaction is created in the trigger, the transaction attempts to reuse the rp_trans rows already allocated in the pool. Rp_trans rows are marked as free and available for reuse 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
Data logical name and Data size
  • Data logical name. Specify the name of the data file/device in which the metabase will be stored. By default, the file name is metabase_name_data. Use the default, or specify an alternate name.
  • Data size: Specify the size of the data file in MB. The default is 64MB.
    Note: These options are available when you click Retrieve Path.
Data physical name If you clicked Retrieve Path, specify the data physical name and path. By default, this is the location where the data logical file is created on SQL Server. For example, C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\metabase_name_data.mdf. Use the default or specify an alternate file path as needed.
Log logical name and Log size
  • Log logical name. Specify the name of the log file/device in which the metabase will be stored. By default, the file name is metabase_name_log. Use the default, or specify an alternate name.
  • Log size. Specify the size of the log file in MB. The default is 64MB.
    Note: These options are available when you click Retrieve Path.
Log physical name If you clicked Retrieve Path, specify the log physical name and path. By default, this is the location where the log logical file is created on SQL Server. For example, C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\metabase_name_log.ldf. Use the default or specify an alternate file path as needed.