Search
Searching for multiple words only shows matches that contain all words.
Btr2sql
Reference
Latest Version
- BTR2SQL v7.0
- Getting Started
- Migration
- Reference
- Deployment & Support
Previous Versions
- BTR2SQL v6.1
- Product Overview
- Release Notes
- Quick Start
- Before you Begin
- Step by Step Migration Using the GUI Migration Utility
- GUI Migration Utility
- Menu bar
- Toolbar
- File Menu
- Table Menu
- Reports Menu
- Help Menu
- Main Screen Display
- 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
- Migration for Magic Users
- MigrateUniPaasData Command-line Tool
- MigrateUniPaasData.ini File
- 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
- What happens after your UniPaaS application is deployed?
- Migration Validator Tool for uniPaaS Applications
- Migrating when no DDFs are Available
- Migration Using the Command Line
- Command Line Migration Scenarios
- Configuration Settings
- BTR2SQL SDK
- Troubleshooting
- Copyright and Contacts
- BTR2SQL v6.0
- Product Overview
- Release Notes
- Quick Start
- Before you Begin
- Step by Step Migration Using the GUI Migration Utility
- GUI Migration Utility
- Menu bar
- Toolbar
- File Menu
- Table Menu
- Reports Menu
- Help Menu
- Main Screen Display
- 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
- Migration for Magic Users
- MigrateUniPaasData Command-line Tool
- MigrateUniPaasData.ini File
- 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
- What happens after your UniPaaS application is deployed?
- Migration Validator Tool for uniPaaS Applications
- Migrating when no DDFs are Available
- Migration Using the Command Line
- Command Line Migration Scenarios
- Configuration Settings
- BTR2SQL SDK
- Troubleshooting
- Copyright and Contacts