AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Adventureworks database diagram 20163/11/2024 ![]() Objects are in the schema under the developer’s name, e.g.: “Andreas.Shoppingcart”.All developers put all objects into the dbo-schema.Up to SQL Server 2000, users and schemas were independent of each other, and there were only 2 options: ![]() Particularly as the concept of the Schema-User separation was a relatively new thing back then. This database is generally supposed to demonstrate the new features of the SQL Server Versions since 2005, but the concepts are not always being developed according to best practices. Because, to relieve all autodidacts, ironically, the well-known “AdventureWorks” database is anything but exemplary when it comes to schema-design. With this – admittedly long due – blog post I hope to provide a good reference. I admit that the amount of information on this topic is not as extensive as on the regulars “Indexing” and “Performance.” Hardening Security is an effort perceived as rather annoying, and developers are rarely trained in such areas in order to make the important decisions right at the design stage. Unfortunately, however, I still see databases every week which only seem to know the “dbo” schema. In the same way that a developer/architect has to deal with business processes for the ER-diagram and later tabular design, one has to deal with database access processes for the schema design. As a matter of fact, it is not really that difficult. Since the release of SQL Server 2005, in fact more than 10 years ago, it is of particular importance to me to train users in correctly using schemas. Here, schema does not mean the database schema with its tabular design but rather the “database object schemas,” also described as Namespace. This article picks up a topic I have been teaching time and again in seminars, at conferences and in forums for many years: Schema-Design.
0 Comments
Read More
Leave a Reply. |