SQL Server and Table Ownership

Limited Support/End of Life Capabilities

If you need to request a hotfix or support for these features, please contact Alemba Support

When using ASM Core with SQL Server, it is recommend that ASM Core tables are created by a member of the sysadmin fixed server role . This ensures that ASM Core tables are owned by dbo.

Any member of the sysadmin fixed server role is mapped to a special account inside each database called dbo. Any object created by any member of the sysadmin fixed server role belongs to dbo automatically. Only objects created by members of the sysadmin fixed server role belong to dbo. The dbo cannot be deleted.

The reasons for having dbo as ASM Core table owner are:

• Any tables owned by dbo can fully support Integrated Security with Microsoft SQL Server 2008 R2, providing index-tuning wizards that offer considerable query performance benefits. However, only tables owned by dbo can take full advantage of the query-tuning wizard.

• Moving databases between servers is simpler since there is no dependency on entries in sysusers matching syslogins.

You can apply the ASM Core schema to a new ASM database or upgrade existing client databases through the Server Console.

The account used when creating a system in the Server Console must be a member of the system administrator’s role.

Once the Update script has been run to create the schema, this account can be replaced with a non-system admin account. Equally, integrated security could be used to access the database from ASM Core.

New ASM Core clients are able to create the complete ASM database, with all the tables owned by dbo as default.