December 7, 2012 at 10:49 am
This is a really basic question but I can't seem to figure out how to save a copy of an SSIS package to the SQL Server. I've saved it locally but I want to upload it to the server.
When I used BIDS, I just:
1. Double-clicked on the package
2. Chose file > Save Copy of Package As
3. Selected SQL Server as the package location and entered the server name
Now I'm using SSDT. When I choose the same option, "Save Copy of Package As" it doesn't show the option for package location.
I was able to upload it by logging into integration services from SSMS and importing the package but I thought there had to be a way to do it from SSDT.
Sorry, I know it's a stupid question. I've only been at this for 2 months. :unsure:
December 7, 2012 at 1:09 pm
Silly question, but what is SSDT? Is that something new in SQL 2012?
I personally have always saved to filesystem first so we can sourcesafe the packages, or at the very least I have a copy somewhere that wasn't mangled by a server crash. Then I just import via SSMS. *shrugs*
That's partially because the 2k5 version of that interface directly to the server used to misbehave heavily for me. I know others have gotten a lot of work from it but it was just always frustrating to me, so file-import worked just fine. Also gave me some coverage if something went screwy.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
December 7, 2012 at 1:43 pm
Evil Kraig F (12/7/2012)
Silly question, but what is SSDT? Is that something new in SQL 2012?
Yep, new in 2012. Data Tools as opposed to BIDS. It's kind of a mashup between VS and SSMS in that it gives you an object explorer and the typical Visual Studio interface.
December 11, 2012 at 5:17 am
In SQL Server 2012, there is a new package deployment model called, Project deployment model, where we can deploy into SQL Server. In SSDT, we can deploy the project to SQL Server SSIS catalog database. SSIS Project is containment of packages and Parameters. Refer to http://msdn.microsoft.com/en-us/library/hh213290.aspx for more information.
March 8, 2013 at 9:21 am
Hello Hogpen,
We are having the same issues. The save copy of package dialog box is different. Any solutions?
Thanks
March 8, 2013 at 10:28 am
Skur,
My solution was to log into SQL Server Management Studio, select Integration Services as the Server type then right click on the folder you want to import to. Right click, select Import Package and upload the package from your local machine with File System as the package location.
Hope that helps.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply