Tara-1044200 (5/24/2011)

---

I created logon trigger but it not allowing the user to logon which i dont want,I want to allow them to logon and may be email me who logged...

Since they are connecting as a SQL Server login, you can't get any information about the Windows user because it's not passed unless the application does in some way. The...

mlundblad (5/24/2011)

---

It looks like the SysAdmin role allows the login to "impersonate" DBO for all databases. I noticed that when I run username() function for a login with the...

No. Logon is a server-level event, which is why the trigger is only at the server level. What are you trying to do? A DDL trigger at the database level...

Yes. But in actuality, you don't have to. However, if you want to remove it, bring up MMC, add the Certificates Snap-In and choose Service Account. If you administrator rights...

Here's what you must do to install the certificate in order to encrypt connections. It must be done for the computer account, not the SQL Server service account. Here's how:

How...

You will likely have to grant the user VIEW SERVER STATE permissions. If you don't want to do that, you'll have to craft their queries into stored procedures and then...

You don't want to do this at the database level. It's actually going to be an operating system configuraiton. Basically, you're going to need to install a server certificate that...

When you see the audit failures in the SQL Server log, what do you see in the OS' security event log? Same thing?

Simple answer: ownership chaining. 🙂

So those accounts have the correct permissions and you still get the error?

Ensure the SQL Server service account has permissions on x:\symantec\data because...

No, those are normal. If you do the same thing against a development SQL Server and login using SSMS, you'll see the same thing. Any other errors being reported? You're...

Third party backup products do require sysadmin membership. You might want to open up profiler, set it up to pickup failed logins, exceptions and user error messages and then run...

Add an EXECUTE AS clause to the stored procedure (SQL Server 2005 and up) as part of the CREATE PROCEDURE statement. You probably want to execute as the owner.

The...