Solved

Save a SSIS package to SQL Server or File System

Posted on 2014-03-04
2
380 Views
Last Modified: 2016-02-10
Hi all.

I'm working with our SQL Server 2008 and want to create a new SSIS package via the SQL Server Business Intelligence Development Studio, but I have a question as far as saving it to SQL Server or File System.

Which is the best practice? And why?

Also, when I create a new package and try to save it, I don't see the option to save it to SQL Server, it just asks me for a path. How can I save it to SQL Server?

Thank you in advance!
0
Comment
Question by:printmedia
2 Comments
 
LVL 39

Accepted Solution

by:
lcohan earned 500 total points
ID: 39904155
"How can I save it to SQL Server?"

You can use VS and create your SSIS packages as files then Import those into a SQL Server or for instance on a simple data Import/Export you can do that by using SQL SSMS under Database Tasks import/export wizard that will ask you at the end where you want to save it - File or Server?

As far as Best Practice...I always saved them as File so I can save them to my Source Safe repository and for versioning purpose.
0
 

Author Comment

by:printmedia
ID: 39904180
Ok, here's what I plan to do and let me know if this is ok:

(1) I  create the SSIS package in BI and save it to "File" which will save it on a secured folder on my network that gets backed up nightly.

(2) Then I go to "Integrated Services" and Import it to: Stored Packages --> MSDB.

(3) Then I go to the Microsoft SQL Server Management Studio and create a Job to run my newly created SSIS package every day.

Is this a correct way of doing it? If I needed to make changes to the SSIS package would I have to open it again in BI save it and then "reimport" it in Integrated Services like I did in step (2)?
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In this article I will describe the Detach & Attach method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
Here's a requirements document template for an integration project (also known as Extract-Transform-Load or ETL) based on my development experience as an SQL Server Information Services (SSIS) developer over the years.
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question