Shulou(Shulou.com)05/31 Report--

This article mainly explains the "SQL Server database architecture and object-related knowledge", the content of the explanation is simple and clear, easy to learn and understand, the following please follow the editor's ideas slowly in depth, together to study and learn "SQL Server database architecture and object-related knowledge" bar!

1. Brief introduction of database architecture

Database architecture is a concept introduced since the SQL Server2005 version. The database schema exists independently of the data user who created it, and each object belongs to a database schema (objects include tables, views, stored procedures, functions, triggers, etc.)

2. Database, schema and database objects

The database schema is a non-repeating namespace independent of the database user, the user and the schema are independent of each other, and deleting the user will not delete the objects in the schema. Separating the database schema from the database user has the following advantages:

1. The operation of deleting database users is greatly simplified. Deleting a database user does not require renaming the objects contained in the user schema. So after you delete the user who created the objects contained in the schema, you do not need to modify and test applications that explicitly reference those objects.

2. Multiple users can share a default schema and then perform unified name resolution.

3. Shared objects can be stored in a schema created specifically for a specific application, not necessarily in the dbo schema, by sharing the default schema.

4. Permissions of objects can be managed with greater granularity.

If the database user has permission to create a schema, you can create and change the database schema in the database, that user is the owner of the schema, and can transfer ownership of the schema to other users, or grant other users access to the database schema, and only the owner of the schema can create objects in the schema.

Security is an important consideration in determining how to arrange objects in the architecture.

The schema acts as a namespace-- it is used as a prefix to the object name. For example, suppose you have a table named UserInfo in a database schema named System. The schema-qualified object name (also known as the "two-part object name") is System.UserInfo.

Description: the default schema of the database is dbo, and if you don't write the schema name, it defaults to dbo. Of course, if there are multiple database schemas in a database, it is recommended to use two-part object names. This can facilitate the readability of subsequent operation and maintenance and code.

Thank you for your reading, the above is the content of "SQL Server database architecture and object-related knowledge". After the study of this article, I believe you have a deeper understanding of what SQL Server database architecture and object-related knowledge has, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.