SQL Packager
Latest version: 6.4
Knowledge Base
Creating a database for an earlier version of SQL Server
Category: How do I?
Date: 05 Jun 2009
Product: SQL Packager
SQL Packager creates databases in a way that is compatible with the database being packaged. For example, if the database resides on the SQL 2000 platform, the database scripts will be created in the SQL 2000 syntax. If Packager is configured to create an "upgrade" package, then it can change the T-SQL syntax so that it conforms to the target server platform.
To create a database package using the SQL syntax different from the version of the source database, it is necessary to have an installation of the version of SQL Server that you would like to deploy to.
On the desired SQL Server, create a new database and leave it empty.
Launch SQL Packager and choose your source database on the left-hand side. Choose the option to create an "upgrade to an existing database" and specify the empty database that you had just created on the right.
SQL Packager will produce a script to create all objects in dependency order, and use syntax that is compatible with the target server platform. Where possible, new features such as CLR assemblies are filtered out because they are incompatible with SQL Server 2000. Sometimes this is not possible, for instance if a stored procedure relies on a CLR function. Since the function cannot be created, the stored procedure cannot be successfully scripted. Analyzing your databases for these conditions first is recommended.
Document ID: KB200709000150 Keywords: SQL,Packager,2000,2005,downgrade
Was this article helpful?
SQL Packager
- Logging and log files
- Package executable cannot load zlib1.dll
- Creating executables that use the .NET 2.0 runtime (version 5)
- Creating a database for an earlier version of SQL Server
- SQL comparison and synchronization automation capabilities
- Reseed applying "incorrect" identity values
- "Value cannot be null" error creating data script
- DEFAULT_SCHEMA clause cannot be used with a Windows group
- Package created from script always creates database
- SQL Packager not keeping the READ_COMMITTED_SNAPSHOT SQL option ON
- Setting the Database Options for a New Database
- Package execution failing because the login already has an account under a different user name
- Invalid SQL when synchronizing an index to a scripts folder when data compression is specified
- Logging and log files
all SQL products
- Compatibility of Red Gate tools in 64-bit environments
- Application has encountered an error and needs to close
- Error message after installing SQL Toolbelt - The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found.
- Changing the temporary directory used by the installer
- Toolbelt Installer "hanging" while "scanning volumes"
- Login failing with "trusted SQL Server connection" error when using RunAs
all products
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
SQL Packager
- Activating your products
- Activating your products
- Getting help offline
- SQL Packager release notes - version 6.xx
all SQL products
all products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs

Using SQL Packager