Try here:

SQL Server Version Database (SQLSecurity.com)

On those rows where the nt_username and loginame are both populated, are they the same?

C2 auditing is a comprehensive server-side trace. It's going to record all activity. Meaning if someone execute a command to change the owner of an object, execute sp_addrolemember, etc., you're...

Check the application event log on the server. There is probably an error event indicating why the reporting services web application wasn't available.

Yes, DDL triggers are the way to go here. Make sure you understand XQuery to understand the output.

*shameless self promotion alert*

I recently contributed on a SQL Server 2005 security book...

Database users are stored within the database itself. So when you move the database, you'll have the user. To transfer logins in SQL Server 2005, see the following KB article:

How...

Mayank Khatri (10/4/2007)

---

To Audit, you can use Sql servers C2 audit feature that will logon all failed and successful logins. To take this into affect you have to restart the...

If the SQL Server connection string says to use Windows authentication (Integrated Authentication), but the workstations aren't in a trusted domain and there is a guest login enabled on your...

Sorry, "modifying role" isn't clear. An event fires for ALTER ROLE. However, using sp_addrolemember to add a user account to a role may not fire an event.

I'm not sure an event fires for modifying role. So you may not be able to do so. Are they granting other users the ability to do more than SELECT?...

How is the connection to SQL Server defined? Is it defined via an ODBC data source? Is it a connection string hardcoded in the application or via the registry? If...

You can install the SQL Server client tools (from the SQL Server CD), but anything capable of making an ODBC or OLEDB connection (including Microsoft Access) will do. How do...

You'll want to set up server side tracing. You can script an appropriate trace using Profiler and then apply it to the server. You'll have to review these traces in...

SQL Server Configuration Manager

Protocols for

Named Pipes should show as Enabled/Disabled

Then those two are using SQL Server logins to connect. The others must be using Windows logins. If there is an ODBC connection, you may check its configuration.