- Paperback: 408 pages
- Publisher: Apress; 1st ed. edition (May 27, 2015)
- Language: English
- ISBN-10: 1430267739
- ISBN-13: 978-1430267737
- Product Dimensions: 7 x 0.9 x 10 inches
- Shipping Weight: 1.9 pounds (View shipping rates and policies)
- Average Customer Review: 6 customer reviews
- Amazon Best Sellers Rank: #2,594,423 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Healthy SQL: A Comprehensive Guide to Healthy SQL Server Performance 1st ed. Edition
Use the Amazon App to scan ISBNs and compare prices.
Customers who viewed this item also viewed
Customers who bought this item also bought
“The book’s intended audience includes both junior and seasoned SQL Server DBAs: they will appreciate it for the hands-on approach as well as for the valuable scripts and tools … they will easily incorporate in their toolboxes.” (Alberto Bolchini, Computing Reviews, computingreviews.com, May, 2016)
About the Author
Robert Pearl, president and founder of Pearl Knowledge Solutions, Inc., has been a Microsoft SQL Server MVP since 2009, having received his fifth MVP recognition award. He is a solutions-oriented senior DBA with 15+ years of experience, and is considered a subject-matter expert on SQL Server technology. He also coined the terms Healthy SQL™ and SQL Fitness™ to kick off the worldwide healthy SQL campaign to highlight the need for regular health checks to ensure that everyone’s SQL Server environment has achieved a healthy state. He is a SQL Community and SQL Saturday evangelist, promoter, and speaker, and maintains his regular blog called Pearl Knows at SQLServerCentral.com. Pearl was voted Top Blogger in the 2011 SQL Mag Community Choice Awards. He is also the creator/developer of the award-winning product SQL Centric―a web-based database monitoring and alert system for DBAs. Robert is a SQL Saturday organizer and co-chair of the successful New York Metro PASS SQL Saturdays.
Try the Kindle edition and experience these great reading features:
Showing 1-6 of 6 reviews
There was a problem filtering reviews right now. Please try again later.
To be clear, I am definitely not knocking the author's skills at SQL Server tuning, he absolutely knows his stuff. There are some solid gold nuggets scattered around through the book.
I have written a detailed chapter-by-chapter review of this book on www DOT i-programmer DOT info, the first and last parts of this review are given here. For my review of all chapters, search i-programmer DOT info for STIRK together with the book's title.
This book aims to ensure your SQL Server databases are healthy, how does it fare?
Robert Pearl sets out to provide you with the knowledge to ensure your SQL Server databases are healthy, this includes aspects of performance, maintenance, high availability and disaster recovery.
His book is targeted at database administrators and developers, additionally, system administrators might also find the content helpful.
Below is a chapter-by-chapter exploration of the topics covered.
Chapter 1 Introduction to Healthy SQL
The chapter opens with a look at the role of the DBA, being involved with backups and restores, creating database objects, and resolving performance problems. The importance of having a database that performs well, is auditable, and regularly maintained (i.e. is healthy), is discussed in terms of a SQL health check.
The chapter expands on the components of a SQL health check, including:
*Performance – primary reason for a SQL health check. Identify why queries are slow then improve them. Spot issues before they’re escalated. Proactive approach
*Security – the need to protect data
*Stability – apply service packs and relevant cumulative updates, in a timely manner
*Audits – prove the instance is healthy, at any time
*Backups – often first line of defence when have problems
*Business continuity – ensure systems can continue after a disaster
The chapter continues with a look at when to perform a heath check (now), highlighting the importance of creating a baseline – against which future changes can be compared. Helpful website links are provided (as they are throughout the book).
This chapter provides a helpful overview of what a SQL health check is, why it should be performed, some potential problems if it’s not performed, and some of the tools used. It also outlined what to expect from the rest of the book.
I found parts of the chapter chatty and informal (this occurs throughout the book), which may be suitable for some readers. The Surface Area Configuration tool is referenced as SAG, this should be SAC. There’s a nonsensical sentence that reads “I suggest that you the entire the book, at least once...” These problems should have been caught by the editors/reviewers.
The book aims to ensure your SQL Servers are healthy. It certainly covers many tools, techniques, and best practices. There are plenty of step-by-step walkthroughs, relevant code examples, helpful diagrams, and links to useful websites throughout the book. The book should take your level of understanding of SQL Server health, from 2 to 8.
Reading the initial chapters, I had expected the book to provide distinct separate checklists to enable me to check the health of my SQL Servers. I expected the checklist to tell me what data values where acceptable, and details of how to correct bad data values. However, this is not the case. In many ways, the book as a whole becomes the source of your checklists.
I found some of the initial chapters muddled - maybe because there is a lot to say on the subject, and the topics overlap and intertwine. Many tools are introduced and then discussed in more detail later, I would have preferred the tool usage to be centralised in one chapter, and earlier in the book. I found the book’s style too chatty and informal, but this might suit other readers.
A few areas contained obvious spelling mistakes e.g. statiscs, exeucet , “dot able scan”, “than0for”. Some of the links given between the chapters were incorrect. The query output is often difficult to read, owing to bad formatting. Sometimes, the language used was a bit lax (e.g. log shipping requires the full recovery model). All these faults should have been caught by the reviewers/editors.
If you want to ensure your SQL Servers are healthy, with respect to performance, security, stability, audits, and business continuity, I can recommend this wide-ranging book.
Robert has brought a lot of information together to help the DBA figure out what is needed to keep the databases running, how to measure that performance over time, and how to show the managers those measures and performance. It is well worth the read.