Archives of the TeradataForum

Message Posted: Thu, 10 Jul 2003 @ 14:29:05 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

<-- Anonymously Posted: Thursday, July 10, 2003 10:23 -->

We started to actually map users between Microstrategy and Teradata. (i.e. Microstrategy Connection Mapping) Assigning multiple Teradata ID's (by appending prefix to the Microstrategy) to one Microstrategy ID with different prioritities based on the Microstrategy project they are using. We use the Microstrategy Command Manager to automate the Microstrategy userid administration and have a Teradata Script to create the Teradata ID's. On each Teradata ID we put in the Comment field the name of the Microstrategy user and we use account string expansion to identify the Microstrategy project.

It a lot of setup work as for each Microstrategy ID we can have up to 4 Teradata ID's. But we can run a report that tells us exactly how much Teradata Resources are being used by a given user. In addition, if we get long running or run-away queries, you can contact the end user for more details.

It seems the main downside is not on the Teradata side, but is on the Microstrategy side. Having so many connection mapping seems to slow down the Administration Desktop tool whenever you need to check on userid.

	<Prev	Next>		<<First	<Prev	Next>	Last>>