I gave it a try on SQL Server 2008 (10.0.2531.0) and I can confirm the resource database can be moved.

1. Stop SQL

2. Move mssqlsystemresource.mdf and mssqlsystemresource.ldf to C:3. From the...

One thing I noticed when changing a schema owner was that a database login that had permissions on the schema lost their permissions.

Not sure if you see the same thing....

It appears that you can only grant this Permission to a Login or a Server role.

If you want to use a role, you cannot create new Server roles so you...

There does not appear to be a GUI option in SSMS see all objects which belong to a schema.

As a work around, possibly you could use a query as below...

I suspect the answer is in 'http://msdn.microsoft.com/en-us/library/ms191291(v=SQL.100).aspx' with the key extract:

'Because the SQL Server security model is hierarchical, CONTROL at a particular scope implicitly includes CONTROL on all the securables...

This is strange as a clustered index can only have a max length of 900 bytes as in the message.

You can get higher than this with non-clustered indexes when using...

I would suggest adding Severity 14 alerts to detect login issues if you have set ‘Failed Logins’ auditing at the SQL instance level.

Below shows the Severity 14 login failure alerts...

As a sanity check, ensure that the 'Default schema' in the database for your login does not say dbo, but rather the new table owner you set. The only reason...

This link should help.

http://msdn.microsoft.com/en-us/library/ms152501(v=SQL.100).aspx

You could also try looking in the SQL default trace files e.g. below would extract the data from the trace file log_25.trc into a table called trace_log_25 in an existing...

The physical_device_name ‘{C1FE7C8B-A202-4A79-B6C6-2EEF42B6D97A}’ indicates possibly a tape agent?

It is possible to change back to SQL Authentication by updating the relevant registry key and therefore letting you use the sa login. This link gives the registry key details...

If you are still receiving the same error message then that would imply that you are still running in fibre mode. I would suggest check the run value of lightweight...