Run these querie:

SELECT * FROM sys.database_permissions WHERE state_desc = 'DENY'

SELECT * FROM sys.server_permissions WHERE state_desc = 'DENY'

And then dig further from the appropriate DENY that you find.

The question is not very clear, but EXECUTE AS is a non-starter. Sign the procedure with a certificate and create a login from the certificate and grant that login the...

sys.database_permissions.

No, that's not the ticket. The certificate user is only there to tie the cert to the permissions. It has nothing to do with the application.

As I said, this error...

You can grant EXECUTE permissions on schema level:

GRANT EXECUTE ON SCHEMA::dbo TO someone

or on database level:

GRANT EXECUTE TO someone

It sounds as if you have an EXECUTE AS somewhere in your procedures or functions. When you impersonate a database user you are sandboxed into the current database. This is...

There are a couple of possibilities. The best is to sign the functions with a certificate which exists in both databases. In the other database, you create user from the...

I'm not sure that this is an SQL Server question, since your problem seems to be with running IIS. But if they are connecting to SQL Server through a web...

Books Online seems to be quite clear that DATABASE_OBJECT_CHANGE_GROUP applies to any databas, and there is a warning that this can result in large logs.

As for the question of model,...

russc-993845 (10/29/2014)

---

Whatever luck you want to call it, it has worked for me through at least 6 versions of SQL. Judging by the number of posts across the net from...

russc-993845 (10/29/2014)

---

I understand that the identity value is "meaningless", but in previous version of MSSQL it provided me with an accurate enough incremental number to allow for accurate auditing. In...

My first attempt would be

ALTER LOGIN guesser ENABLE

Then again, it may be the fact that the guy is login which prevents UNLOCK from working.

Server side trace with SP:StmtStarting and SQL:StmtStarting with the filter TextData like %xp_cmdshell% seems like the only alternative. Ot the corresponding X-event session on SQL 2012 or later.

If you look up the documentation for sys.database_principals and similar catalog view, you will find that the type for name is sysname, that is nvarchar(128). This is also the return...

The attacks are coming on the port on which SQL Server is listening on. Which you can see in SQL Server Configuration Manager and also in the beginning of the...