Connect to and Query SQL Server Data in QlikView over ODBC

The CData ODBC drivers expand your ability to work with data from more than 200 data sources. QlikView is a business discovery platform that provides self-service BI for all business users in an organization. This article outlines simple steps to connect to SQL Server data using the CData ODBC driver and create data visualizations in QlikView.

The CData ODBC drivers offer unmatched performance for interacting with live SQL Server data in QlikView due to optimized data processing built into the driver. When you issue complex SQL queries from QlikView to SQL Server, the driver pushes supported SQL operations, like filters and aggregations, directly to SQL Server and utilizes the embedded SQL engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze SQL Server data using native QlikView data types.

Connect to SQL Server as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

Connecting to Microsoft SQL Server

Connect to Microsoft SQL Server using the following properties:

• Server: The name of the server running SQL Server.
• User: The username provided for authentication with SQL Server.
• Password: The password associated with the authenticating user.
• Database: The name of the SQL Server database.

Connecting to Azure SQL Server and Azure Data Warehouse

You can authenticate to Azure SQL Server or Azure Data Warehouse by setting the following connection properties:

• Server: The server running Azure. You can find this by logging into the Azure portal and navigating to "SQL databases" (or "SQL data warehouses") -> "Select your database" -> "Overview" -> "Server name."
• User: The name of the user authenticating to Azure.
• Password: The password associated with the authenticating user.
• Database: The name of the database, as seen in the Azure portal on the SQL databases (or SQL warehouses) page.

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

Populate a Chart with SQL Server Data

The steps below supply the results of an SQL query to a visualization in QlikView. In this article, you will create a bar chart with the query below:

1. Click File -> Edit Script (or click the Edit Script button in the Toolbar).
2. On the Data tab, select ODBC in the Database menu and click Connect.
3. Select the DSN (CData SQL Sys) in the resulting dialog. A command like the following is generated: ODBC CONNECT TO [CData SQL Sys];
4. Enter the SQL query directly into the script with the SQL command (or click Select to build the query in the SELECT statement wizard). SQL SELECT ShipName, Freight FROM Orders;

   Where possible, the SQL operations in the query, like filters and aggregations, will be pushed down to SQL Server, while any unsupported operations (which can include SQL functions and JOIN operations) will be managed client-side by the CData SQL engine embedded in the driver.

5. Close the script editor and reload the document to execute the script.
6. Click Tools -> Quick Chart Wizard. In the wizard, select the chart type. This example uses a bar chart. When building the chart, you have access to the fields from SQL Server, typed appropriately for QlikView, thanks to built-in dynamic metadata querying.
7. When defining Dimensions, select ShipName in the First Dimension menu.
8. When defining Expressions, click the summary function you want and select Freight in the menu.

9. Finish the wizard to generate the chart. The CData ODBC Driver for SQL Server connects to live SQL Server data, so the chart can be refreshed to see real-time changes. Live connections are possible and effective, thanks to the high-performance data processing native to CData ODBC Drivers.