MDS File¶
mds.ini file¶
The mds.ini file contains the location of the INT files, schema, server and database name, login information, and table pre and postfix values. The Btr2SQL drivers use the mds.ini file in conjunction with the INT files at runtime. Some of the tokens in the mds.ini file are also used during migration:
Migration Utility: uses the INT-Folder, Table-Prefix, and Table-Postfix tokens (for examples, refer to Scenarios using the GUI Migration Utility .
MDSMigrateTable and MigrateUniPaasData: use all of the tokens. Command-line tokens override those in the mds.ini file (for examples, refer to Options to migrate a multi-directory UniPaaS application).
One copy of the mds.ini file can be placed in each folder where the application’s data files are usually stored. The mds.ini file contains the following tokens. All the tokens are optional.
Token |
Description |
Allows you to |
---|---|---|
INT-Folder |
Path to the INT files |
Consolidate INT files in one directory |
Server |
The server name |
Identify the target backend for a group of files rather than storing the information in each INT file or obtaining the information at runtime |
Database |
The database name |
Identify the target backend for a group of files rather than storing the information in each INT file or obtaining the information at runtime |
Schema |
The schema name (not used in Oracle) |
Identify the target backend for a group of files rather than storing the information in each INT file or obtaining the information at runtime |
UseTrustedConnection |
Rely on Windows authentication, yes or no. The default is no. (MSSQL only) |
Store login information so a Login dialog box is not required |
User |
User name. If UseTrustedConnection is yes, the User and Password values are ignored |
Store login information so a Login dialog box is not required |
Password |
A 128-bit encrypted value obtained with the command-line tool MdsEncryptPassword, which can be found in the bin folder of the Mertech driver installation |
Store login information so a Login dialog box is not required |
Table-Prefix |
Text to prepend to the table name during migration |
Create unique table names when migrating multiple directories with the same files names to the target server |
Table-Postfix |
Text to append to the table name during migration |
Create unique table names when migrating multiple directories with the same files names to the target server |
FilegroupTable |
Filegroup for table data (MSSQL only) |
Specify a filegroup for table data, indexes, or for text, ntext, image, xml, varchar(max), nvarchar(max), and varbinary(max) fields. |
FilegroupIndex |
Filegroup for indexes (MSSQL only) |
Specify a filegroup for table data, indexes, or for text, ntext, image, xml, varchar(max), nvarchar(max), and varbinary(max) fields. |
FilegroupText |
Filegroup for large fields (MSSQL only) |
Specify a filegroup for table data, indexes, or for text, ntext, image, xml, varchar(max), nvarchar(max), and varbinary(max) fields. |
A sample mds.ini file is shown below. Entries under a specific heading (e.g., heading [SQL_BTR]) are only used for that driver (e.g., driver MS SQL). The driver’s default value is used when a value is left empty. Spaces are ignored around the equal sign. All settings and values are case insensitive. A more detailed description of each setting is provided in the next section.
Sample mds.ini file¶
[SQL_BTR]
INT-Folder=..\IntFiles_SQL
Server=mssql\sql2008
Database=testdb
Schema=dbo
UseTrustedConnection=no
User=mydomain\\me
Password=4c8fe10aad3
Table-Prefix=proj1\_
Table-Postfix=
FilegroupTable=TABLES
FilegroupIndex=INDEXES
FilegroupText=LOBFIELDS
[ORA_BTR]
INT-Folder=..\IntFiles_ORA
Server=orclsrv
User=me
Password=4c8fe10aad3
Table-Prefix=proj1\_
Table-Postfix=
[PGS_BTR]
INT-Folder=..\IntFiles_PGS
Server=pgsqlsrv:5432
Database=testdb
User=me
Password=4c8fe10aad3
Table-Prefix=proj1\_
Table-Postfix=
NOTE: A sample mds.ini file can be found in the installation folder (<Program Files>\Mertech Data Systems\DB Drivers\Btrieve\sdk\samples).