Logo
Theme Logo

Btr2sql

Reference

  • Supported Platforms
    • Btr2SQL v7.0.XXXXX.0
    • Btr2SQL v7.0.10675.0
    • Btr2SQL v7.0.10587.0
    • Btr2SQL v6.1.9604.0
    • Btr2SQL v6.0.9558.1

Latest Version

  • BTR2SQL v7.0
    • Getting Started
      • Product Overview
        • How It Works
        • What’s Included
        • Supported Backends
        • License Registration
      • Release Notes
        • BTR2SQL v7.0.XXXXX.0
        • BTR2SQL v7.0.10675.0
        • BTR2SQL v7.0.10587.0
      • Quick Start
        • Prerequisites
        • Licensing
        • Your First Migration
        • Performance Tips
      • Before you Begin
        • Prerequisites
        • Database Limitations
        • DDFs
    • Migration
      • Step by Step Migration Using the GUI Migration Utility
        • 1. Migrate Data to SQL backend using the Migration Utility
        • 2. Verify the Migration
        • 3. Substitute the Btrieve Access dlls
        • 4. Run Your Application
        • 5. Deploy the Application
        • 6. Optimize the Application for SQL
      • GUI Migration Utility
        • Menu bar
        • Toolbar
        • File Menu
        • Table Menu
        • Reports Menu
        • Help Menu
        • Main Screen Display
        • Setting Migration Preferences
        • Convert Data Files
      • Scenarios Using the GUI Migration Utility
        • A Basic Migration
        • Distributing Tables to a Different Database or Schema
        • Using a Custom Prefix or Postfix to Distinguish Tables
        • A Real-life Example
        • Pros and Cons of each Migration Option
      • Migration for Magic Users (Historical)
        • MigrateUniPaasData Command-line Tool
        • MigrateUniPaasData.ini File
        • Options to migrate a multi-directory UniPaaS application
        • Final steps in the UniPaas migration process
        • What happens after your UniPaaS application is deployed?
        • Migration Validator Tool for uniPaaS Applications
    • Reference
      • Configuration Settings
        • Intermediate (INT) Files
        • MDS INI File
        • MDS Global INI File
        • Environment Variables
        • Configuration Precedence
        • Configuration Methods
        • Configuration Files at a Glance
      • Command Line Utilities
        • MdsMigrateTable
        • MdsMigrateFile
        • MigrationValidator
        • MdsEncryptPassword
      • Migration XML Configuration
        • XML Structure Overview
        • Root Element
        • Table Element
        • Field Elements
        • Index Elements
        • Backend-Specific Elements
        • Examples
      • Unicode Support
        • WString and WZString Column Types
        • SQL Type Mapping by Backend
        • PostgreSQL Database Setup
        • Oracle Database Setup
        • MS SQL Server Setup
        • Mixed Environments
      • Programmers Guide
        • Btrieve Data Concepts
        • BTR2SQL SDK
        • What’s in the Programmers Guide?
        • Key Benefits for Developers
        • SDK Components Overview
        • Getting Started with the SDK
        • What’s Next?
    • Deployment & Support
      • Deploying Your Application
        • Software Vendor vs. In-House Deployment
        • Runtime File Setup
        • XML Deployment for New Installations
        • Login Credentials and Authentication
        • Production Tracing Configuration
        • Testing Before Deployment
      • Troubleshooting
        • Migration Report
        • Migration Driver Trace
        • Runtime Driver Trace
        • Turning on application logging
        • Startup Trace
        • External Tools
      • Copyright and Contacts
        • Corporate Head Office
        • California Office

Previous Versions

  • BTR2SQL v6.1
    • Product Overview
      • Supported Database Drivers
        • BTR2SQL for Microsoft SQL Server
        • BTR2SQL for Oracle
        • BTR2SQL for PostgreSQL
      • Installed Files
      • License Registration
    • Release Notes
      • BTR2SQL v6.1.9604.0
        • New Features
        • Bug Fixes
    • Quick Start
      • Prerequisites
      • Licensing
      • Your First Migration
        • Pre-migration: Validate the DDFs
        • Step 1 - Migrate data to SQL backend using Btr2SQL
        • Step 2 - Post-Migration: Check migration using Migration Validator
        • Step 3 - Replace Btrieve Access dlls
        • Step 4 - Test
        • Step 5 - Deploy the application
      • Hardware considerations
      • Utilizing Function Executor
    • Before you Begin
      • Prerequisites
      • Database Limitations
      • DDFs
        • Handling variant records
        • The IN DICTIONARY clause
        • Nullable columns and the True-Null extra byte
        • Restart the Pervasive.SQL engine after modifying table definitions
      • Validate Data Definition Files using DDF Validator
        • DDF Validator command-line syntax
        • DDF Validator errors
        • Sample output from the DDF Validator tool
      • Hardware Considerations
      • Utilizing Function Executor
    • Step by Step Migration Using the GUI Migration Utility
      • 1. Migrate Data to SQL backend using the Migration Utility
        • Login to the target database
        • Select and migrate files
        • What happens during the migration?
      • 2. Verify the Migration
      • 3. Substitute the Btrieve Access dlls
      • 4. Run Your Application
      • 5. Deploy the Application
      • 6. Optimize the Application for SQL
    • GUI Migration Utility
      • Menu bar
      • Toolbar
      • File Menu
        • Select File.DDF
        • Select Database
        • Attach
        • Detach
        • Login
        • Preferences
        • Exit
      • Table Menu
      • Reports Menu
        • Migration Report
        • Clear Migration Report
      • Help Menu
        • BTR2SQL Help F1
        • Index
        • Quick Start Guide
        • Quick Start Video
        • Mertech on the Web
        • About
      • Main Screen Display
        • All
        • None
        • Invert
        • Valid Btrieve Files
        • Valid SQL Tables
      • Setting Migration Preferences
        • Overwrite Existing Tables Without Warning
        • Erase Table Before Migration
        • Require Btrieve Data Files
        • Prompt For Btrieve Owner If Needed
        • Migration Report File Name
        • Append to Existing Migration Report
        • Migration Trace File
        • File Name
        • Level
        • Runtime (debug) Trace File
        • Set Field Defaults
        • Set Data Type Mapping
      • Convert Data Files
        • Options Tab
        • Get Server Name from Login
        • Get Schema Name from Login
        • Get Database Name from Login
        • OEM to ANSI Translation
        • OK
        • Fields Tab
        • Name
        • Type
        • SQL Type
        • Binary
        • Offset
        • Size
        • Dec
        • Null
        • Default
        • Indexes Tab
        • Field Name
        • Desc
        • Case
        • Properties and Storage (Oracle Only)
        • Table Operations
        • Copy Data to Table
        • Create Table
        • Drop Table
        • Truncate Table
        • Browse Btrieve Data
        • Browse SQL Table
        • Index Maintenance
        • Specify Btrieve Ownership
        • Tablespaces
        • Btrieve Data Files
        • Create Text File for Loader
        • Batch File Location
        • SQL Loader Option
        • In the Grid
        • Adjust Sequence Definition
        • Enable Trigger to Handle Auto-Increment and Inverse Key
        • Handling of AutoInc Fields
        • Disable Trigger to Handle Auto-Increment and Inverse Key
        • Generate
        • Table Definition Files from Btrieve/Pervasive.SQL
        • Generate SQL Script for Creating Tables
    • Scenarios Using the GUI Migration Utility
      • A Basic Migration
        • What happens during runtime?
        • Common folder layouts
      • Distributing Tables to a Different Server, Database, or Schema
        • Other options
      • Using a Custom Prefix or Postfix to Distinguish Tables
        • Specifying the path to the INT files
        • What happens at runtime?
      • A Real-life Example
      • Pros and Cons of each Migration Option
        • Migrate each folder to a different server
        • Migrate each folder to a separate schema (users on Oracle)
        • Migrate each folder using a different table prefix or suffix
      • Recap
    • Migration for Magic Users
      • MigrateUniPaasData Command-line Tool
      • MigrateUniPaasData.ini File
        • MagicIni
        • [Logical Names]
        • [Temp Tables]
      • Options to migrate a multi-directory UniPaaS application
        • Creating the migration files
        • Creating the MigrateUniPassData mds.ini files
        • Option 1: Migrate each directory to a different server
        • Option 2: Migrate each directory to a different database
        • Option 3: Migrate each directory to a different schema (user on Oracle)
        • Option 4: Choose a unique table prefix (or postfix) for each directory
      • Final steps in the UniPaas migration process
        • Creating the MigrateUniPaasData.ini files
        • Creating the MigrationValidator_uniPaas.ini files
        • One more IMPORTANT consideration
      • What happens after your UniPaaS application is deployed?
        • Creating tables on the fly
        • Deleting tables
        • B_DROP_FILE
        • B_TRUNCATE_FILE
        • Creating a new regional store
        • Using a table-prefix
        • In a separate database
      • Migration Validator Tool for uniPaaS Applications
    • Migrating when no DDFs are Available
      • MdsMigrateFile Command-line Tool
        • Improving the conversion process
    • Migration Using the Command Line
      • MdsMigrateTable
        • Command-line syntax
        • XML Config File
      • Migration Validator
    • Command Line Migration Scenarios
      • First-time migration
      • Schema update
    • Configuration Settings
      • INT files
        • Sample INT file
      • mds.ini file
        • Sample mds.ini file
        • Consolidating INT files on the client
        • Specifying the target backend
        • Automatic application login
        • Segregating tables using a prefix or postfix
        • Using MS SQL Filegroups
      • mds_global.ini file
        • Sample mds_global.ini
      • Setting global and folder specific values programmatically
        • MdsSetSetting
        • How does MdsSetSetting work?
        • Example
        • MdsGetSetting
      • Precedence of configuration settings
    • BTR2SQL SDK
      • Runtime dll with extended APIs
        • How do I use the extended APIs?
      • Migration dll
        • How do I use the migration APIs?
      • Supported Btrieve API Functions
      • Additional MDS status codes
      • Extended DDF Data Types
        • B_CREATE API
        • SQL Login and Direct Query Execution
        • Fast Inserts
        • Driver Trace Control
        • Schema Functions (DTI Function Support)
        • Migration Functions
        • Additional Btrieve APIs
        • Accessing Both Btrieve and SQL Backends
        • Visual Basic Linking:
    • Troubleshooting
      • Migration Report
      • Migration Driver Trace
      • Runtime Driver Trace
      • Turning on application logging
        • Tracing driver calls from BTR2SQL using the Preferences dialog box
        • Tracing driver calls with environment variables
        • Tracing driver calls with registry settings
        • Tracing driver calls with mds_global.ini settings
        • Tracing driver calls using MdsSetSetting
        • Driver Trace Control Tool
      • Startup Trace
      • External Tools
        • Dependency Walker
        • Identifying statically loaded dll dependencies
        • Examining your application at runtime
        • Process Monitor
        • Blog Topics
    • Copyright and Contacts
      • Corporate Head Office
      • California Office
  • BTR2SQL v6.0
    • Product Overview
      • Supported Database Drivers
        • BTR2SQL for Microsoft SQL Server
        • BTR2SQL for Oracle
        • BTR2SQL for PostgreSQL
      • Installed Files
      • License Registration
    • Release Notes
      • BTR2SQL v6.0.9558.1
        • Bug Fixes
      • BTR2SQL v6.0.9526.0
        • New Features
        • Bug Fixes
      • BTR2SQL v6.0.9465.0
        • New Features
        • Bug Fixes
      • BTR2SQL v6.0.8817.0
        • New Features
        • Bugs Fixed
      • Version 5.3
        • MSSQL
      • Version 5.2
        • MSSQL
        • Oracle
        • PostgreSQL
        • GUI Migration Utility
        • Command-line Migration Tools
        • APIs
        • General
      • Version 5.1
        • License
        • Support for Btrieve 6.15
        • PostgreSQL client library
        • FUJITSU COBOL
        • Support for Microsoft SQL Server Filegroups
        • Migration Utility
        • SQL
        • Support for SQL Case Identifier
        • Tracing
        • CACHE
      • Version 5.0
        • Server Support
        • Tracing
        • Migration Utility
      • Version 4.5
        • Btrieve API Support
        • Migration
        • SDK
        • mds_global.ini
        • Misc
        • Tools
      • Version 4.2
        • Server Support
        • Tracing
        • Btrieve API Support
        • Misc
        • SDK
      • Version 4
        • Server Support
        • Tracing
        • Btrieve API Support
      • Version 3
        • Performance and Usability Improvements
        • Mertech SDK for BTR2SQL
        • New validation tools
    • Quick Start
      • Prerequisites
      • Licensing
      • Your First Migration
        • Pre-migration: Validate the DDFs
        • Step 1 - Migrate data to SQL backend using Btr2SQL
        • Step 2 - Post-Migration: Check migration using Migration Validator
        • Step 3 - Replace Btrieve Access dlls
        • Step 4 - Test
        • Step 5 - Deploy the application
      • Hardware considerations
      • Utilizing Function Executor
    • Before you Begin
      • Prerequisites
      • Database Limitations
      • DDFs
        • Handling variant records
        • The IN DICTIONARY clause
        • Nullable columns and the True-Null extra byte
        • Restart the Pervasive.SQL engine after modifying table definitions
      • Validate Data Definition Files using DDF Validator
        • DDF Validator command-line syntax
        • DDF Validator errors
        • Sample output from the DDF Validator tool
      • Hardware Considerations
      • Utilizing Function Executor
    • Step by Step Migration Using the GUI Migration Utility
      • 1. Migrate Data to SQL backend using the Migration Utility
        • Login to the target database
        • Select and migrate files
        • What happens during the migration?
      • 2. Verify the Migration
      • 3. Substitute the Btrieve Access dlls
      • 4. Run Your Application
      • 5. Deploy the Application
      • 6. Optimize the Application for SQL
    • GUI Migration Utility
      • Menu bar
      • Toolbar
      • File Menu
        • Select File.DDF
        • Select Database
        • Attach
        • Detach
        • Login
        • Preferences
        • Exit
      • Table Menu
      • Reports Menu
        • Migration Report
        • Clear Migration Report
      • Help Menu
        • BTR2SQL Help F1
        • Index
        • Quick Start Guide
        • Quick Start Video
        • Mertech on the Web
        • About
      • Main Screen Display
        • All
        • None
        • Invert
        • Valid Btrieve Files
        • Valid SQL Tables
      • Setting Migration Preferences
        • Overwrite Existing Tables Without Warning
        • Erase Table Before Migration
        • Require Btrieve Data Files
        • Prompt For Btrieve Owner If Needed
        • Migration Report File Name
        • Append to Existing Migration Report
        • Migration Trace File
        • File Name
        • Level
        • Runtime (debug) Trace File
        • Set Field Defaults
        • Set Data Type Mapping
      • Convert Data Files
        • Options Tab
        • Get Server Name from Login
        • Get Schema Name from Login
        • Get Database Name from Login
        • OEM to ANSI Translation
        • OK
        • Fields Tab
        • Name
        • Type
        • SQL Type
        • Binary
        • Offset
        • Size
        • Dec
        • Null
        • Default
        • Indexes Tab
        • Field Name
        • Desc
        • Case
        • Properties and Storage (Oracle Only)
        • Table Operations
        • Copy Data to Table
        • Create Table
        • Drop Table
        • Truncate Table
        • Browse Btrieve Data
        • Browse SQL Table
        • Index Maintenance
        • Specify Btrieve Ownership
        • Tablespaces
        • Btrieve Data Files
        • Create Text File for Loader
        • Batch File Location
        • SQL Loader Option
        • In the Grid
        • Adjust Sequence Definition
        • Enable Trigger to Handle Auto-Increment and Inverse Key
        • Handling of AutoInc Fields
        • Disable Trigger to Handle Auto-Increment and Inverse Key
        • Generate
        • Table Definition Files from Btrieve/Pervasive.SQL
        • Generate SQL Script for Creating Tables
    • Scenarios Using the GUI Migration Utility
      • A Basic Migration
        • What happens during runtime?
        • Common folder layouts
      • Distributing Tables to a Different Server, Database, or Schema
        • Other options
      • Using a Custom Prefix or Postfix to Distinguish Tables
        • Specifying the path to the INT files
        • What happens at runtime?
      • A Real-life Example
      • Pros and Cons of each Migration Option
        • Migrate each folder to a different server
        • Migrate each folder to a separate schema (users on Oracle)
        • Migrate each folder using a different table prefix or suffix
      • Recap
    • Migration for Magic Users
      • MigrateUniPaasData Command-line Tool
      • MigrateUniPaasData.ini File
        • MagicIni
        • [Logical Names]
        • [Temp Tables]
      • Options to migrate a multi-directory UniPaaS application
        • Creating the migration files
        • Creating the MigrateUniPassData mds.ini files
        • Option 1: Migrate each directory to a different server
        • Option 2: Migrate each directory to a different database
        • Option 3: Migrate each directory to a different schema (user on Oracle)
        • Option 4: Choose a unique table prefix (or postfix) for each directory
      • Final steps in the UniPaas migration process
        • Creating the MigrateUniPaasData.ini files
        • Creating the MigrationValidator_uniPaas.ini files
        • One more IMPORTANT consideration
      • What happens after your UniPaaS application is deployed?
        • Creating tables on the fly
        • Deleting tables
        • B_DROP_FILE
        • B_TRUNCATE_FILE
        • Creating a new regional store
        • Using a table-prefix
        • In a separate database
      • Migration Validator Tool for uniPaaS Applications
    • Migrating when no DDFs are Available
      • MdsMigrateFile Command-line Tool
        • Improving the conversion process
    • Migration Using the Command Line
      • MdsMigrateTable
        • Command-line syntax
        • XML Config File
      • Migration Validator
    • Command Line Migration Scenarios
      • First-time migration
      • Schema update
    • Configuration Settings
      • INT files
        • Sample INT file
      • mds.ini file
        • Sample mds.ini file
        • Consolidating INT files on the client
        • Specifying the target backend
        • Automatic application login
        • Segregating tables using a prefix or postfix
        • Using MS SQL Filegroups
      • mds_global.ini file
        • Sample mds_global.ini
      • Setting global and folder specific values programmatically
        • MdsSetSetting
        • How does MdsSetSetting work?
        • Example
        • MdsGetSetting
      • Precedence of configuration settings
    • BTR2SQL SDK
      • Runtime dll with extended APIs
        • How do I use the extended APIs?
      • Migration dll
        • How do I use the migration APIs?
      • Supported Btrieve API Functions
      • Additional MDS status codes
      • Extended DDF Data Types
        • B_CREATE API
        • SQL Login and Direct Query Execution
        • Fast Inserts
        • Driver Trace Control
        • Schema Functions (DTI Function Support)
        • Migration Functions
        • Additional Btrieve APIs
        • Accessing Both Btrieve and SQL Backends
        • Visual Basic Linking:
    • Troubleshooting
      • Migration Report
      • Migration Driver Trace
      • Runtime Driver Trace
      • Turning on application logging
        • Tracing driver calls from BTR2SQL using the Preferences dialog box
        • Tracing driver calls with environment variables
        • Tracing driver calls with registry settings
        • Tracing driver calls with mds_global.ini settings
        • Tracing driver calls using MdsSetSetting
        • Driver Trace Control Tool
      • Startup Trace
      • External Tools
        • Dependency Walker
        • Identifying statically loaded dll dependencies
        • Examining your application at runtime
        • Process Monitor
        • Blog Topics
    • Copyright and Contacts
      • Corporate Head Office
      • California Office
  • Docs »
  • BTR2SQL v7.0 »
  • Configuration Settings »
  • Intermediate (INT) Files »
  • Database Related INT Tokens

Database Related INT Tokens¶

This section documents all INT file tokens related to database and schema configuration for BTR2SQL.

  • Schema_Name
  • Database_Space_Name
  • Number_DF_Fields
  • Hints
  • Optimize_Scheme
  • Permanent_INT
  • Filegroup_Table
  • Filegroup_Index
  • Filegroup_Text