Options
Determining the number of objects being migrated
kfilipowsky
Posts: 14
If I intend to migrate 1 database object, but the API includes a dependent object(because it changed), is it a reliable to use something like work.messages.count>1 to determine that additional objects are being included?
I really just need to be sure if additional (dependent) objects are being included in the SQL creation process when I intended to only migrate 1. Those additional objects will have to flow through our CMS approval process is why I'm asking. I'm working in a Federally Regulated Environment.
I really just need to be sure if additional (dependent) objects are being included in the SQL creation process when I intended to only migrate 1. Those additional objects will have to flow through our CMS approval process is why I'm asking. I'm working in a Federally Regulated Environment.
Comments
I definitely wouldn't use the message count. There are plenty of reasons for displaying warnings before synchronization.
I can't find an interface in the SQLCompare.Engine that shows dependencies on an object, so I'd assume that whatever does this in SQL Compare is for 'internal use only'.
If you're migrating relatively few objects, what I would suggest is keep the list of objects that you want to migrate in an ArrayList or a Hashatble, then when you compare databases, loop through the differences and report on objects that appear in the differences collection, but not in your own list. These must be dependencies of the objects that you have chosen to migrate.
What I'm thinking of doing is marking all Differences as False after the comparrasion. Then selecting only the single intended object for migration. When I create the Work Object, I've "Observed" it generates the Batch(s) for the intended object and all the dependents. I haven't been able to make sense out of the Batche objects yet but It sure "Looks" like work.messages.count would work
If you have any other suggestions, I'd appreciate it.
Thanks in advance