Data Warehouse
The University of Arkansas Data Warehouse is a data repository made up of over 270 tables of legacy and historical data such as financial (DART, UPS, BASIS, Payroll, etc.) and academic (ISIS) data that is separate and distinct from the mainframe production databases. Warehouse data is copied from the live, production system, summarized, transformed, and then loaded into the Data Warehouse at regular intervals. Non-programmers will find easy access to this data from their desktops.
Accessing Data Warehouse
Access to the Data Warehouse requires an authorized signature from the department head (or person responsible for authorizing cost center expenditures) and is only available to academic and administrative users. No students will be authorized for access. The data warehouse is accessible from 7 a.m. to 6 p.m. weekdays and on weekends when maintenance is not scheduled. Call the IT Services Data Center at 575-2303 to verify accessibility on weekends.
To gain access to the Data Warehouse, complete and return the Data Warehouse Access Agreement form (PDF), selecting your Warehouse Access Software: BrioQuery, SAS, or Microsoft Access.
Data Warehouse passwords can be reset using PASSweb.
IT Services supports and recommends using Microsoft Access, BrioQuery or SAS, but the 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 Data Warehouse team, on the user's computer to connect to the Data Warehouse.
Microsoft Access is the most common product used to access the Data Warehouse. UARK users may also purchase site licenses for BrioQuery and SAS. BrioQuery is a sophisticated, client-server ad hoc query and reporting system that provides access for non-technical users. With BrioQuery, users can build queries and reports by clicking icons and manipulating objects and BrioQuery displays retrieved data in a tabular format, or build presentations that can include graphic elements and charts.
SAS is less expensive than BrioQuery, but not as user friendly.
Use the Online Site License Request to request BrioQuery or SAS.
Stopping a Data Warehouse Query
If you build a 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 and you will want to stop the query.
Troubleshooting
No Records Returned after 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 Data Warehouse Queries
Sometimes when running a lot of queries (or using more than one session at a time), the query program (i.e., BrioQuery, 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 Data Warehouse is either down, the server name is wrong, or your services file cannot be located. Contact the Data Warehouse staff by calling the Help Desk at 575-2905 or open an AskIT case.
Last Reviewed: