Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS packages backup Expand / Collapse
Author
Message
Posted Tuesday, September 23, 2008 3:27 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Sunday, December 7, 2014 9:00 AM
Points: 264, Visits: 1,513
Hi, I am developing SSIS packages in our development server. How do I backup my SSIS packages so that I do'nt lose those packages incase something happens to the dev box. Thanks!
Post #574806
Posted Tuesday, September 23, 2008 5:00 PM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Monday, December 15, 2014 12:03 PM
Points: 4,064, Visits: 5,372
If you're saving them to SQL Server, they're stored in msdb and will be backed up when you backup that database. If you save them to the file system, you could use a source control solution like Visual SourceSafe.

Greg
Post #574828
Posted Wednesday, September 24, 2008 7:34 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Sunday, December 7, 2014 9:00 AM
Points: 264, Visits: 1,513
Thanks for the reply. Per the properties of the SSIS package, the full path of the package shows as "C:\SSISpackage\package1.dtsx", so based on this I think the package is getting saved in C:\SSISpackage. If I want to save the package in SQL server how can I do that? Usually which one is preferable saving in a folder or saving in SQL server?
Thanks!
Post #575184
Posted Monday, September 29, 2008 9:34 AM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Monday, December 15, 2014 12:03 PM
Points: 4,064, Visits: 5,372
After you save the package to a .dtsx file, you can import it into SQL Server by opening SSMS, connect to Integration Services, expand Stored Packages, right-click on MSDB, and select "import package...".

Opinions vary on which storage location is better. We've chosen to store packages as files because we can use configuration files and because the packages seem to be easier to move from instance to instance.


Greg
Post #577799
Posted Tuesday, September 30, 2008 3:30 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, December 17, 2014 2:36 PM
Points: 2,850, Visits: 1,165
Storing packages in the file system is usually better for development, primarily because you can use source control. (Hopefully your source control archive is part of a regular backup.) You can only store the package itself in a server, but you can store a complete project in a file system. A project might include documentation files, a group of related packages, or anything else that might aide the development effort. In my opinion, package development should always be done with a Visual Studio project stored in a file system.

Is your package intended to execute on a server, or on a client? If it runs on a client the file system version is probably sufficient. If it runs on a server there may be good reasons for deploying the finished package to that server (stored in msdb). In a secure network environment, a remote server may not have access to the file system used by developers, and developers may not have rights to copy files over to the server. Developers can work with the file-based package without affecting the production copy. If a package is used for a critical scheduled job, there are more ways for it to fail if the server has to go over the network to another file system to find the package. It may be easier for the DBA to manage security issues if the package is on the server.



Post #578723
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse