tailieunhanh - SQL Server Tacklebox- P13

SQL Server Tacklebox- P13: This book, as with almost all books, started out as an idea. I wanted to accumulate together those scripts and tools that I have built over the years so that DBAs could sort through them and perhaps adapt them for their own circumstances. | 2 The SQL Server landscape document a SQL Server infrastructure using some T-SQL scripts a DBA Repository SSIS and SSRS. If you are interested in deploying this solution in your environment it is available to download from http RedGateBooks RodneyLandrum . It can easily be modified to suit your needs. With this repository or something similar in place you will have a means to easily get to know and monitor your SQL Server environment. Next it is time to consider the sort of tasks that this SQL Server environment needs to do and what others want it to do. A common request just when you ve got the environment nice and settled down is to move the data around a bit. The migratory data as it is often referred to at least by me is the subject of the next chapter. 60 Chapter 3 The migratory data When someone usually a developer or project manager enters my office and states We are going to need to move data from X to Y . there usually follows a short inquisition starting with the question Why Of course I can probably guess why as it is such a common request. As a data store grows it often becomes necessary to offload certain processes in order to maintain performance levels. Reporting is usually the first to go and this can involve simply creating a mirror image of the original source data on another server or migrating and transforming the data for a data warehouse. QA and Dev environments also need to be refreshed regularly sometimes daily. As a DBA I have to consider many factors before deciding how to allocate the resources required in building a data migration solution. As Einstein may have posited it is mostly a matter space and time or more correctly space time. The other less scientific variable is cost. Moving data is expensive. Each copy you need to make of a Terabyte 500-table production database is not only going to double the cost of storage space but also the time required for backup and restore or to push