June 6, 2012 at 8:40 am
Is it possible to develop SSIS packages in SQL SERVER 20012 for deploying in SLQ SERVER 2008?
June 6, 2012 at 5:47 pm
The marketing material says you can, but I have not tried it so could not say how accurate the claims are.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
June 7, 2012 at 3:48 am
opc.three (6/6/2012)
The marketing material says you can, but I have not tried it so could not say how accurate the claims are.
I don't think you can create a package in SQL 2012 and then run it on a SQL Server 2008.
You can create a 2012 package that connects to 2008 but still runs on a 2012 server.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
June 7, 2012 at 7:41 am
Koen Verbeeck (6/7/2012)
opc.three (6/6/2012)
The marketing material says you can, but I have not tried it so could not say how accurate the claims are.I don't think you can create a package in SQL 2012 and then run it on a SQL Server 2008.
You can create a 2012 package that connects to 2008 but still runs on a 2012 server.
You're right. Here is the article I was thinking of: SQL Server Data Tools FAQ. It was database project targeting I was thinking of.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
June 8, 2012 at 5:45 am
opc.three (6/7/2012)
Koen Verbeeck (6/7/2012)
opc.three (6/6/2012)
The marketing material says you can, but I have not tried it so could not say how accurate the claims are.I don't think you can create a package in SQL 2012 and then run it on a SQL Server 2008.
You can create a 2012 package that connects to 2008 but still runs on a 2012 server.
You're right. Here is the article I was thinking of: SQL Server Data Tools FAQ. It was database project targeting I was thinking of.
In the FAQ it says: SSDT targets: SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012 and SQL Azure.
As I see it you can develop SSIS-packages in SQL Server Data Tools and deploy it in SQL Server 2008.
June 8, 2012 at 5:46 am
Jan.Sundbye (6/8/2012)
opc.three (6/7/2012)
Koen Verbeeck (6/7/2012)
opc.three (6/6/2012)
The marketing material says you can, but I have not tried it so could not say how accurate the claims are.I don't think you can create a package in SQL 2012 and then run it on a SQL Server 2008.
You can create a 2012 package that connects to 2008 but still runs on a 2012 server.
You're right. Here is the article I was thinking of: SQL Server Data Tools FAQ. It was database project targeting I was thinking of.
In the FAQ it says: SSDT targets: SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012 and SQL Azure.
As I see it you can develop SSIS-packages in SQL Server Data Tools and deploy it in SQL Server 2008.
SSDT <> SSIS
And as I said before, you can create a package that connects to earlier versions of SQL Server, you just cannot run the package on such a server.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
June 8, 2012 at 6:02 am
I'll agree it is confusing. The article uses "SSDT" to refer to the whole product, including the SSIS development tools, however what they really mean when they say "target" is that the DB Admin tools (from SSMS) and Data Dude functionality (from Visual Studio 2010 Premium/Ultimate) that was folded into SSDT can target all those platforms. The SSIS development portion of SSDT can only target SSIS for SQL Server 2012. To manage SQL 2008 packages you will still need BIDS 2008, and for SSIS 2005 development you'll still require BIDS 2005.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
May 1, 2013 at 8:35 am
A SSIS 2012 package can read from and write to a SQL SERVER 2008/R2 database.
However, the package should be deployed into SSIS 2012.
We currently have SQL Server 2000 database + DTS packages and are attempting the following on our server -
- Use SQL Server 2008 R2 for database
- Upgrade DTS packages to SSIS 2012 packages
- Install SSIS 2012 on the server
- Deploy the new packages to FileSystem and schedule using task scheduler.
We have certain constraints on upgrading database to SQL Server 2012 and hence this workaround for now. Can only hope this works!
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply