SQL Server mainly focus on the Database Architecture and design issues and many database level design changes can have a great impact on the performance, but unfortunately the user may be restricted from making schema is equal to level changes in some of the conditions. This includes the third party software, legacy internal software or even with the some of the internal software's. While the user is trying to make the necessary changes in schema level and the developer cannot perform with user jointly.One of the best database design actually perform to reduce many performance issues like proper normalization and foreign key usage. And these things even though the user may get some push back from the developers, quite often it provides better performance while performing the design issues in design phases in appropriate matching data types to help avoid implicit conversion issues and queries. And unexpected index scans that can make a queries takes much longer to execute and use a lot more resources. The physical database design is very important for performance and a huge majority of database out in the field can have only one data file with only one primary file group.
Architecture and Issues
Description
The Database Architecture and design issues contain the following procedures and methods such as:
Using default database properties
Poor database normalization
Lack of check constraints
Lack of foreign keys
Heap tables
Inappropriate data types
Wide data types
Poor query designs
Not using T-SQL stored procedures
Overuse of ORM query generators
ORM query considerations
Description
ORM query considerations contains the synonymous values and stages such as:
Contain stored procedures or parameterized queries
Writing complex select queries as stored procedures
Checking the parameter sizes
Optimize for ad hoc workloads
stored procedures or parameterized queries
This helps in minimizing the plan in cache bloat and stored procedures are easier to monitor.
Writing complex select queries as stored procedures
Here the ORM tools have more problems with the complex select queries.
Checking the parameter sizes
Here the ORM code is very common for all the ORM tools to size the parameter to the string size of the passes parameter.
Optimize for ad hoc workloads
Optimize for ad hoc workloads will helps in minimizing the plan cache bloat and is an instance level setting.
Summary
Key Points
Database and Design Issues - Describes the procedural aspects for SQL Server.
Architecture and issues - Contain the methods and procedures.
ORM query consideration - Describes the parameter size and optimize works loads.