Chris Auckland wrote:Thanks for your post.
I believe you have found the private release version now, so hopfully this should resolve your first issue. (Tools > Options > schema options > [uncheck] include dependencies)
When you try the patch version, can you see if using the updated SQL Comapre & SQL Data compare engines also resolves your script order issue?
With regards to the FullText catalogs, unfortunatly this is actually quite difficult to resolve.
Changes to the FULLTEXT Catalog or Indexes cannot be placed into a transaction and therefore have to be scripted somewhere outside of the transaction. If we put the full text stuff first and then there was a problem with the subsequent transaction, then the database would be left in an inconsistent state. We feel that it's better to create a script that fails and rollsback, rather then damages the database.
The usual workaround to this problem (with SQL Compare) is to compare the two data sources, synchronize the FULLTEXT Catalog first on it own, then refresh the comparison and synchronize the remaining database objects. With SQL Packager, you could use the same aproach, but save a sync script for each, then join them together and use the 'package script' feature of SQL Packager 6.
I hope this is helpful.
CodeDreamer68 wrote:First, using the wizard, when I uncheck boxes for objects in my database, the packager seems to completely ignore my un-selections and scripts them anyway. So that means I have to go through the script, that your software generates, line-by-line and remove all the objects that I didn't want scripted.
This means I can't build an executable installer package, because your software dosn't allow you to edit the script manually, prior to creating said executable package.
Explain to me why anyone would buy this POS?
Users browsing this forum: No registered users and 1 guest