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

Create SSIS package in SQL SERVER 2012 for SQL SERVER 2008 Expand / Collapse
Author
Message
Posted Wednesday, June 6, 2012 8:40 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, August 29, 2014 5:46 PM
Points: 182, Visits: 737
Is it possible to develop SSIS packages in SQL SERVER 20012 for deploying in SLQ SERVER 2008?
Post #1311909
Posted Wednesday, June 6, 2012 5:47 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:32 AM
Points: 7,135, Visits: 12,745
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
Post #1312249
Posted Thursday, June 7, 2012 3:48 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 9:00 AM
Points: 13,520, Visits: 11,313
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.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1312371
Posted Thursday, June 7, 2012 7:40 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:32 AM
Points: 7,135, Visits: 12,745
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
Post #1312501
Posted Friday, June 8, 2012 5:45 AM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, November 4, 2014 2:57 AM
Points: 487, Visits: 258
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.
Post #1313068
Posted Friday, June 8, 2012 5:46 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 9:00 AM
Points: 13,520, Visits: 11,313
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.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1313070
Posted Friday, June 8, 2012 6:02 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:32 AM
Points: 7,135, Visits: 12,745
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
Post #1313076
Posted Wednesday, May 1, 2013 8:35 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Sunday, November 2, 2014 3:18 PM
Points: 31, Visits: 43
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!
Post #1448440
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse