SQL Packager - 6.4
Running the package - SQL Packager
Choosing a project type > Specifying contents > Previewing scripts > Specifying a package type > Running
When SQL Packager has generated the package, you can run it using a graphical user interface or from the command line.
Note that the graphical user interface may differ from the interface described in this topic if it has been customized.
Using the graphical user interface to create a database
To create a new database:
- Display the Run Package dialog box:
- for an .EXE package, run the executable in the usual way
For example, double-click the .exe file in Microsoft® Windows® Explorer.
- for a C# project, open the project in Visual Studio®, press F5 to run it, or on the Debug menu, click Start
Alternatively, compile the project and run the executable in the usual way.
The Run Package dialog box is displayed.
- for an .EXE package, run the executable in the usual way
- To view any notes that were added to the package when it was generated, or to see a summary of the SQL scripts and any warnings, click More Info.
The More Information dialog box is displayed with the information. Click OK to close it.
- In the Server box, type or select the name of the SQL Server on which you want to create the database.
If you experience problems selecting a SQL Server that is not running on the LAN, for example if you are accessing the SQL Server via an internet connection, you may need to create an alias to the SQL Server using TCP/IP (refer to your SQL Server documentation for details). You can then type the alias name in the Server box to connect to the remote SQL Server.
- Select the authentication method, and for SQL Server authentication enter the User name and Password.
- Do one of the following:
- To create a new database, click Make a database (the default) and type a name for the database in the Database box.
If you want to change the default database properties, click Advanced and enter the details as required. For more information about database properties, see Entering extra package information. Note that if you want your database to use filegroups or full-text processing you should create the database manually, and use the Upgrade an existing database option.
- To populate an empty database that you have already created, click Upgrade an existing database and in the Database box, type or select the name of the database.
- Click Run.
A message dialog box is displayed for you to confirm that you want to continue. A second message dialog box confirms that the package has run successfully.
Using the graphical user interface to upgrade a database
To upgrade an existing database:
- Display the Run Package dialog box:
- for an .EXE package, run the executable in the usual way
For example, double-click the .exe file in Windows Explorer.
- for a C# project, open the project in Visual Studio .NET, press F5 to run it, or on the Debug menu, click Start
Alternatively, compile the project and run the executable in the usual way.
The Run Package dialog box is displayed.
- for an .EXE package, run the executable in the usual way
- To view any notes that were added to the package when it was generated, or to see a summary of the SQL scripts and any warnings, click More Info.
The More Information dialog box is displayed with the information. Click OK to close it.
- In the Server box, type or select the name of the SQL Server for the database you are upgrading.
If you experience problems selecting a SQL Server that is not running on the LAN, for example if you are accessing the SQL Server via an internet connection, you may need to create an alias to the SQL Server using TCP/IP (refer to your SQL Server documentation for details). You can then type the alias name in the Server box to connect to the remote SQL Server.
- Select the authentication method, and for SQL Server authentication enter the User name and Password.
- In the Database box, type or select the name of the database that you want to upgrade.
- Click Run.
A message dialog box is displayed for you to confirm that you want to continue. A second message dialog box confirms that the package has run successfully.
Using the command line
When you run the package from the command line, the following options are available:
For example, to create a database called MyDatabase on SQL Server MyServer using SQL Server authentication, navigate to the folder that contains the package, and at the command prompt, type:
MyPackage.exe /server:MyServer /database:MyDatabase
/username:MyUserName /password:MyPassword
SQL Packager sets two return codes that you can use in batch files or scripts to determine whether the package ran successfully:
- 0 is returned if the package ran successfully
- -1 is returned if an error occurred
If you have specified /quiet to run without the graphical user interface, the return code is stored in the ERRORLEVEL environment variable, and the error message is written to the console.
See also |
Was this article helpful?
Using SQL PackagerSQL 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
