The most recent release of SQL Server is SQL Server 2025, there is no SQL Server 2026.
As for which version to migrate to, I would say SQL 2025 if it is only a matter of the Database Engine. There may be some initial bugs, but SQL Server is a mature product, so existing features tend to be stable. If there are more glaring bugs, they are more likely to be with new features. But be sure to apply Cumulative Updates when they come out!
One reason I suggest SQL 2025 is that SQL 2025 will be in mainstream support for five years, while SQL 2022 only have two years left. Which means that you will soon be in for an upgrade again. Whichever version you move to, you will need perform testing, so that you don't run into issues.
When it comes to SSIS and Visual Studio, I can't speak to these, since I don't use them myself. My understanding is that it can take some time before full support for the new version appears on the tooling side. Also, while Visual Studio has the 2026 moniker, I would not expect it as such to understand SQL 2025, which was released later.
Answer from Erland Sommarskog on learn.microsoft.comThe most recent release of SQL Server is SQL Server 2025, there is no SQL Server 2026.
As for which version to migrate to, I would say SQL 2025 if it is only a matter of the Database Engine. There may be some initial bugs, but SQL Server is a mature product, so existing features tend to be stable. If there are more glaring bugs, they are more likely to be with new features. But be sure to apply Cumulative Updates when they come out!
One reason I suggest SQL 2025 is that SQL 2025 will be in mainstream support for five years, while SQL 2022 only have two years left. Which means that you will soon be in for an upgrade again. Whichever version you move to, you will need perform testing, so that you don't run into issues.
When it comes to SSIS and Visual Studio, I can't speak to these, since I don't use them myself. My understanding is that it can take some time before full support for the new version appears on the tooling side. Also, while Visual Studio has the 2026 moniker, I would not expect it as such to understand SQL 2025, which was released later.
Thank you for your response. Installations on the new server will be for 2022, including Visual Studio 2022 and SQL Server 2022. DWH tables are located in Oracle 19c. "Microsoft Connector for Oracle" will also be installed.
How to install SSIS PowerPack in Visual Studio 2026 - Getting Started - ZappySys Community – SSIS & API Connectors, ODBC Drivers, ETL Support Forum
VS 2026
sql server - Existing SSIS package not loading correctly in newer version of Visual Studio - Stack Overflow
How to fix "Could not find or load a type. (Exception from HRESULT: 0x80131522)" in Visual Studio 2026
Videos
Have you guys already switched to VS2026, or are you waiting for the full release? Is it worth it to already switch or are there still some breaking issues?
If anyone in the future runs into this issue:
- Install Visual Studio 2019,
- Instal SQL Server Integration Services via the extension menu in VS 2019,
- Open the SSIS project in question, open properties, change deployment target to SQL Server 2022,
- (Possibly optional) Upgrade all packages by right clicking on the ssis folder and chosing the upgrade option.
After this, I have been able to open my project in Visual Studio 2022 Community [preview] without getting any of the errors from before.
Do you have the ispac files from a previous good build? I exported my problem children from the SSISDB, and used the create new project from ispac file option in visual studio. They converted just fine that way, then could replace the project that wasn't working.
Oh and I also needed to change the db connections to use the new oledb drivers. Since 2019 was the last change exit for that version.
Hi! So I have visual studio 2022 and I’m trying to download the SQL server integrations services extension.
But it comes back with the following error when installing.
Requested metafile operation is not supported (0x800707D3)
Does anyone know what I need to do? I’ve tried so much and it’s my company laptop so I can’t exactly get Microsoft to remote on to help lol.
For context, I have data tools 2017 installed and the ‘sql server analysis services’ extension downloaded perfectly fine!!
Thanks for the help!!