For that reason, having accurate and up-to-date statistics is crucial.
In such cases, the DBA should apply one or more of the obfuscation techniques described in this article, extracted from John Magnabosco's excellent new book, Protecting SQL Server Data. On this holiday, the young and young at heart apply make-up, masks, costumes and outfits and wander the streets in search of sweet treats from their neighbors.The restore The first step in the process is to restore the database.We talked about restoring databases in a previous tip and the different commands that are used to restore databases.Typically, both should be left enabled for databases.Statistics are automatically updated when certain thresholds within SQL Server are met, i.e., the number of rows in the table increases or decreases by 10% of the number of rows the statistic was based on.on SQL Server 2005, we do a weekly full backup with nightly incremental backups. There is another method, but a little more complex.I want to know if it is possible to restore a single table from a backup, either to the source database or a different one. If your single table is getting very large, copy it onto a filegroup.Restoring the database is the easy part, but then you may be left with mismatched logins and database users.In this tip we will look at some of steps to go through when restoring a database from a different server.The views provide basic metadata about most of the entities in each database.The far-more-expansive Catalog views offer just about every piece of metadata that SQL Server currently exposes to the user.We will take a look at a couple of the commands that can be used to look at the contents of the backup files as well as the commands to perform the restore.Restores can be accomplished by either using T-SQL commands or using Enterprise Manager.We will take a look at how the restore can be accomplished using T-SQL.