Viewing 15 posts - 196 through 210 (of 6,105 total)
Tara-1044200 (5/24/2011)
May 24, 2011 at 10:44 am
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...
May 24, 2011 at 10:02 am
mlundblad (5/24/2011)
May 24, 2011 at 10:00 am
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...
May 24, 2011 at 9:41 am
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...
May 24, 2011 at 5:27 am
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:
May 23, 2011 at 9:23 pm
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...
May 23, 2011 at 9:19 pm
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...
May 23, 2011 at 9:15 pm
When you see the audit failures in the SQL Server log, what do you see in the OS' security event log? Same thing?
May 23, 2011 at 9:12 pm
Simple answer: ownership chaining. 🙂
May 20, 2011 at 10:52 am
So those accounts have the correct permissions and you still get the error?
May 20, 2011 at 8:59 am
barry reilly (5/20/2011)
I also see the BAckupDiskFile: CreateMedia for the x:\symantec\data\BEDB.bak' failed to create. OS Err 5 ( access denied),
Ensure the SQL Server service account has permissions on x:\symantec\data because...
May 20, 2011 at 8:29 am
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...
May 19, 2011 at 9:23 am
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...
May 18, 2011 at 7:39 am
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...
May 18, 2011 at 7:34 am
Viewing 15 posts - 196 through 210 (of 6,105 total)