You can use your stored defaults, the password is encrypted, and the file contains everything you need. This will all work well, if you can set up the access permissions properly. You can define and refine it in the SQL Compare GUI and be confident that if you save it to the correct shared file location, it can also be used by the automated process. The easiest of all these methods to use is the project file. With PowerShell, you can use SQL Compare with the switches as you would at the command prompt or batch file, use an existing project file, you can ‘splat’ them (pass parameters as hashtables, to the PowerShell cmdlets), or you can use an XML file.With the command line, you can use SQL Compare command line in the conventional way, or use an existing project file, or you can get it to take its commands, switches and options from an XML file.You are most likely to choose to use either the old-fashioned command line or PowerShell. You have several alternatives for scripting SQL Compare. Scripting schema comparisons and deployments There are ways of avoiding these minor tweaks easily, by using the SQL Compare command-line together with the GUI, so that they share and use project files to store configuration information. If you need to make a change, and you use the obvious approach of command line switches in your script, you face the task of rummaging about in a long script to change command line switches and lists of options. This is a noble aim, but a lot of the changes are forced on us, because of the many ways that you can configure a comparison and synchronization. Therefore, once they are working well, the instinct is to leave them well-alone. Without some forethought, and perhaps some cunning, these scripts can get quite complicated, and so take quite a bit of development work. When you have a process, such as a database deployment, that is well established using SQL Compare’s GUI, you will want to replace it with a script. If you are doing a daily build, then that requires a daily chore. This article proposes a way to avoid this using SQL Compare projects.ĭatabase development requires a great deal of work to keep all the required databases up to the current version. However, you continually need to delve into the script to tweak comparison settings or add a new command line switch. Your PowerShell script for automating database comparison and deployment is running smoothly, and your instinct is to ‘leave well alone’. 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.
0 kommentar(er)
