Administering SQL ID Connections

  • We use Business objects on our SQL servers that allows users to create infinate queries. I have seen one user using 78% of the CPU at one time. We are set to give access to 2000 plus users which in my mind will bring the server to its knees. Business Objects has a time out parameter but I was wondering if there was anything in SQL server that could limit the amount of CPU usage per connnection? I know we will have to scale up but I would like to limit the amount being used on the server.

  • Check

    query governor cost limit setting on server.

  • That's your best option. No "throttle" per se, which is something I've asked for. Send that to sqlwish@microsoft.com and maybe we'll get it some day.

    Be sure you test this and let your users know that long runing queries may not run. This will "socialize" and prevent some issues by letting them know in advance. Make you are clear that very complex queries will be affected. This might not be acceptable for your business, so don't just change this.

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

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