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 12»»

Can SSIS 2012 run against SQL 2014 database? Expand / Collapse
Author
Message
Posted Monday, July 28, 2014 3:00 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, July 29, 2014 1:28 PM
Points: 7, Visits: 13
We are considering installing SQL 2014 to take advantage of columnstore updateable indexes for an upcoming ETL process but am wondering if an SQL 2014 database can be accessed with SSIS 2012. We are planning on a centralized SSIS server, but the SSIS group has already begun developing with SSIS 2012 and they are hesitant to switch over at this time to SSIS 2014 as they are afraid it will negatively impact their development timeline. Any thoughts?
Post #1597072
Posted Monday, July 28, 2014 3:03 PM This worked for the OP Answer marked as solution


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:23 AM
Points: 12,954, Visits: 10,724
Yes, you can connect from SSIS 2012 to SQL 2014.

There are no notable difference between SSIS 2012 and 2014, aside from the development environment (SSIS 2014 uses VS 2013), so the SSIS group shouldn't expect that much of a negative impact.




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 #1597074
Posted Monday, July 28, 2014 3:07 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, July 29, 2014 1:28 PM
Points: 7, Visits: 13
Thank you for your prompt response. This definitely helps in our decision making.

BTW - I was just reading one of your articles about SSIS deployments and greatly appreciate your knowledge share as SSIS is something that I am just learning about now.

Jacki
Post #1597078
Posted Tuesday, July 29, 2014 6:14 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 5:46 AM
Points: 13,752, Visits: 28,148
While you can connect to it, you won't be able to access 2014 objects and may run into issues with objects that contain 2014 only constructs (clustered columnstore).

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1597241
Posted Tuesday, July 29, 2014 6:24 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:23 AM
Points: 12,954, Visits: 10,724
Grant Fritchey (7/29/2014)
While you can connect to it, you won't be able to access 2014 objects and may run into issues with objects that contain 2014 only constructs (clustered columnstore).


I don't really see an issue when using SSIS 2012 to read/write from SQL Server 2014.
SSIS either issues just a select statement or it just sends data. How SQL 2014 handles it is of no concern for SSIS.




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 #1597247
Posted Tuesday, July 29, 2014 7:48 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, July 29, 2014 1:28 PM
Points: 7, Visits: 13
Our initial thoughts for considering SQL 2014 for the database was to take advantage of updateable columnstore indexes to enhance the performance of our ETL process. Are you saying that when SSIS 2012 is used to update a SQL 2014 database, you don't believe that we would take advantage of this 2014 feature?
Post #1597295
Posted Tuesday, July 29, 2014 7:55 AM This worked for the OP Answer marked as solution


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:23 AM
Points: 12,954, Visits: 10,724
jhamilton 47458 (7/29/2014)
Our initial thoughts for considering SQL 2014 for the database was to take advantage of updateable columnstore indexes to enhance the performance of our ETL process. Are you saying that when SSIS 2012 is used to update a SQL 2014 database, you don't believe that we would take advantage of this 2014 feature?


Yes you can. SSIS will merely send some SQL statements to SQL Server which the database engine itself will execute.
SSIS does not care what SQL Server does behind the scenes.




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 #1597301
Posted Tuesday, July 29, 2014 8:00 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, July 29, 2014 1:28 PM
Points: 7, Visits: 13
Thank you Koen for the clarification.

Jacki
Post #1597307
Posted Tuesday, July 29, 2014 8:17 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 5:46 AM
Points: 13,752, Visits: 28,148
As long as we're talking about straight T-SQL commands, you should be fine. If you start trying to access objects directly through SSIS, you may hit issues. Forward compatibility is not guaranteed like backward compatibility.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1597313
Posted Tuesday, July 29, 2014 11:33 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:23 AM
Points: 12,954, Visits: 10,724
Grant Fritchey (7/29/2014)
As long as we're talking about straight T-SQL commands, you should be fine. If you start trying to access objects directly through SSIS, you may hit issues. Forward compatibility is not guaranteed like backward compatibility.


How are you going to access objects directly? Through SMO?




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 #1597430
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse