It does precisely what its name suggests: it compares SQL databases. A database schema comparison tool like SQL Compare makes light work of the task. If you must sort all of this out manually, it’s a laborious, error-prone and time-consuming task. See Using Filters to Fine-tune Redgate Database Deployments When you need to exclude certain classes, or types, of database objects completely from any schema comparisons and deployments, sometimes there is an option that will do it, but it probably safest to set up filters to do this job.
Multiple select and editing with redgate sql toolbelt tips and tricks code#
With some of these features, it is by no means clear-cut that the code is suitable for a development version of a database. There are a host of features in SQL Server, and more are being introduced on every release. Conversely, when those classes of objects sneak into development systems, regardless, and then get changed and included into deployment script for production, it can cause all sorts of problems. For example, you’ll probably want to exclude synonyms, partition schemes and partition functions, and users to name just a few. If you’re generating a script to capture production changes into your source control system, or development database, then there will be parts of the metadata that are strictly outside the responsibility of the development and shouldn’t even be in source control you’ll need to exclude those objects from comparisons. Customizing schema comparisons and deployment scripts It also depends on whether you’re deploying changes from development to production systems, or vice versa.
But which database objects should be included in the schema comparison? Are all differences significant? Is it right, for example, to list or deploy differences in comments, indexes, or constraints? How do you deal with issues such as system-named constraints, or differences that arise because the collation setting isn’t the same in the databases being compared? How should you handle differences in encryption settings between two databases? When answering these questions, so much depends on the style, design, or type of database. You are examining schema differences between two copies of a SQL Server database. He is a regular contributor to Simple Talk and SQLServerCentral. Phil Factor (real name withheld to protect the guilty), aka Database Mole, has 30 years of experience with database-intensive applications.ĭespite having once been shouted at by a furious Bill Gates at an exhibition in the early 1980s, he has remained resolutely anonymous throughout his career.