Archives of the TeradataForum
Message Posted: Fri, 10 Nov 2000 @ 18:17:49 GMT
We are in the process of converting several Oracle databases over to Teradata v2.3. We use a front-end data access tool, Business Objects, which requires a repository database to store its internal objects. The user heirarchy created in Teradata is:
dbc sysdba repositorydb db1 db2 ...
The issue we're facing is end users must connect to the repository and then their query is run against one of the databases (db1 or db2, etc). Thus the default database for the end users is required to be "repositorydb". This is forcing us to append the database owner to each object within the data access tool (e.g. db1.tableA). It also forces the administrator for the data access tool to be changing their default database depending on what they are doing.
With Oracle this could all be handled on the database side through the use of Public Synonyms (e.g. db1.tableA is aliased as tableA).
I'm wondering how others using Teradata may be dealing with this issue.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|