That error may be due to that the database has been restored from a different server and there is a mismatch between dbo in the database and the database owner...

syslogins or sysusers? That is, server logins or database users?

As John says, you should be using sys.xxxxx_principals, but whether that is database_principals or server_principals depends on wherther you...

I can confirm what John says about the password. On SQL 2000, passwords were case-insensitive, if the server collation was case-insensitive. This was changed in SQL 2005.

If...

Yes, for views database chaining are the only option. However, if you want the interface of a view, you could use a multi-statement function and wrap a view around it.

The alternatives without moving data are:

1) EXECUTE AS + TRUSTWORTHY. OK, *if* ExternalGroupDb is owned by an SQL login that has no permissions granted, except one: AUTHENTICATE in the other...

I think I need to abstain from answering on what you should do. There is just too little I know about your situation.

I can add two tidbits though:

1) I would...

If you only want to drop the *login* which is on server level, there is no issue with the schema.

However, if you also want to drop the database *user*, then...

The policy for the password is taken from Windows. The common rule in Windows that there must be characters from three of the four groups uppercase, lowercase, digits and punctuation,...

I don't know exactly what you mean with "see", but you mean what you see when you expand nodes in SSMS, please attempt to run queries from a query window...

Enabling DB chaining for the two databases is probably the simple way out.

However, beware that if one user is db_owner in one database and plain user in the other, this...

Membership in sysadmin implies that all permissions checks are voided. So that DENY has absolutely no effect. At all.

Had you only granted them CONTROL SERVER, I believe that DENY would...

How is the symmetric key protected on the publisher? If you supplied a KEY_SOURCE on the publisher, I guess you need it at the subscriber too. If you encrypted the...

The issue with case-sensitivity and not being able to do range queries always applies if you encrypt data on cell level, no matter how you do it.

Smendle,

TLS is for securing the communication channel, so that no one can eavesdrop on the conversation with a network listener. But it does not encrypt any data in the...

The solution you have currently encrypts/decrypts server side - obviously. SQL Server functions do not run on the client.

If you want to encrypt client side and stay on SQL 2008...