|
|
|
|
|
Schema Manager 1.0 1 2 3 4 5 6 7 With the captures, you can restore an earlier version of the schema if needed. You can roll back an entire schema or a specific object. In addition to being able to revert to an earlier version, you can also compare the archive to another archive or live database, migrate the schema to a live server, extract all or specific objects to a script file, and generate a navigable HTML report of all of specific objects.
A comparison is probably the most frequent operation that you will perform. A compare can be done between an archive or a live data source. The comparison can also take place with one or more targets. The wizard that guides you through this process is very similar to the one for a capture job. You can specify that you want graphical or file output. Graphical output is on demand. File output can be scheduled. It struck me as curious that they would force a decision here. I should be able to specify whether I wanted a file based or graphical output when I execute the job. If I schedule it, I obviously want file output. If I have a need to run the same compare interactively and get a graphical output while also scheduling one, I need to create a copy of the job. When the job runs graphically, you will something similar to the figure below. This demonstrates the failure in distinguishing between user and system objects that I mentioned above.
|
All content on this site, except where noted, represents an original work of Michael R. Hotek and is protected by applicable copyright laws. The SQL Server FAQ is the sole work of Neil Pike. No page, portion of a page, or download may be used for commercial purposes in whole or in part without the express, written permission of the applicable author.
