I won't address the different Azure options as I don't know them well enough. Others here are much better suited to compare them.
I have a fair amount of experience working with Azure and your biggest wildcard regarding redesign is how your existing app is structured. In short, you need to minimize the amount of data that moves back and forth between the app and the cloud. If you've already done that, there may be very little to redesign. For example, a form that pulls 1,000 records when it loads may work fine with an on premise server but be unusable with data in the cloud. Complex Access queries may need to be changed to views/stored procedures/functions/pass through queries/etc. When my employer moved to Azure from an on premise server, I had to tweak a few things in the various apps I created/support, but for the most part everything worked fine.
Paul
------ Original Message ------
From: "drnorbert2002 via groups.io" <drnorbert=msn.com@groups.io>
Sent: 1/20/2026 2:28:10 PM
Subject: [MSAccessProfessionals] Migrate MsAccess Frontend with SQL Server Backend to Azure
I am planning to migrate MS Access front end + SQL Server 2022 backend on Server 2022 on-prem to Azure architecture.
Anybody has any experience?
What is the fastest and most cost-effective Azure architecture with minimal redesign?
10 users-
SQL Database 2 Gib
MsAccess program 56 Kb
Azure SQL vs SQL Server VM decisions
Thanks,
Norbert
Tidak ada komentar:
Posting Komentar