There are a number of good reasons to upgrade to BI4.1 SP3.
However based on discussions with many customers, this one will make many BI admins happy. It has been one of the more requested little features for some time.
Kill session is finally here!
The CMC Sessions page has been modified to list out individual sessions for each user, with the ability to force end any one or all of a user’s sessions.
You will also notice that we list the client type that affects the session, for example Information Design Tool
You can select multiple sessions for a user and end them all at the same time. Note that we cannot get finer granularity than “BI Launhcpad”, since a user could be using CR, Web Intelligence and other tools in that sessions.
Also notice the session ID listed. This ugly looking string can be used by the administrator to reference the audits and logs to further trace down to what the user is doing, and help you isolate problematic sessions to keep those from occurring in the future.
Having said that, session management has been greatly cleaned up with BI4.1 SP2, and the feedback I have heard from customers in this regard has been very positive, so I very much hope that you will not need to spend much time in this screen.
The columns can also be sorted to help you quickly find old sessions, where you can list oldest sessions first.
One thing to be aware of is that ending a session does not end jobs that were initiated by that session. If a user has sent a big request to the database in a report refresh, ending the user’s BI session does not cancel the database request. It only frees the user’s BI session.