Using BI/Data Warehouse

IT Services supports and recommends using Microsoft Access or SAS EG, but the BI/Data Warehouse can also be accessed with any ODBC (Open Data Base Connectivity) compliant software product. An ODBC driver must be installed, typically by the BI/Data Warehouse team, on the user's computer to connect to the BI/Data Warehouse.

Microsoft Access

Microsoft Access is the most common product used to access the BI/Data Warehouse. SAS EG is a sophisticated, client-server query and reporting system that provides access for non-technical users.

Get instructions for BI/Data Warehouse in Microsoft Access


With SAS EG, users can build queries and reports, as well as graphic elements and charts. Stored processes can be built to reproduce reports to be displayed on the web as HTML. Faculty and non-administrative UARK users can purchase site licenses for SAS.

Stopping a BI/Data Warehouse Query

If you build a BI/Data Warehouse query and submit it, but forget to provide any selection (or limit) criteria, a "runaway" query can be created if the table(s) have a lot of records. In this case, you will want to stop the query.


No Records Returned after BI/Data Warehouse Query

Double check what you used as selection criteria. Selection data is case sensitive. Look at a sampling of the data you are wanting. If you are using dates, check to see if you are using the same date format.

Example: If you entered "19990125" (YYYYMMDD) as the date, but the table date format is (MMDDYYYY) 01251999, you will not get any records returned. If you are using multiple tables, double check what fields you are linking on. You might want to remove all the tables and then start adding (and linking) a table at a time. This may identify the table that is causing the problem (or give you some insight as to what you were doing wrong).

Locked Up and/or Error Messages While Running BI/Data Warehouse Queries

Sometimes when running a lot of queries (or using more than one session at a time), the query program (i.e. MS Access, SAS) gets lost. Log off and exit the software (you might also have to exit Windows or turn your computer off), then log back in and try running your query again. If you are hung up and are not able to log off, hold down the CTRL, ALT and DELETE keys to end your task.

"ODBC-connection to dwh32 failed" or "ODBC-call failed" Error Messages

The BI/Data Warehouse is either down, the server name is wrong, or your services file cannot be located. Please report this issue to the IT Help Desk.