Create Your Own Advance Sql Server

I’ve been writing and presenting about query tuning and optimization for years. I even wrote a book on the
topic called SQL Server 2014 Query Tuning and Optimization. Query tuning and optimization is extremely
important to improve the performance of your databases and applications.
Equally important is having a well-designed and configured system in the first place. SQL Server default
configuration can work fine for some applications, but mission critical and high-performance applications
demand a thoughtful design and configuration. Well-written and tuned queries will not shine if a system
is not properly configured. For example, queries will not use processor resources in an optimal way if
a maximum degree of parallelism setting is not configured correctly. Database performance will suffer
if a database is using the default file auto-growth settings or if the storage is not properly configured. A
misconfigured tempdb may show contention on many busy systems. Even the query optimizer will struggle
with a bad database design or badly written queries. These are just some common configuration problems
out there in real production systems.
In addition, even when a well-designed application goes to production, performance tuning does not
end there. Monitoring and troubleshooting are an extremely important part of an application and database
life cycle since performance problems eventually will arise. Workloads may change, hopefully for the
better (for example, an application having to deal with an unexpected increase on business transactions).
Sometimes those changes will require a redesign, changes, and perhaps new configurations.
So this is, in fact, an iterative process, consisting of design and configuration, followed by
implementation, monitoring, and troubleshooting, which again may lead to new designs or configurations,
monitoring, and so on. In addition, collecting performance data, creating a baseline, and performing trend
analysis is an important part of a production implementation, not only to troubleshoot problems but also
to anticipate issues or understand future growth and additional requirements. It is essential to estimate
and trend those changes proactively instead of waking up to a system suddenly having trouble in handling
changing workloads or, even worse, to face a downtime that could have been avoided. There are several tools
to help with this, and the great news is that SQL Server 2016 offers a very promising one called the Query
Store.
I spent a good part of my daily job working on all these items so I decided to write a book about them.
I wanted to cover everything you need to know about performance in SQL Server that does not require you
to know about query tuning, work with execution plans, or “fight” the query optimizer. There are so many
areas to cover and more are being added as new features and technologies appear on SQL Server such as In-
Memory OLTP, columnstore indexes, and the aforementioned Query Store.
This book covers all currently supported versions of SQL Server with a major focus on SQL Server
2016. Although this is a performance book from the practical point of view, SQL Server internals are very
important too. The best way to troubleshoot something is to know how it works and why things happen.
Consequently, I focus on internals when required.
Finally, this book complements my query tuning and optimization book. If you are a database
developer or a SQL Server professional who cares about query performance, you could benefit from both
books. If you are a database administrator, a database architect, or even a system administrator, and you
want to improve the performance of your system without query tuning, you can read only this book.