Re: Monitoring Impact of a User in SQL Server

Access does not really limit the damage they can do. At least it will be read only but they can still issue any queries they want. Profiler or Trace will allow you to see what each connection is doing. Check out each in BooksOnLine for more details.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"iaingblack" <iaingblack@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:692D3E10-260A-4F16-B733-9035139D518F@xxxxxxxxxxxxxxxx
Ha, yeah. I know we are kinda asking for trouble, but, question is really how
much! The users will be using an access frontend so they cant do too much
damage(!), but it would be nice to know how much of an impact it is having.
Each user will be connecting using a generic read-only login account so just
looking for a way to measure this and see if it is saturating the server.

I will try what you have suggested. I didnt actually realise SQL Server had
the available logging/performance tools to restrict and monitor activity in
this way. So, i'll set up a trace and keep my fingers crossed.

Thanks for the reply and advice.
Cheers

"Andrew J. Kelly" wrote:

Anytime you allow direct adhoc access you run the risk of someone doing
something that will impact performance. But that doesn't mean they will but
adhoc query access is usually a path to trouble:). If they will connect
once a day you can find out the SPID and then run a trace filtered on that
SPID to see the reads and cpu their queries will use and go from there.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"iaingblack" <iaingblack@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:85A15AB9-62A2-48FD-96A5-9D4C13724B47@xxxxxxxxxxxxxxxx
> Hi all,
>
> Quick question. At my current job, we are looking to install an Access
> frontend that connects to our main database. This would involve > everyone
> using the front-end to access the main SQL Server using a read-only > user
> account. The only concern is how this will affect performance.
>
> Is there any quick way to profile and monitor if this is creating a big
> drain on the database or if there is any problem in doing it this way?
>
> Thanks a lot.
> Iain



.

Relevant Pages