Introduction
This article explains how to connect FME to a Sybase database using an ODBC connection. While ODBC is a viable option, we recommend using the FME SAP Sybase Adaptive Server Enterprise (ASE) Reader/Writer if your organization supports JDBC connectors.
For JDBC-based connection instructions, refer to: SAP Sybase Adaptive Server Enterprise (ASE) Reader/Writer.
Requirements
- Sybase ODBC Driver (SQL Anywhere Client)
- Windows OS
-
Access credentials for your Sybase database
-
JDBC connector (optional but recommended)
Step-by-step Instructions
1. Download SQL Anywhere Database Client
Visit the SAP website and download the SQL Anywhere Database client
After downloading, launch the installer and follow the prompts to install.
2. Open the ODBC Manager
To create an ODBC data source, navigate to:
C:\Windows\System32\odbcad32.exe
3. Add a New Data Source
- Go to the System DSN or User DNS tab and click Add.
- Choose the SQL Anywhere 12 ODBC driver from the list.
- Set a Data Source Name (you will use this name later in FME).
- Enter the required database parameters (host, port, username, etc.).
- Use the Test button to confirm the connection is successful.
4. Connect to Sybase in FME
In FME Workbench, add a new reader:
- Format: ODBC 3.x
-
Parameters:
- Database: Enter the Data Source Name created earlier
- Username/Password: Enter your MySQL Credentials
- Click the ellipsis button next to Table to list available tables
See ODBC 3.x Reader/Writer documentation
5. Verify Connection
If the list of tables appears, FME has successfully connected to Sybase.
Optional: Manual Table Entry
If the connection appears in the FME log but no tables are listed:
- You can manually type the name of the table into the Table List field
- To load multiple tables, separate each name with a space (eg. table1 table2 table3)
This workaround is useful for partial ODBC implementations or limited metadata access.
Troubleshooting
-
Can’t see the ODBC driver?
Ensure the 64-bit version was installed and that you are using the 64-bit ODBC Manager (not the 32-bit one in SysWow64). -
Tables don’t appear in FME?
Double-check that the Data Source Name is entered exactly as configured in the ODBC Manager and that credentials are correct.
Note: we would recommend using the FME SAP Sybase Adaptive Server Enterprise (ASE) Reader/Writer to connect to your Sybase database, if your organisation has the option of using JDBC connectors. Refer to the SAP Sybase Adaptive Server Enterprise (ASE) Reader/Writer documentation for more details.
Installing the Correct Driver
First you need to make sure you have the Sybase ODBC driver. You can download one from Sybase for free from here:
SQL Anywhere Database Download Client
You will want to select the 64-bit MSI Installer so that it’s compatible with 64-bit FME.
Download and run the installer.
Creating an ODBC Data Source
Next you need to set up an ODBC dataset. To do this find the windows ODBC Manager located at:
C:\Windows\System32\odbcad32.exe
Then select "ADD" on the System or User DSN tab, and when prompted select the "SQL Anywhere 12 ODBC Driver". You will then be prompted to enter a 'Data Source Name' of your choosing (name doesn't matter but you will need to remember it for later on) and enter database parameters. The dialog also allows you to test that the connection works properly. Once this is correctly set up you can access your Sybase database via FME.
Connecting in FME
Back in FME add an ODBC reader. When setting up the reader on the parameters tab enter the name you gave the Data Source in the ODBC Manager in the 'Database' field and enter a user name and password. Then clicking on the [...] next to table should open up a list of the available tables in the database.
If you can view the tables you know FME is able to connect.
If you are still not seeing the table list but do notice in the logfile that you are connecting, then it is possible to just type the name of the table you are interested in, e.g. "myTable", in the Table List text box. For multiple tables just separate them with a blank space.
Clicking on OK should add a reader with the associated feature types to your workspace.