Unlike other vendor BI tools, it appears Microsoft SSRS has not integrated Teradata Queryband feature (preferrably w/ Teradata .NET Data Provider) which allow dynamic parameter passing (i.e. user and application info) at the connection/transaction level for database workload management monitoring and goverance.
We got the Expression-based Connection Strings to work with SSRS and successfully passed a UserId via Teradata QueryBand parameters in .NET Data Provider for Teradata. Theoretically, we could pass any QueryBand information to Teradata using this methodology, using a mix of hard-coded values, user selections, or environment/report variables.
However, there are two MSFT limitations to note regarding the ECS which are quite a burden:
•Requires embedded data sources (can’t maintain in a shared location)
•Prevents metadata retrieval of columns in data set until run time (major issue!)
- Essentially would have to use native TD data source create report referencing columns in data set, and then convert into ECS
- Any updates to the report might require converting the connections string back to the native connection, perform modifications, and then convert back to ECS