For more info, see Complete the Wizard.How does it work? A. On this page, you review the choices that you made in the wizard, and then you start the operation. What's next?Īfter you specify additional options for saving the package, the next page is Complete the Wizard.
To learn how to customize the saved package, see Integration Services (SSIS) Packages. You have to add the package to an Integration Services project before you can open and run it. If you saved the package in the file system, see Run Integration Services (SSIS) Packages to run the package in the development environment. Then, in SQL Server Management Studio, in Object Explorer, navigate to Stored Packages | MSDB, right-click on the package, and select Run Package. If you saved the package in SQL Server in the msdb database, connect to the Integration Services service. To run a package from the command line or from a batch file, see dtexec Utility. To run a package by using a utility program with a friendly user interface, see Execute Package Utility (DtExecUI) UI Reference. To learn how to run the saved package again later, see one the following topics. On the current page, you provide a name for the package and more info about where to save it.
To take another look at the Save and Run Package page, see Save and Run Package. You also pick security settings for the saved package. On the previous page, Save and Execute Package, you pick whether to save the package in SQL Server or as a file. The Save SSIS Package page is one of two pages on which you pick options for saving the SSIS package. About the two pages of options for saving the package Optionally, browse to select the path for the destination file in the Save Package dialog box. Remember where you save the package file. Also, the wizard may try to save the package to a location where you don't have permission to save a file, and raise an error. If you only enter the filename without a path, you don't know where the wizard saves the package.
The following screen shot shows the Save SSIS Package page of the wizard if you selected the SQL Server option on the Save and Run Package page.īe sure to specify a destination folder, either by entering it or by browsing. Screen shot - Save the package in SQL Server If you want to save the package to a different destination, go back to the Save and Run Package page. The destination ( SQL Server or File system) that you previously specified for the package. As a best practice, describe the purpose of the package, to make packages self-documenting and easier to maintain. Provide a name and description for the package The rest of the page has a variable number of options which depend on the package destination that you chose. The following screen shot shows the first part of the Save SSIS Package page of the wizard. The wizard creates an SSIS package in memory as you move through the pages of the wizard and specify options. What's a package? The Wizard uses SQL Server Integration Services (SSIS) to copy data. The options that you see on the Save SSIS Package page depend on the choice that you made previously on the Save and Run Package page to save the package to SQL Server or to the file system. On this page, you specify additional options for saving the package created by the wizard.
If you specified on the Save and Run Package page that you want to save your settings as a SQL Server Integration Services (SSIS) package, the SQL Server Import and Export Wizard shows Save SSIS Package. Applies to: SQL Server (all supported versions) SSIS Integration Runtime in Azure Data Factory