Commercial Database Connections

Commercial databases – Microsoft SQL Server and Azure SQL Database, Oracle and IBM Db2 LUW, SAP/Sybase ASE and SQL Anywhere – come with 7-day free trial for full access to anything. Then you get limited visual SQL query design and SQL generation, unless you pay for a small monthly subscription.

The process described here is for Data Xtractor, but it’s valid for all our products as well, with few exceptions: ER models are supported and generated only in Data Xtractor and Model Xtractor, while queries are not supported or generated in Model Xtractor.

How to Connect to a Microsoft SQL Server Database

Supported and tested versions are from 2008 to current. Your database must have been previously installed with a third-party tool. We recommend the free SSMS (SQL Server Management Studio), included in the SQL Server distribution kit.

1. Click on Connect > Open-Source Databases > Microsoft SQL Server. This will open the previous New Database Connection popup. Return here anytime with the Properties context menu command on your database node.
2. No need to install any data provider. System.Data.SqlClient driver is already part of .NET.
3. Enter your database Host Name. Type localhost or your machine name for a local database. Follow it by a back slash plus the name of the instance, eventually, like in “HP-TOUCH\SQLEXPRESS2012”. Default port number in SQL Server is 1443, but it could be different. Try to leave port number empty, it will be detected automatically.
4. Select the Authentication Type. With Server Authentication, fill-in a username and password, and leave Save Password checked. Default admin’s name in SQL Server is sa. Or use the Windows Authentication, to use computer’s logged-in user instead.
5. Connect through SSH if required. Follow the steps described separately below for SSH and come back to continue.
6. Select the list entry with your Database name. It should appear in the Database list when expanded, if previous parameters are correct. Or type the database name manually.
7. Select the database schema, usually dbo. Leave it empty, if you have multiple schemas and you want to import all of them (as for the AdventureWorks and WideWorldImporters database samples). Or select one or more schemas from the list. The list may have all schema names, with total number of tables in each.
8. Leave the default values for Connection and Query Timeout. Increase these values later on if you use a slow connection, or if your queries do not have enough time to complete.
9. Leave Other Properties as they are. Or pass additional connection string values, when in need.
10. Click on Test. This will check the number of tables and server’s version, as in the example. Do not continue until your connection has been properly verified as successful.
11. Click on OK. Wait for metadata to be collected. The popup will close and a database connection node will be created, with table child nodes. In Data Xtractor or Model Xtractor, some ER model diagrams will also be generated, and one will be opened on screen.
12. Click on Queries > Demo Queries > add demo queries. If you are not in Model Xtractor and want to play with some built-in SQL samples, this will open a popup with the missing queries.
13. Double-click on any model or query node. This will open it up on the right pane.

How to Connect to an Oracle Database

Support and tested versions are from 10g up. Your database must have been previously installed with a third-party tool. We recommend the free SQL Developer, included in the Oracle distribution kit.

1. Click on Connect > Open-Source Databases > Oracle. This will open the previous New Database Connection popup. Return here anytime with the Properties context menu command on your database node.
2. No need to install any data provider. Oracle.ManagedDataAccess.Client ODP.NET (Oracle Data Provider) managed driver, owned by Oracle, is included in the setup.
3. Enter your database Host Name and Port Number. Type localhost or your machine name for a local database. Default port number in Oracle is 1521.
4. Pass Oracle’s Instance name. Use XE if you use the local Express version.
5. Connect with your User Name and Password. Leave Save Password checked. Default admin’s name in Oracle is SYS.
6. Connect through SSH if required. Follow the steps described separately below for SSH and come back to continue.
7. Select the list entry with your Database name. It should appear in the Database list when expanded, if previous parameters are correct. Or type the database name manually.
8. Schema name is user’s name. In Oracle, you usually connect to your own schema, if not admin.
9. Leave the default values for Connection and Query Timeout. Increase these values later on if you use a slow connection, or if your queries do not have enough time to complete.
10. Leave Other Properties as they are. Or pass additional connection string values, when in need.
11. Click on Test. This will check the number of tables and server’s version, as in the example. Do not continue until your connection has been properly verified as successful.
12. Click on OK. Wait for metadata to be collected. The popup will close and a database connection node will be created, with table child nodes. In Data Xtractor or Model Xtractor, some ER model diagrams will also be generated, and one will be opened on screen.
13. Click on Queries > Demo Queries > add demo queries. If you are not in Model Xtractor and want to play with some built-in SQL samples, this will open a popup with the missing queries.
14. Double-click on any model or query node. This will open it up on the right pane.

How to Connect to an IBM Db2 Database

We support and we tested the LUW (Linux, Unix, and Windows) distribution, starting with version 10.5. Your database must have been previously installed with a third-party tool. We recommend the free SQL Workbench or DBeaver.

1. Click on Connect > Open-Source Databases > IBM Db2. This will open the previous New Database Connection popup. Return here anytime with the Properties context menu command on your database node.
2. You may need to install a data provider. Follow the separate steps described below for a free IBM.Data.DB2 driver. You can download and install the IBM Data Server Driver Package (DS Driver) from IBM’s website.
3. Enter your database Host Name and Port Number. Type localhost or your machine name for a local database. Default port number in DB2 is 50000.
4. Connect with your User Name and Password. Leave Save Password checked. Admin’s default username is db2admin.
5. Connect through SSH if required. Follow the steps described separately below for SSH and come back to continue.
6. Select the list entry with your Database name. It should appear in the Database list when expanded, if previous parameters are correct. Or type the database name manually.
7. Select the Schema for your Database. The list may have all schema names, with total number of tables in each.
8. Leave the default values for Connection and Query Timeout. Increase these values later on if you use a slow connection, or if your queries do not have enough time to complete.
9. Leave Other Properties as they are. Or pass additional connection string values, when in need.
10. Click on Test. This will check the number of tables and server’s version, as in the example. Do not continue until your connection has been properly verified as successful.
11. Click on OK. Wait for metadata to be collected. The popup will close and a database connection node will be created, with table child nodes. In Data Xtractor or Model Xtractor, some ER model diagrams will also be generated, and one will be opened on screen.
12. Click on Queries > Demo Queries > add demo queries. If you are not in Model Xtractor and want to play with some built-in SQL samples, this will open a popup with the missing queries.
13. Double-click on any model or query node. This will open it up on the right pane.

A free third-party .NET Data Provider may be required to be installed separately, as it is not included with any of our applications. Your Database Connection popup will open up with the Provider tab selected by default, if you need to install and select one dedicated provider.

1. Switch to the Provider tab.
2. Select one single provider from the list, if any. Check the info on screen, to see if it is tested or supported, and try to use eventually. Continue, if there is no provider in the list, or none can be used.
3. Download the free IBM Data Server Driver Package (DS Driver). The link sends you to IBM’s website.
4. Install this third-party product on your local computer. This should register the IBM DB2 .NET Data Provider (IBM DB2 Data Provider for .NET Framework 4.0) on your machine..
5. Click on the Refresh button. You should see and select the new IBM.Data.DB2 driver from the list, as in the previous image. A message in green will appear at the bottom, if everything ok.
6. Switch back to the Connection tab. Continue with the database setup from where you left.

How to Connect to a SAP/Sybase ASE Database

This commercial RDBMS, formerly owned by and known as Sybase, and owned today by SAP. ASE (Adaptive Server Enterprise), has also a free evaluation version. Supported and tested versions are from 16 up. Your database must have been previously installed with a third-party tool. We recommend the free I-SQL or DBeaver.

1. Click on Connect > Open-Source Databases > Sybase/SAP ASE. This will open the previous New Database Connection popup. Return here anytime with the Properties context menu command on your database node.
2. You may need to install a data provider. Follow the separate steps described below to download and install the free SAP/Sybase ASE .NET Data Provider, with the Sybase.Data.AseClient driver.
3. Enter your database Host Name and Port Number. Type localhost or your machine name for a local database. Default port number in SAP/Sybase ASE is 5000
4. Connect with your User Name and Password. Leave Save Password checked. Admin’s user name in SAP/Sybase ASE is sa by default.
5. Select the list entry with your Database name. It should appear in the Database list when expanded, if previous parameters are correct. Or type the database name manually.
6. Select the database schema, usually dbo. The list may have all schema names, with total number of tables in each. Connectivity is somehow similar to Microsoft SQL Server, because both ASE and SQL Server are actually derived from a previous version of Sybase.
7. Leave the default values for Connection and Query Timeout. Increase these values later on if you use a slow connection, or if your queries do not have enough time to complete.
8. Specify an optional Character Set to Other Options. chartset=utf8; is obviously for a UTF-8 encoding. Concatenate with extra connection string values, when in need.
9. Click on Test. This will check the number of tables and server’s version, as in the example. Do not continue until your connection has been properly verified as successful.
10. Click on OK. Wait for metadata to be collected. The popup will close and a database connection node will be created, with table child nodes. In Data Xtractor or Model Xtractor, some ER model diagrams will also be generated, and one will be opened on screen.
11. Click on Queries > Demo Queries > add demo queries. If you are not in Model Xtractor and want to play with some built-in SQL samples, this will open a popup with the missing queries.
12. Double-click on any model or query node. This will open it up on the right pane.

A free third-party .NET Data Provider may be required to be installed separately, as it is not included with any of our applications. Your Database Connection popup will open up with the Provider tab selected by default, if you need to install and select one dedicated provider.

1. Switch to the Provider tab.
2. Select one single provider from the list, if any. Check the info on screen, to see if it is tested or supported, and try to use eventually. Continue, if there is no provider in the list, or none can be used.
3. Download a free Evaluation Edition of SAP Adaptive Server Enterprise. The link sends you on SAP’s website.
4. Run the setup as Custom and install just ADO.NET. This should register the Sybase ASE Data Provider (.NET Framework Data Provider for Sybase ASE) on your machine.
5. Click on the Refresh button. You should see a new driver in the list.
6. Select the new Sybase.Data.AseClient driver from the list. It should look like in the previous image, with a message on green at the bottom.
7. Switch back to the Connection tab. Continue with the database setup from where you left.

How to Connect to a SAP/Sybase SQL Anywhere Database

Support and tested versions are from 16 up. Your database must have been previously installed with a third-party tool. We recommend the free SQL Central, included in the SQL Anywhere distribution kit.

1. Click on Connect > Open-Source Databases > Sybase/SAP SQL Anywhere. This will open the previous New Database Connection popup. Return here anytime with the Properties context menu command on your database node.
2. Or use File > Open Database File. Select a local or remote SQL Anywhere file, with the typical .db extension. You are then redirected to this same popup, with the File field populated with your selected path.
3. No need to install any data provider. We included the iAnywhere.Data.SQLAnywhere driver, from the SQL Anywhere 16 Data Provider, which supports version 17 as well.
4. Enter your database Service Name. There is one service instance per database.
5. Enter your optional File name. This may be already there from step 2.
6. Connect with your User Name and Password. Leave Save Password checked. Admin’s user name in SQL Anywhere is DBA by default, with sys password.
7. Select the list entry with your Database name. It should appear in the Database list when expanded, if previous parameters are correct. Or type the database name manually.
8. Leave Schema(s) blank. Or select the same schema name as your user name.
9. Leave the default values for Connection and Query Timeout. Increase these values later on if you use a slow connection, or if your queries do not have enough time to complete.
10. Leave Other Properties as they are. Or pass additional connection string values, when in need.
11. Click on Test. This will check the number of tables and server’s version, as in this example. Do not continue until your connection has been properly verified as successful.
12. Click on OK. Wait for metadata to be collected. The popup will close and a database connection node will be created, with table child nodes. In Data Xtractor or Model Xtractor, some ER model diagrams will also be generated, and one will be opened on screen.
13. Click on Queries > Demo Queries > add demo queries. If you are not in Model Xtractor and want to play with some built-in SQL samples, this will open a popup with the missing queries.
14. Double-click on any model or query node. This will open it up on the right pane.