SQL Packager - 6.4
Working with projects - SQL Packager
Whenever you create a database package, you set up a project. A project contains:
- the information required to connect to the database you want to package
- information about which objects and data you want to include in the package
- the package details such as name, location, type, and compression
- optional deployment notes
- optional details about the database that will be created, such as the default name and size
You can create a new project each time you create a package. Alternatively, if you will be using the same settings repeatedly, you can save the current project to a file. You can then open it at a later date to make it the current project. You can also edit the current project if required.
You are recommended to run the project using the default packaging options and review the results before you change any options. If you want to change your packaging options before you run the next project, if necessary click Cancel on the Packager Wizard, and set the options before you proceed.
Note that packaging options are not saved as part of the project.
Creating a new project
To create a new project:
- If the Packager Wizard is not already displayed, click
New Project. The Packager Wizard opens.If you have unsaved changes in the current project, you are prompted to save it.
- In the Packager Wizard, choose a project type.
- If you are not packaging an existing SQL script, specify the package contents.
- Review any generated SQL scripts for the object and data creation.
- Create an .EXE (.NET executable) or a C# project.
SQL Packager packages the database. Alternatively, you can launch the package creation script in your default SQL editor, or save the script.
You can then save the project if required.
Saving the current project
When you have packaged a database, you can save a new project so that you can re-use the settings at a later date, or you can save an existing project to a new name. Projects are saved with the extension .sqlpkg
- On the File menu, click Save Project As.
A standard Windows® Save As dialog box is displayed.
If you have edited the current project, an asterisk (*) is shown in the title bar; to save the edited project to the same name:
- On the File menu, click Save Project; alternatively, click

Editing the current project
You can edit the current project and package the database again.
- Click
Edit Project. - In the Packager Wizard, change the package specification as required.
- Review the generated SQL scripts for the object and data creation.
- Generate an .EXE or a C# project.
SQL Packager packages the database. An asterisk (*) is displayed in the title bar to indicate that the project has been edited.
Opening an existing project
- If the Packager Wizard is displayed, click Cancel to close it.
- Click
Open Project.If you have unsaved changes in the current project, you are prompted to save it.
- In the Open dialog box, choose the project and click Open.
The Packager Wizard is displayed with the project's settings.
To open a recently-used project, on the File menu, click the name of the project.
See also |
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