Database Tutorials MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux 
When a database owner changes his password, you may receive errors as follows. Therefore, it would make more sense to set the owner of the databases as the sa user.
SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. The logon attempt failed [CLIENT: ]
You can set the owner of a database to sa using the following script.
1 2 3 | Use MyDatabase GO EXEC sp_changedbowner 'sa' |
You can do this with the script above, but Microsoft has announced that sp_changedbowner can be removed in the future. Instead, it recommends using the following script.
Change the owner of the database:
1 | ALTER AUTHORIZATION ON DATABASE::MyDatabase TO sa; |
You can do more than just change a database owner with ALTER AUTHORIZATION. You can change the owner of each entity that has an owner.
Change the owner of the schema named test to DBO:
1 | ALTER AUTHORIZATION ON SCHEMA::test TO dbo |
