September 10, 2012 at 1:15 pm
I installed all the services of SQL server 2012 (database engine, ssis, ssas, ssrs) on a sandbox with another existing version sql 2008 (db engine, ssis, ...)
The 2012 instances are named instances, and 2008 are default instances.
I read from this article: http://technet.microsoft.com/en-us/library/ms143731.aspx
it says after the second heading: You can install SQL Server 2012 Integration Services (SSIS) side-by-side with an existing instance of SQL Server 2005 Integration Services (SSIS) and SQL Server 2008 Integration Services (SSIS).
But in the table below: it says: You can only install one instance of the Integration Services service on a computer
This is confusing,
And when I connect to SSIS using SSMS, if default computer name, I connected to SSIS 10.50 which is 2008 version, there I cannot see the integration service catalog folder, but if I connet to the .\instance name, it will say doesn't support multi instances
Thanks
September 14, 2012 at 2:32 pm
I apologize, I am still new with SSIS 2012 and can only comment on one part of your post...
You will find your Integration Services Catalog located under the ".\[2012 named instance]" Database Engine node of SSMS, not the Integration Services node.
September 14, 2012 at 2:45 pm
Thanks, I found you can only install one instance of SSIS on it.
The microsoft doc is confusing to say they can co-exist.
February 26, 2013 at 12:43 am
Had the same issue briefly now... thought it was strange as i have the same setup on my laptop and that worked fine.
In summary:
You can have both versions of Integration services installed on a machine...
To see the integration services catalog on the sql2012 instance, you need to have the database running as well as integration services. Then you must use the sql2012 client to connect to the database engine and voila you will see it.
If you use an older version of the client, my experience is that i do not see the integration services client.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply