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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello Team ,
Am trying to get the DB backup from Microsoft SQL Azure (RTM) - 12.0.2000.8 and restore on Microsoft SQL Server 2019 (RTM-GDR) (KB5029377) - 15.0.2104.1 (X64) Aug 16 2023 00:09:21 Copyright (C) 2019 Microsoft Corporation Express Edition (64-bit) on Windows 10 Enterprise 10.0 <X64> (Build 19045: ) (Hypervisor). Below is the error encountered.
Now the Question could be why not connect Azure DB directly to SSMS. Due to firewall constraints we could not hence, this approach
Need to understand the versioning concept of Azure so as to have the same version locally.
An Azure relational database service.
![](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(220.8, 4%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Hi
Swathi Muthiyam (SX/BSV-TC2) •,
Just checking in to see if the provided suggestion helped. If this answers your query, do click Accept Answer and Mark Helpful for the same. And, if you have any further query do let us know. Thanks
Answer accepted by question author
Azure SQL Database is always running on the latest stable version of the SQL Server database engine. Your best bet is to upgrade your SQL Server instance to SQL Server 2022 (currently the latest version of SQL Server), next apply the latest cumulative update available for SQL 2022, then try to import the Azure Database bacpac (backup) to the SQL Server instance in your computer.
It did partially resolve the issue, while restore the Procedure which had spit with 3 params was not restored. Another observation is 2019 SSMS cant be used for 2022 server.