Archives of the TeradataForum
Message Posted: Fri, 16 May 2003 @ 10:46:57 GMT
BO makes it easy to "connect the dots" for building join paths. In the installations that I have worked with, I have not see any automation for building object join paths.
Also on a different note... Most BO installations use a single user for all BO users. This means the BO server maintains multiple sessions for multiple users. We notices a huge degradation in performance when doing this.
BO has a thing called a PASS THRU that enables the BO server to pass the username and password to Teradata. The challenge is in managing usernames and passwords on both the BO and the Teradata side.
We have standardized the Username for all warehouse users and we use a single password for all users on the Teradata side. The users do not know the password. This enables the Teradata system to account for what users are running what queries. On the BO side they have their own passwords to maintain security. The TDAT password gets changed every 30 days.
Since most users are using BO we have only a small amount of users that need "Power User" access on the TDAT system so they receive another user id on the TDAT.
We have seen a great performance gain by doing this. I know that was a bit off subject but if you are working in a BO shop, this might come in handy....
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|