QUICK LINKS
Support
Issue Tracker
[Services]
Questions
[uAchieve 4.5 Applications]
[uAchieve 5.0 Application]
[uAchieve 5.1 Application]
Transferology
TES
[Training & Conferences]
Accessibility
The u.select Connector must access several DARS (or u.achieve) tables to provide the course equivalency and degree audit functionality.
Accessing Database Tables
Handy Hint
The sql statements executed by the u.select Connector do not prepend a database, user or schema prefix to the table name. An example select statement executed by the Connector looks like this:
select jobid from job_queue_list
When the Connector's database user (i.e. identified in the connection Url or data source definition) is different than the database user that actually owns the DARS tables, you need to ensure the u.select Connector has the correct visibility and permission to properly access the DARS/u.achieve tables.
Table Visibility
Depending on your database you may need to use synonyms, views or aliases to the DARS/u.achieve tables.
Table Permission
You may need to grant permissions/privileges specifically to the database user specified in the Connector's connection Url or data source definition.
Required Tables for the Connector's database user
Your DBA should use one of the following pages to understand the required tables and permissions for the Connector's database user:
- DARS - Required DARS Tables
- u.achieve - Required u.achieve Tables
Degree Audits from u.select through the Connector
Your DBA should review one of the following pages to understand the relationship between the Connector and your degree audit environment:
- DARwin Audits - Connector and DARwin audits
- u.achieve Audits - Connector and u.achieve audits
Overview
Content Tools