#Visual studio 2017 sql server 2008 install
#Visual studio 2017 sql server 2008 update
#Visual studio 2017 sql server 2008 upgrade
#Visual studio 2017 sql server 2008 windows

When you have confirmed that your system satisfies the above prerequisites, you can navigate to the KingswaySoft website at to download the installation package.Īfter you download the package, install the software by following the installation wizard. NET Framework 3.5 is required, which is generally installed along with SQL Server installation. When working with SQL Server 2008 or 2008 R2.NET Framework feature or install it by downloading it from the Microsoft website. For SSIS 2014 or lower, you may turn on the.NET Framework 4.6 (or above) is generally a prerequisite. Our software requires the installation of.

#Visual studio 2017 sql server 2008 windows

In such cases, Windows Installer 4.5 needs to be installed by downloading it from the Microsoft website. Still, it is definitely not recommended, nor do we officially support such installations.

If working with SSIS 2008, it might be possible to work with Windows Server 2003 R2 (even Windows XP for development workstation).

Windows Server 2008 should work fine for SSIS version up to 2014, but we highly recommend upgrading to a more recent version due to its support status with Microsoft.

Windows Server 2012 or Windows Server 2012 R2 should work fine for SSIS version up to 2016.

We generally recommend Windows Server 2016 or greater (Including Windows Server 2019 and potentially future Windows Server versions).

For server system (mostly for runtime deployments).

#Visual studio 2017 sql server 2008 upgrade

Windows 8.1, 8 or 7 should work fine with our software installation, which supports most SSDT versions and SQL Server 2016 or below, but we highly recommend you upgrade to Windows 10 because of its support status with Microsoft.We generally recommend Windows 10, version 1507 or greater.For desktop system (mostly for development workstations).In summary, our software should work for the following Windows operating systems. The general guideline is the newer the operating system is, the better. We don't have any additional requirements in terms of the operating system as long as it satisfies the minimum requirements of SSIS runtime or design-time. Windows operating system requirement largely depends on the version of SSIS runtime or design-time selected. The Business Intelligence Development Studio that is shipped with the installation media of the corresponding SQL Server version. Packages created using SSDT 2015 need to have their project's TargetServerVersion setting set to ' SQL Server 2012' in order to work with SSIS 2012.Packages created using SSDT 2017 need to have their project's TargetServerVersion setting set to ' SQL Server 2012' in order to work with SSIS 2012.SSDT for Visual Studio 2017 (not recommended due to potential compatibility issues with ISV solutions).Packages created using SSDT 2019 need to have their project's TargetServerVersion setting set to ' SQL Server 2012' in order to work with SSIS 2012.SSDT for Visual Studio 2019 (not recommended due to potential compatibility issues with ISV solutions).SSDT-BI for Visual Studio 2012 (recommended most reliable).Packages created using SSDT 2015 need to have their project's TargetServerVersion setting set to ' SQL Server 2014' in order to work with SSIS 2014.Packages created using SSDT 2017 need to have their project's TargetServerVersion setting set to ' SQL Server 2014' in order to work with SSIS 2014.Packages created using SSDT 2019 need to have their project's TargetServerVersion setting set to ' SQL Server 2014' in order to work with SSIS 2014.

#Visual studio 2017 sql server 2008 update

Note: When using SQL Server 2014, a cumulative update is required (a recent service pack, such as one of the following, is preferred) to run our software during runtime.įor SSIS design-time, you should install the version of SSDT (SQL Server Data Tools) or BIDS (Business Intelligence Development Studio) that aligns with the SQL Server version that you plan to use for your final deployment (the runtime).