We are pleased to announce the general availability of SQL BI Manager 2.2. Existing users may access through the IDERA Customer Portal. New Users may download the trial version from the IDERA Website.
This enhanced monitoring feature allows the user to turn on continuous logging of queries being executed on the SSAS instance. It allows users to quickly identify bottlenecks by providing the ability to look at a point in time of user activity and resource consumption. This feature is configurable such that you can turn it on and off. For example, suppose you need to do some bench marking and want to run a set of queries and monitor their execution, you could turn the capture on and then off when you were done. You can also specify thresholds that will be used to limit the queries being captured. Often times users only care about long running or resource consuming queries. The user is also able to specify a retention period for the historical queries. This will keep the size of the repository database down as old data is groomed off.
The product administrator can control access at the user level to instances as well as the level of privilege. For example, I have 10 users and 5 of them are developers. I can grant them access to only the development instances. When they log in they will only see those 5 instances in the product. All alerts, configuration information, etc. for those instances are displayed. They will not see any information regarding the other instances in the UI.
A user that has SSRS instances that are deployed using a scale-out architecture can now register the instances the services are running on and the instance the SSRS repository database is running on. This provides the ability to monitor the performance and metrics associated with the SSRS nodes while still providing user activity information and reports executed across all nodes. Previously, this was not available.
In environments where the BI services are running on a cluster, the user can register the listener or cluster name. This makes the product cluster aware, such that the user does not have to register the active and passive instances on the cluster. If fail over occurs, BI Manager will still connect to the instance.
Another improvement, is instances that have been installed on a UDP (User-defined port) instead of the default one, you can register the instance with the UDP. This allows the application to communicate using the UDP instead of always looking on the default port for the service.