Compatibility issues on Azure SQL migration assessment

Question

User1604699451 posted

My app was originally written in 2005.  It included ASP.NET Membership.  The DB has not been extensively reorganized since.  Now the app is being rewritten, targeted toward Azure SQL.  

When I ran a Data Migration Assistant for the database, it showed 27 "unqualified joins" that were all associated with Membership queries.

I'm thinking maybe I need to install a new version of Membership and hope that my app code doesn't get too confused with updated Membership calls.

Questions:

1) Is that the likely problem and resolution?

2) how do I to install a new Membership function in an existing database?

Any guidance on this would be appreciated.

Thanks!

Answer 1

User283571144 posted

Hi codequest,

As far as I know, if you use data migration migrate the sql 2005 database to new database it show "There are 0 breaking changes. 27 Behavior changes which are primarily unqualified joins."

It shows you 0 breaking changes. means nothing will get break or crashed if you upgrade.

27 behavior changes means the same feature that you used in SQL 2005 maybe works slightly different in azure sql. it can also affect on the performance. performance can increase or decreased.

So if it doesn't show the breaking changes, you could directly migrate the database to azure sql database.

Besides, we used identity instead of membership now.

If you want to know how to migrate the membership to identity, you could refer to this article.

Best Regards,

Brando

Answer 2

User1604699451 posted

Thanks, that helped me decide.