Answered by:
Saving Visual Studio 2013 SSIS Packet

Question
-
Hi,
I am trying to save a packet created in VS 2013 in SQL Server 2014. But the save as option displays only file structure in my drive but no option is there for sql server !!
Wednesday, April 29, 2015 1:00 PM
Answers
-
Hi ganeshsg,
When we click “Save Copy of <package file> As” on the File menu in Project Deployment Model, we can only save the package on the disk.
Please note that the procedures in the article is about Package Deployment Model. So if we want to save a copy of package to SQL Server, we should change the Model first, then refer the steps in the article.
To convert the Model from Project Deployment Model to Package Deployment Model, please right-click the project to select “Convert to Package Deployment Model” option in the Solution Explorer. If a package uses features unique to the project deployment model, such as parameters, then the package cannot be converted. So please avoid use features unique to the project deployment model.
The following screenshot is for your reference:
If there are any other questions, please feel free to ask.
Thanks,
Katherine XiongKatherine Xiong
TechNet Community Support- Marked as answer by ganeshsg Thursday, April 30, 2015 7:29 AM
Thursday, April 30, 2015 1:48 AM
All replies
-
Hi,
you could connect to SSIS using SQL Server Management Studio and upload the package there via context menu "Import Package".
Cheers
Martin
Wednesday, April 29, 2015 1:50 PM -
Hi ganeshsg,
When we click “Save Copy of <package file> As” on the File menu in Project Deployment Model, we can only save the package on the disk.
Please note that the procedures in the article is about Package Deployment Model. So if we want to save a copy of package to SQL Server, we should change the Model first, then refer the steps in the article.
To convert the Model from Project Deployment Model to Package Deployment Model, please right-click the project to select “Convert to Package Deployment Model” option in the Solution Explorer. If a package uses features unique to the project deployment model, such as parameters, then the package cannot be converted. So please avoid use features unique to the project deployment model.
The following screenshot is for your reference:
If there are any other questions, please feel free to ask.
Thanks,
Katherine XiongKatherine Xiong
TechNet Community Support- Marked as answer by ganeshsg Thursday, April 30, 2015 7:29 AM
Thursday, April 30, 2015 1:48 AM -
Thanks Martin, it worked with the method suggested by KatherineThursday, April 30, 2015 7:29 AM
-
Thanks a lot Katherine. It worked the way you described :)Thursday, April 30, 2015 7:29 AM
-
Thank you Katherine!Thursday, October 5, 2017 9:24 PM