August 10, 2012 at 6:49 am
Hello,
i tried to migrate Packages from our stable 2008 R2 SQL Server with SSIS and Visual Studio 2008 to a new development SQL Server 2012 with SSIS and Visual Studio 2010 Shell.
I have converted the old SSIS Packages into the new Vistual Studio 2010 and created backups of the orld SSIS Packages.
I repaired Connections and can localy run the migrated Package.
Now i want to upload the lokal SSIS package to my SQL Server 2012, but i cant.
In my old environment (SQL 2008 R2 and Visual Studio 2008) i was able to upload packages by "file -> Save Copy of Package.dtsx As...". But in my new environment (SQL Server 2012 and Visual Studio 2010) i cant see this menu point.
Are there some changes in SQL 2012?
So currently i´m not able to upload my packages to SSIS Server.
August 10, 2012 at 7:11 am
some additional Informations:
my Workstation: Windows 7 64bit
Installed SQL Server 2012 Tools (SDK´s and Connection / Management Tools)
Server is a failovercluster with 2 servers: Windwos Server 2008 R2
I use the Visual studio brought with sql server 2012
October 25, 2012 at 1:54 am
Hello Thomas
I have the same problem, I am only able to copy my package to the file system.
Have you found a solution for your problem?
Yours
max
October 25, 2012 at 1:57 am
Are you using the project deployment model or the package deployment model?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
October 25, 2012 at 2:06 am
I do not deploy neither the project nor the package, I just want to use the "save copy of..." and choose the location Integration Server as decribed in
http://msdn.microsoft.com/en-us/library/ms137565.aspx
Similar as I did in BIDS forme times.
October 25, 2012 at 2:16 am
That's not what I asked 🙂 I asked which model you were using.
In SSIS 2012 you have two models:
* project deployment model: a new model, which has parameters and project connection managers. Projects are deployed as a whole to the SSIS catalog on the SQL Server database engine. The single unit of deployment is a project, not a package.
* package deployment model: the old model, used in SQL Server 2005 and 2008 (R2). Still available for backwards compatability. Single unit of deployment is a single package, which can be deployed to the MSDB database or the filesystem. If you use this model, you should see (package deployment model) next to your project name.
The link you provided is for the package deployment model, although it doesn't say it explicitly. MSDN is really confusing on that part.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
October 25, 2012 at 2:32 am
It is realy confusing:
1) I tried to deploy the whole in project deployment model, but Data Tools said: ".....the version of the specified SQL Server instance does not support the selected operation" (it is SQL Server 2008 SP2)
So I believe that you cannot deploy a project to an SSIS Server Version 2008
2) I changed to package deployment model and then I got my next surprise:
"Storing or modifying packages in SQL Server requires the SSIS runtime and database in the same version. ;(((((
should I 'll better wait using SQL 2012 until ....
October 25, 2012 at 2:43 am
Ah yes, I understand. You cannot deploy SSIS 2012 projects to SQL Server 2008R2 or older. You can only deploy to SQL Server 2012.
In Visual Studio 2010 (SQL Server Data Tools), you can only create SSIS 2012 projects. So if you want to create SQL Server 2008(R2) projects, you need to use Visual Studio 2008 or BIDS.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
October 25, 2012 at 3:09 am
So, I'll wait using SQL 2012
;((
The Office team worked better. There you can store an Excel 2003 with Excel 2007 or 2010.
:angry:
Thank you so far.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply