Troubleshooting
Published 06 February 2013
This page provides information that may help you if you are having difficulties. You may also wish to refer to Understanding the results.
If you are asked to send Red Gate support a log file, see Logging and log files.
Common issues
- SQL Packager cannot connect to the SQL Server
- Missing tables in Packager Wizard
- Identity columns created or upgraded even though they are excluded
- Identical CLR data is flagged as different
- CLR data has not been upgraded
- SQL Packager sometimes creates DLL files with the executable
- Creating a database for an earlier version of SQL Server
- Rollback on script cancellation or failure
- Reseed applies "incorrect" identity values
- Primary keys, indexes, or unique constraints are not dropped
- Data has not been upgraded
- Package execution failing because the login already has an account under a different user name
- Package created from script always creates new database
- SQL Packager not keeping the READ_COMMITTED_SNAPSHOT SQL option ON
- Setting the database options for a New Database
Error messages
- "Value cannot be null" error creating data script
- Invalid SQL when synchronizing an index to a scripts folder when data compression is specified
- Insufficient disk space
- A duplicate object name has been found
- User already exists in database
- DEFAULT_SCHEMA clause cannot be used with a Windows group