|
|
|
|
|
Schema Manager 1.0 1 2 3 4 5 6 7 Selecting Capture will take you to a 5 step wizard that defines the scope of what is captured. You first select a server and specify login parameters. The next part allows you to specify a single database or the entire server. From there you can specify if you only want database objects and which types or if you want to grab server level items such as configuration settings and logins. After you give the capture job a name and save it, you will see the figure below that allows you to immediately execute the job or optionally schedule it.
When you execute the job, you will see a figure similar to the one below showing the progress of the job.
When the job completes, you will see a screen similar to the one below. Here I have run multiple capture operations against more than one data source. You can see the versions clearly tracked by data source. There are a few bugs in the capture process. One of the databases that I captured was published with merge replication. Even though the capture is supposed to ignore system objects, it captured all of the system objects from the merge replication. It also can not distinguish the information schema views and other system views such as sysalternates from user objects. Both of these are known bugs that exist across DBArtisan, RapidSQL, and Schema Manager that will be fixed in the next release.
|
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.
