The question is can I use Visual Studio 2019 with the most current SSIS to create SSIS packages for SQL Server 2008? Or do I need to download an earlier version of Visual Studio?
I do not have access yet to execute on the server I am waiting for this and just doing some research to get tools ready in the mean time. So I have not tried anything yet.
You have to install SQL Server Data Tools (SSDT) for Visual Studio 2019.
This is the link
https://learn.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?redirectedfrom=MSDN&view=sql-server-ver15
Says that you can't.
Supported SQL versions
Integration Services packages SQL Server 2012 - SQL Server 2019
Unfortunately, SSIS 2008 is too old. Additionally, SQL Server 2008, and its SSIS, are out of support. I strongly suggest upgrading your SSIS to a later and supported version.
VS2019 supports SSIS development for the following SSIS versions:
2012
2014
2016
2017
2019
-- UPDATE --
can sql server2008 use ssis later than 2008? this is what i was trying
to establish
No, SQL Server version and SSIS version are one and the same.
-- UPDATE #2 --
BIDS (Business Intelligence Development Studio) can be found after installing the full version of SQL server 2008.
Check it out here: Creating a SSIS package in VS 2008
Which version of Visual Studio and SSDT-BI I need to use to create and deploy a SSIS project for SQL server 2008 R2?
You have to install Microsoft Visual Studio 2008 to deploy package for SQL Server 2008 or SQL Server R2 by default. (newer versions will not work correctly)
This Link contains very helpful informations:
https://learn.microsoft.com/en-us/sql/integration-services/install-windows/installing-integration-services-versions-side-by-side
There are a lot of links saying that newer versions of visual studio cannot deploy SSIS 2008 packages correctly:
Can SQL Server Data Tools work with SQL Server 2008 SSIS?
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/bff5e145-1c63-4221-b2ba-009ea96a9e05/can-i-use-vs2012-to-create-and-deploy-ssis-for-sql2008r2?forum=sqlintegrationservices
https://www.sqlservercentral.com/Forums/Topic1560322-364-1.aspx
But in theory, You can create SSIS 2008 package using Visual Studio 2012 or 2013. if you decide to try this you can refer to this link it may help
Can some one tell me whether the SSIS packages developed in Visual Studio 2012 or 2013 works in 2008r2 server or not ???
If yes, did any other software needs to be installed in the 2008r2 server?
Deployment is not any concern here. I just want to run the packages in 2008r2 server via sql agent job
Please help.
No. Backwards compatibility is not an option. A package built in 2014 will not run on 2012. A 2012 package will not run on 2008 and a 2008 package will not run on 2005.
However, forward compatibility does exist so a 2005 package will run on 2008. 2008 will run on 2012, 2012 on 2014.
While I don't think this is your scenario, if you have the 2012/2014 SSIS packages deployed to a 2012/2014 server, you could run them from the 2008 server's SQL Agent task. It'd just be a matter of scripting the catalog.create_execution and catalog.start_execution BOL
Having that SQL Script, add a job step task of SQL and point the context over to your 2012/2014 server.
MSDN at https://msdn.microsoft.com/en-us/library/mt204009.aspx contains an overview of all the supported VS/SQLServer version combinations.
Basically, for SQLServer2008R2 SSIS development you will need BIDS (from the SQLServer installation).
The VS2012/VS2013 tools support only SQLServer2012/2014 SSIS development.
For VS2015, the Februari preview release of the SSDT-BI tools is intended to support multi-targetting SSIS package development (but only SQLServer2012-2016, no 2008R2), see also in the comments at http://blogs.msdn.com/b/ssdt/archive/2015/12/16/sql-server-data-tools-preview-update-for-december-2015.aspx
Note there is also something called BIML which is able to generate SSIS packages for different versions of SQLServer (incl 2008R2) from the same source code, so you could possibly use VS2012/VS2013 with BIDSHelper and then as a last step maybe generate packages for SQLServer2008R2.
Currently I am creating SSIS packages for SQL server 2014 using Visual Studio 2012 and the SSDTBI for VS2012.This works well.
But I found some compatability issues with VS2012 for SSIS 2014(on web).I'm new to SSIS.I dont know what is that exact issues with VS2012?.And also they mentioned SSIS 2014 is compatible only with VS2013.Here i have mentioned the link below.
http://www.stefanjohansson.org/2015/02/issues-upgrading-an-ssis-solutionpackage-from-visual-studio-2012-to-vs-2013/
http://blogs.technet.com/b/dataplatforminsider/archive/201
3/11/13/microsoft-sql-server-data-tools-update.aspx
Can anyone tell me what is exact compatability issues for VS2012 with SSIS 2014?.I can not seem to find anything on google.
Thank you
According to msdn it possible.
On an instance of SQL Server 2014, you can import packages from an
instance of SQL Server 2008 or from an instance of SQL Server 2012,
but you cannot export packages to an instance of SQL Server 2008 or to
an instance of SQL Server 2012.
-
Run packages. You can run SQL Server 2008 Integration Services and SQL
Server 2012 Integration Services packages by using the SQL Server 2014
version of the dtexec utility or of SQL Server Agent. Whenever a SQL
Server 2014 Integration Services tool loads a package that was
developed in SQL Server 2008 or SQL Server 2012, the tool temporarily
converts, in memory, the package to the package format that SQL Server
2014 Integration Services (SSIS) uses. If the SQL Server 2008 or SQL
Server 2012 package has issues that prevent a successful conversion,
the SQL Server 2014 Integration Services tool cannot run the package
until those issues are resolved. For more information, see Upgrade
Integration Services Packages.
However, I would just use VS 2013 if you can.
When I try to install a new instance of SQL Server 2008 Express on a development machine with SQL 2005 Express already up and running, the install validation fails because the "SQL 2005 Express tools" are installed and I'm told to remove them.
What exactly does that mean?
After reading this article:
http://www.asql.biz/Articoli/SQLX08/Art1_5.aspx
I uninstalled the 2005 version of the SQL Management Studio but received the same error from the 2008 installer during my follow-up attempt.
Updates
1) Uninstalled the SQL 2005 Management Studio only. Received the same error from the 2008 install.
2) Removed all SQL 2005 common components. Received the same error from the 2008 install.
3) Installed the shared components from the SQL 2008 installation program. Received the same error from the 2008 install when trying to install the new SQL 2008 instance.
4) Uninstalled SQL 2008 components, rebooted, re-installed SQL 2005 Management Studio from installation media, rebooted, un-installed SQL 2005 Workstation Components from Control Panel, re-booted.
Installation of SQL 2008 is now proceeding as it should.
Seems likely that if I'd re-booted after update 2 above things would have gone more smoothly. :-(
Although you should have no problem running a 2005 instance of the database engine beside a 2008 instance, The tools are installed into a shared directory, so you can't have two versions of the tools installed. Fortunately, the 2008 tools are backwards-compatible. As we speak, I'm using SSMS 2008 and Profiler 2008 to manage my 2005 Express instances. Works great.
Before installing the 2008 tools, you need to remove any and all "shared" components from 2005. Try going to your Add/Remove programs control panel, find Microsoft SQL Server 2005, and click "Change." Then choose "Workstation Components" and remove everything there (this will not remove your database engine).
I believe the 2008 installer also has an option to upgrade shared components only. You might try that. Good luck!
In my case even after uninstalling all 2005 related components it didn't worked. I had to resort to a brute force way and remove following registry keys
32 Bit OS: HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90
64 Bit OS: HKLM\Software\Wow6432Node\Microsoft\Microsoft SQL Server\90
I had to unistall the Workstation Components and SSMS Tools Pack (SSMS Tools Pack is an add-in for Microsoft SQL Server Management Studio (SSMS) including SSMS Express.)
Installation of SQL 2008 is now proceeding as it should.
The problem is that SQL 2008 MS has a bug where connecting to a remote server (say like a service provider collocation) it will always try to open the fist db in the list, and since the possibilities of been ur db the first on the list are really low, it will throw and error and fail to display the list of dbs... which using sql 2005 management studio it just works.
Wished I could use SQL 2008 MS, but looks like as far I connect to remote SQL 2005, SQL 2008 is out of the question on my dev machine :(
Just Remove the the Workstation Components from Add/Remove Programs - SQL Server 2005.
Removing Workstation Components, SQL Server 2008 installation goes well.
Simply remove the Microsoft SQL Server Management Studio Express 2005 from control panel
N.B. These notes are for SQL Server Express 2008 R2 (so Microsoft still haven't made this any easier). I also realise that I complicated things by installing 32-bit SQL Server Express 2005 and 64-bit SQL Server Express 2008.
I followed the steps by Josh Hinman above. Uninstalling the SQL Server Express 2005 "Workstation Components" was not enough. I required an uninstall of the 2005 Management Studio as well.
I also tried the Upgrade route that Josh Hinman suggested by clicking on the 'Upgrade from SQL Server 2000, SQL Server 2005 or SQL Server 2008'. This route never gave me the option of installing the components side-by-side it just went straight through the process of upgrading from 2005 to 2008. It completed successfully - but hadn't actually done anything. Thankfully though it hadn't harmed any existing database instances. So be warned trying that route.
If you currently have Red Gate SQL Toolbelt, you will need to unistall that too before continuing. Somehow it adds a reference to the 2005 version of the SQL Management Studio.
I'am trying to install SQL SERVER developer 2008 R2 alongside SQL SERVER 2005 EXPRESS,
i went to program features, clicked on unistall SQL SERVER 2005 EXPRESS, and only checked, WORKSTATION COMPONENTS, it unistalled: support files, sql mngmt studio
After that installation of sql 2008 r2 developer went ok....
Hopes this helps somebody
I also had to remove the SMSS before it would get past that step.