Omni Loader Docs
  • OVERVIEW
    • About
    • Getting Started
    • Databases
    • Performance considerations
    • Prerequisites
  • Project Wizard
    • General
    • Database List
    • Favorites
    • Review
  • Project types
    • Full Table Copy
    • Data Compare & Sync
    • Change Data Capture
    • Overview
  • Project Options
    • General
    • Performance
    • Databases
    • Mapping
    • Logging
    • Troubleshooting
  • Table Options
    • Columns
    • WHERE clause
    • Partitioning
    • Cut-off
    • Options Override
  • Global Settings
    • Overview
  • Automations
    • Overview
    • JSON job specification
  • Connections
    • Amazon RedShift
    • Analytics Platform System
    • Synapse Dedicated Pool
    • CockroachDB
    • CSV
    • Databricks
    • DB2 iSeries
    • DB2 LUW
    • DB2 zOS
    • Greenplum
    • Google AlloyDB
    • Google BigQuery
    • MariaDB
    • MySQL
    • Netezza
    • NuoDB
    • ODBC
    • Oracle
    • Parquet
    • PostgreSQL
    • Snowflake
    • Sybase ASE
    • Sybase IQ
    • SQL Server
    • Teradata
    • Vertica ODBC
    • Fabric Lakehouse
    • Fabric Warehouse
    • Azure SQL Database
    • V-ORDER Fabric Lakehouse Optimization
Powered by GitBook
On this page
  • Connection Details
  • Connect using
  • DSN
  • Connection string
  • Username
  • Password
  • Include views as tables
  1. Connections

Netezza

PreviousMySQLNextNuoDB

Last updated 10 months ago

Connection Details

Connect using

DSN

Select this option if you have a pre-configured DSN for Databricks. DSNs are a convenient way to store connection information in a named location and can be easily managed within your operating system.

Connection string

‍Choose this if you prefer to directly enter a full connection string. This string includes all necessary details such as host, port, and credentials.

Username

Enter the username that has access rights to the Netezza database.

Password

Enter the password corresponding to the username provided.

Include views as tables

If you want to include views in the migration and treat them as tables, check this option. This can be useful for migrations where the view's data needs to be replicated along with the tables.