There is a major face-lift with monochrome look. At the time of writing (a few minutes of exploring SSDT Visual Studio 2012), everything works the same for Option A. (Read Microsoft announcement on SQL Server Data Tools – Business Intelligence for Visual Studio 2012). Update – 6 March 2013: Both options work for Visual Studio 2012 too. Would it work for SSDT Visual Studio 2012? Special thanks to Josh Fennessy ( b | t), for providing Option B. Note: If the server is in Production, you could ask your DBA to export the. Please note that in this example, I have 4 connection manager files and 9 dtsx files.Ħ.
#CREATE SSIS PACKAGE IN VISUAL STUDIO 2012 ZIP FILE#
Browse the zip file and you should be able to see the. Navigate to the folder where the file has been saved and rename the file extension to. Choose the destination folder on “Save As” to save the. Right click on the, then choose Export….ģ. > Integration Services Catalogs > SSISDB > Projects > as shown on the picture below.Ģ. Navigate to the SSIS project on SSMS i.e. All the components in the Project, such as Project Variables and Project Connection Managers are kept in tact.ġ. This option is one of the safest / simplistic ways of getting SSIS project from the server. In my example here, I have 4 connection manager files and 9 dtsx files. Once the project is created, you can browse to the package(s) that you wish to inspect. Then provide the details of the project on the server that you wish to import.Ħ. On the Select Source dialog, choose Integration Services Catalog. Click Next on the Integration Services Import Project Wizard windowĤ. Then click OK to proceed to the next step.ģ. Choose Integration Service Import Project Wizard option, enter the Name, Location and Solution Name accordingly. In the New Project dialog box of SSDT, browse to Installed Templates > Business Intelligence > Integration Services on the left navigation pane.Ģ. Exporting the project into ispac file via SQL Server Management Studio (SSMS).Ĭaveat: Both these options require access to the project on the server.ġ. Creating a new project in SQL Server Data Tools (SSDT) and import the project from existing catalog.ī. Back to the issue at hand, if you want to get a copy of what is in the production, in summary, there are two “easy” ways of doing so.Ī. SQL Server 2012 Integration Services now is now making use of Project Deployment Model. Unfortunately at the moment there is no way of just quickly downloading that single SSIS package. Bottom line is you want to inspect or to edit a package that is already published on the server. Or, you have deployed something on the server but you are not sure if it is the right version. Your company do not use source control so you can’t easily see what was last published (Oh no!!). So, you have inherited a set of SQL Server 2012 Integration Services projects that have been deployed on a server.