No, it is not an SQL Server permission per se. The error comes from LoginUserW which is a Win32 routine. So fiddling with groups etc in SQL Server is not...

NET HELPMSG 1385 says:

Logon failure: the user has not been granted the requested logon type at this computer.

But if this was a permission issue on the NAS, I would not...

Not sure why you are digging in the past. Better to get things working again.

But if you want to look, the primary places to for differences would be sys.database_permissions and...

TDE can be applied to an existing database. Beware that it does not apply to FILESTREAM data.

I agree with everything that Elliot said and not the least: be careful with...

A title from Joe Jackson's excellent album "Body and Soul" comes to mind: You can't get what you want, before you know what you want.

None of the encryption solutions in...

You can add EXECUTE AS '<somelogin>' to the trigger and this login has been granted access to the table. Or been granted VIEW SERVER STATE. You need to use original_login()...

It is unclear what you did, but you can grant permissions on schema level. For instance:

GRANT SELECT ON SCHEMA::DataArchive TO someuser

Say that you at some point run

CREATE LOGIN Hilary WITH PASSWORD = 'sdefhsdhhh'

And then you go on and grant permissions to this new employee. However, when this person turns...

SELECT u.name

FROM sys.database_principals u

JOIN sys.database_role_members rm ON u.principal_id = rm.member_principal_id

JOIN sys.database_principals r ON r.principal_id = rm.role_principal_id

WHERE r.name = 'yourrole'

ORDER BY u.name

Far from a complete solution for your case, but at least a starting point. Look at this blog post from Sebastian Meine:

http://sqlity.net/en/2584/script-database-permissions/%5B/url%5D

Since I am not versed in Active Directory, maybe I should not answer, but my gut feeling is no. The login has to be validated by other domain, and if...

Or course they do. principal_id in sys.database_principals is always 1 for dbo, and 0x01 is also the SID for sa in sys.server_principals. That is, you are mixing apples and oranges....

This can happen when you restore a database from one server on another. sys.databases says one thing about who is the owner, but sys.database_principals in the database has a different...

Lynn Pettis (6/17/2015)

---

IIRC, starting with SQL Server 2014 you can actually create custom roles that allow sys admins to do their work but not see the data. I haven't...

You encrypt the data client-side, and the users owns the encryption key out of reach for sysadmin. Values that needs to be keys, you hash.

As for auditing, there is SQL...