Packages and compresses schema and contents of SQL Server databases
Moderators: JonathanWatts, Chris Auckland, David Atkinson, david connell, Anu Deshpande, Michelle Taylor, james.billings, Marianne
We are using SQL Packager 5 to include some lookup data for our application. The app relies on some ID fields (identity fields) being present in the database and matching specific records, therefore the order in which the data is put in is important.
We had problems running the exe generated by SQL Packager on some systems where it complained about a mismatch between the collations, so we selected the Ignore Collations option. This made the exe work, however it no longer inserts the data in the same order source database tables (i.e the IDs to not match)
How can we get around this problem.
Shire Systems LTD
- Posts: 9
- Joined: Mon Jun 04, 2007 10:36 am
SQL Packager upgrade packages are static -- producing a data update between two databases will result in identity values that exactly match the ones in the source database. So if you run the resulting upgrade against a third database, you will get the source database's hard-coded IDs instead of the third database's automatically generated IDs. This is the same whether you're using Packager v5 or v6.
The only way I know of to produce a "dynamic" data upgrade would be using the SQL Comparison SDK
to compare your destination database to a backup file of your source database. SQL Packager doesn't (yet) have this functionality.
- Posts: 6670
- Joined: Mon Aug 23, 2004 10:48 am
Return to SQL Packager 6
Who is online
Users browsing this forum: No registered users and 0 guests