文件名称：Healthy SQL.pdf
文件大小：18.74MB
文件格式：PDF
更新时间：2023-02-27 11:57:59
sql server
Microsoft SQL Server has become an eminent relational database management system (RDBMS) in the marketplace. The SQL Server engine has come a long way from being just another RDBMS; it’s an end-toend business intelligence platform with built-in options for reporting; extract, transform, load (ETL); data mining; and high availability/disaster recovery (HA/DR). Its rich feature set provides a comprehensive solution for deploying, managing, monitoring, maintaining, auditing, reporting, and backing up and restoring databases; building data warehouses; and more! You will learn all about this as you journey through this book toward achieving healthy SQL. Whether it’s small, medium, or large enterprise infrastructures, it is common for organizations to have deployed multiple SQL Server instances in their environments, and as companies deploy various applications, many have had to deal with what’s known as SQL sprawl. This is the 1:1 ratio explosion of deploying every new application to its own SQL Server. The implementation of multiple SQL Server instances has made it difficult for database administrators to manage and maintain them. It is not uncommon to eventually embark on a SQL Server database consolidation project with the assistance of a qualified SQL Server database professional. Another common scenario is that third-party vendors will deploy their applications on back-end SQL Server instances and leave their clientele to their own devices. They will install SQL Server even though it’s doubtful that they know what the proper installation and configuration settings are. The goal of a vendor is to install and set up its application without regard for the ongoing health or performance of SQL Server. This is known as “Set it and forget it.” In a situation of “Set it and forget it,” as the application usage increases, as new records are continuously inserted, updated, and deleted, and as users place demand on the application, response times will eventually slow down, as will the overall performance of the SQL Server database back end. Indexes become fragmented, excessive page splitting occurs, and backups are not properly configured. All these issues that occur on the back-end SQL Server instance frustrate users, and organizations don’t usually have the database administrator (DBA) skill set in-house to fix these performance problems. Often the application vendor will not even have the right know-how or database expertise required to resolve these issues. In these situations, there are a myriad of questions that companies and database professionals need to ask themselves. For example, can SQL Server perform better? Can the application scale if it is necessary? Do we have a recent backup? Is there a disaster recovery plan? Can the database be restored?