Re: [MSAccessProfessionals] Migrate MsAccess Frontend with SQL Server Backend to Azure

I did not set it up but I believe it was the VM option. I could remote to the server using RDP or ScreenConnect and then run SSMS on it directly (normally I just use SSMS from my desktop to work with it). It was definitely not the single database option as we have multiple databases on the instance. 

I'll add that they have a very robust Internet connection in the office, so it wasn't a case of a slow connection.

Paul

------ Original Message ------

From: "drnorbert2002 via groups.io" <drnorbert=msn.com@groups.io>

To: MSAccessProfessionals@groups.io

Sent: 1/21/2026 3:30:46 PM

Subject: Re: [MSAccessProfessionals] Migrate MsAccess Frontend with SQL Server Backend to Azure

Paul, quick clarification — when you say your employer moved to Azure, were you using Azure SQL Database (PaaS) or SQL Server running in an Azure VM (IaaS)?

I'm trying to understand whether the issues you saw were more related to cloud latency in general, or specific to Azure SQL's PaaS constraints.

Thanks,
Norbert