There aren't any PROS to this.

Whats the business driver for this work?

What do your applications do, what resources do they need?

What availability is required by the business?

The answers to these...

If you manage your SQL Servers from workstations then install SSMS on your workstations and there is need to install SSMS on the server.

If you manage your SQL Server by...

Can you describe what the service is and why you don't want to use a functional account to access the database?

Any service that requires access to SL Server should be...

http://www.microsoft.com/technet/prodtechnol/sql/2005/library/security.mspx

There's no easy fix for security, but I would say that - I'm a SL Server Security Consultant.

PM me if your business wants a comprehensive approach.

Joseph

I stand corrected.

Another option is in your design - use stored procedures to run the select, and add a step to log the access.

Look at your link again, first find a reference to mirroring, then try to find a reference to snapshots.

They are different things.

In SQL 2000 you have three options:

Run Profiler (as suggested)

Create a trigger on the table

Run SQL in C2 audit mode

As with all solutions, you'll get a more comprehensive answer, if...

In this version you want to use Integration Services to haul your data over and into your warehouse.

1 - Grant a group membership of that role, use other groups/roles for other permissions - mix and match to suit.

2 Use a while loop and run through the sysobjects...

"run off of a local account, another says a locked down Windows account."

These are not conflicting recommendations. A windows account can be local or domain - I would choose...

Glad to hear it worked out for you.

They do tend to say read/write everything in response though, but it is a sea change...

Easy - don't tell the developer, tell his boss. Tell whoever in the business own the application. Tell anyone in the the business who might care.

Tell them the...

You can work around SQL 2000 security by granting a user membership of TargetServerRole, or in 2005 you can utilise the SQLAgentReaderRole.

For stored procedures you can use a GRANT statement...

Forget SQL for a minute and check the event logs on the server through compmgmt.msc - remember to use the IP address to connect.

If there's nothing there, check the services...

IP is not something that is SQLs responsibility, it's done by the OS so you can either monitor there, or check your firewall logs.

You _do_ have a firewall right?

Another thing...