Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Can SQL Server Data Tools work with SQL Server 2008 SSIS?

Can I use the new SQL Server Data Tools that come with SQL Server 2012 to create SSIS packages for SQL Server 2008?

I work with both SQL Server 2008 and SQL Server 2012 and I am wondering if I can use SSDT to create and maintain SSIS on both.

like image 846
Mark Arnott Avatar asked May 04 '12 14:05

Mark Arnott


People also ask

Is Ssdt backwards compatible?

SSDT is backwards compatible, so you can always use the newest SSDT to design and deploy databases, models, reports, and packages that run on older versions of SQL Server.

Does Microsoft still support SQL Server 2008?

Microsoft SQL Server 2008 R2 - Microsoft Lifecycle | Microsoft Learn. This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Which SQL Server is compatible with Visual Studio 2008?

Since SQL Server 2008 is not supported in Windows 10, we have to upgraded it to SQL Server 2017 or SQL Server 2019.

Is SSIS included in Ssdt?

SSDT installs the following things: The SSIS package design and development tools, including SSIS Designer. 32-bit SSIS components only. A limited version of Visual Studio (if a Visual Studio edition isn't already installed).


2 Answers

No. See problem with deploying ssis 2010 package

It seems that the backward compatibility offered by SSDT does not apply to SSIS.

like image 153
Sentinel Avatar answered Oct 06 '22 16:10

Sentinel


Everyone wants a smooth integration process that will allow for proficient system performance. In theory, the SQL Data tools package should work well with server SSIS (SQL Server Integration Services) 2008. Get the intended benefits of both systems when each is installed properly.

In theory, SDT should work with SSIS 2008, as the SQL Data tools is compatible with versions of SSIS dating back to 2005. However, more than a few have complained of getting "not supported" error messages. Some have found that answers lie in their installment procedures, while others have used improper versions of SSIS 2008. Overall, however, the underlying issues lie in the unique qualities of the 2008 system.

One important system aspect to keep in mind is the changes that took place when the 2008 version of the integration system was "rolled out." The new features were to better support the day-to-day activities of administrators than the 2005 and other versions. The advancements in individual components of the 2008 version made it more intuitive but, perhaps, inadvertently more complex to integrate with with other systems. For example, its policy-creation configurations are broken into facets, which are meant to be "matched" to the conditions of your policy. While this offers manual control, it's possible that other systems such as SDT will not integrate with 2008 as easily.

In light of the unique qualities of the 2008 version, as opposed to its predecessors, special attention to specific integration maneuvers is necessary. Also keep in mind that the SSIS 2008 R2 version yields more problems than the standard version.

The changes to SQL 2008 also include some discontinuations. In the move to this particular version, there was a large swath of features that were discontinued. As a result, the version lacks much backward compatibility. These conditions may require significant changes in your other systems.

like image 34
matt smith Avatar answered Oct 06 '22 17:10

matt smith