This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 64%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECF%3C/text%3E%3C/svg%3E)
Are there any know issue: VS_NEEDSNEWMETADATA SSIS error running on SQL Server 2019 IaaS on Azure VM when connecting remotely to IaaS SQL Server on Azure VM that recently upgraded to 2022?
Any suggested solution for this error?
Remote source SQL Server IaaS on Azure SQL VM version:
Microsoft SQL Server 2022 (RTM-CU1) (KB5022375) - 16.0.4003.1 (X64) Jan 27 2023 16:51:31 Copyright (C) 2022 Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2019 Datacenter 10.0 <X64> (Build 17763: ) (Hypervisor)
Hi @Catameo, Fred (Taguig City 1634),
Have you change the target server version to SQL Server2022 and then deploy the package?
Regards，
Zoe Hui
If the answer is helpful, please click "Accept Answer" and upvote it.
Hello Zoe,
Tried to change SSIS project TargetServerVersion to SQL Server 2022 and redeploy packages, unfortunately, error persists. Any other suggestions?
Is it recommended to set to false ValidateExternalMetadata?
Thank you
Tried to set TargetServerVersion to SQL Server 2019, refresh and get latest metadata for source and target on the SSIS package but the error persists.
Also tried to set the ValidateExternalMetadata to false. The VS_NEEDSNEWMETADATA error message disappeared but the "No column information was returned by the SQL command" error persists.
Update on this. It seems the error disappeared when we removed the parameter on SQL command. It seems SQL Server 2022 does not work with the ? parameter on the SSIS SQL command. The SSIS has been running for several years now on SQL Server 2019. The error VS_NEEDSNEWMETADATA and "No column information was returned by the SQL command" suddenly popped up when our source remote SQL server upgraded to SQL Server 2022.