Post reply

Stopping an application using sql server2005

  • September 14, 2006 at 5:19 am

    #170353

    I am a dba for a sql server 2005 server, and recently some users have been given the business intellegence tools for use on their own servers.

    Since then i have been encountering timeouts etc, and after investigation i have found out it is those users with BI.  They are copying all the data from this server to theres which is causing issues.

    I cannot have the tools taken off them as it is a business requirement and they need read access to this server too.

     

    What i was wondering is if anyone knows of a way of setting something up to allow the users to connect but not to connect via BI?

     

  • September 14, 2006 at 7:02 am

    #660362

    I think you need to talk with BI users/developers about the BI task (loading data etc) schedule. If there is time period that the db is not heavily used, schedule the BI task at that time. Just kicking off BI connections will affect the BI app, and may be not a good solution.

    If you really need to kick off BI connections, you can try the following two ways :

    1) Use event notification, monitor log in event and if the client is BI, KILL the connection.

    2) Or have a job runs frequently to check sysprocesses. IF you find processes's "program name" is BI app, Kill it.

    1) needs more work but it can kill the connection immediately when its logged in. 2) is easy to implement but it has some delay due the schedule.

     

     

     

  • September 14, 2006 at 8:55 am

    #660427

    Thanks for the advice.

    I have chatted to the users and they can be quite un-cooperative so i will opt for kicking the app out for the time being.

     

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply