we are trying to migrate the database from 2019 express edition to 2017 enterprise edition , pls suggest which POA is best , how we will do this activity with any error . we will plan for migration through data tier application but we have one issue because here version and editions also different is it possible to migrate the database in this scenario. we have to migrate all the data like indexes and constraints and keys with table data .

we are trying to migrate the database from 2019 express edition to 2017 enterprise edition , pls suggest SQL Server databases are not backward compatible, you can not restore/attach a 2019 database to a 2017 server. You have to do a lot of manually work, you could e.g. script all objects and data SSIS package with Transfer SQL Server Objects Task

Hi @ Srinivas Naraipeddi Full agree with others, the best choice is to upgrade SQL server to the latest version 2022. Quote from MS document SQL server 2017 out of mainstream support at Oct 11, 2022. If you still want to migrate SQL server 2019 databases to SQL 2017, please follow the steps from this blog How to migrate a SQL Server database to a lower version If the answer is helpful, please click "Accept Answer" and kindly upvote it.

we are trying to migrate the database from 2019 express edition to 2017 enterprise edition , pls suggest which POA is best , how we will do this activity without any error .

Srinivas Naraipeddi 40

we are trying to migrate the database from 2019 express edition to 2017 enterprise edition , pls suggest which POA is best , how we will do this activity with any error .

we will plan for migration through data tier application but we have one issue because here version and editions also different is it possible to migrate the database in this scenario.
we have to migrate all the data like indexes and constraints and keys with table data .

2 answers

Olaf Helper 45,376 Reputation points

2024-10-17T09:48:33.3233333+00:00
we are trying to migrate the database from 2019 express edition to 2017 enterprise edition , pls suggest

SQL Server databases are not backward compatible, you can not restore/attach a 2019 database to a 2017 server.

You have to do a lot of manually work, you could e.g.

script all objects and data

SSIS package with Transfer SQL Server Objects Task
Please sign in to rate this answer.
Srinivas Naraipeddi 40 Reputation points

2024-10-17T10:32:45.3666667+00:00

is it not possible through Data tier Application SQL package ?

Erland Sommarskog 114.6K Reputation points MVP

2024-10-17T21:26:06.6366667+00:00

Maybe, if you are not using features that are new to SQL 2019. But I don't use DACPACs and BACPACS a lot, so I don't know.

But SQL 2017 has been out of mainstream support for some time (and SQL 2019 will also out of mainstream support in a few months). So I think it would be better to upgrade that instance to SQL 2022.

If you insist on keeping that instance on SQL 2017, you will have go through a number of extra hoops.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
CathyJi-MSFT 22,336 Reputation points Microsoft Vendor

2024-10-18T01:47:33.8433333+00:00

Hi @Srinivas Naraipeddi

Full agree with others, the best choice is to upgrade SQL server to the latest version 2022.

Quote from MS document SQL server 2017 out of mainstream support at Oct 11, 2022.

If you still want to migrate SQL server 2019 databases to SQL 2017, please follow the steps from this blog How to migrate a SQL Server database to a lower version

If the answer is helpful, please click "Accept Answer" and kindly upvote it.
Please sign in to rate this answer.
Srinivas Naraipeddi 40 Reputation points

2024-10-22T07:34:26.4066667+00:00

Hi CathyJi ,

I want to migration through Export data tier application feature pls share the steps How to do Migration through Export data tier application.

CathyJi-MSFT 22,336 Reputation points Microsoft Vendor

2024-10-22T07:56:19.4733333+00:00

Hi @Srinivas Naraipeddi

Please follow steps from MS document Export a Data-tier Application.

Erland Sommarskog 114.6K Reputation points MVP

2024-10-22T21:36:22.71+00:00

Out of curiosity, I tried exporting a data-tier application for a database on SQL 2019 and import it on SQL 2017. I was indeed successful, but I had to try a couple of databases before I was able to succeed.

For some databases, I was not even able to create a bacpac, because there were issues in the database. For other databases, I was not able to import the .bacpac, because it was using features supported in SQL 2017. (In my case, I had several databases with a UTF8 collation.)

But I must say that in the case where the .bacapc actually worked it was very smooth and painless.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

we are trying to migrate the database from 2019 express edition to 2017 enterprise edition , pls suggest which POA is best , how we will do this activity without any error .

2 answers

Your answer