As long as SQL and Sage are on the same VM, you're fine.  Just don't move only the data.

Hi Jay. Thanks for getting back to me quickly.

To be clear, what we're looking to do is eliminate MS SQL server and use Azure's hosted SQL service. So, the database would be in that and the only VM would be for Sage 300 itself. I've seen some discussions of this, including one other thread that indicates this might be possible, but I wanted to get more opinions on it. Do you have any knowledge of whether this is doable?

Thanks!

If you have less than 20 users, you should put them on the same server.  If you split them, make sure the VMs are on the same physical host.

I understand what you're saying, but what I'm wondering is if using Azure's hosted SQL (which is a managed service that doesn't have its own VM) is possible here as our client is looking to eliminate MS SQL server entirely. If they move to the cloud, they will have to purchase a very expensive, new MS SQL Server license and if they can avoid that by hosting their databases with Azure directly, it will save them a small fortune. Presently, Sage 300 is the only product of their line of business tools that we aren't sure supports this scenario.

You have a basic misunderstanding.  Hosted Sql is still MSSQL. 

I understand that, but you're discussing VMs. When you're using Hosted SQL, you don't manage a VM. You create a database that Azure fully manages, point your product to it and pay for usage. There can be subtle difference in database functionality and compatibility between the hosted offering and a "real" MS SQL server, so what I'm trying to figure out is if Sage 300 is compatible with this offering.

No, you still don't get it.  Hosted SQL is still MSSQL.  

OK...so it should in theory work then is what you're saying? You previously said to ensure it was best to keep it either on the same VM or on the same host, depending on the user count. As you don't manage an actual VM with Hosted SQL, would that cause potential issues?

We have many small to medium clients running on a single VM with Sage and MSSQL.  Azure, AWS, NetAtWork, they're all variations.  But if you think you can still run Sage with Sage programs on your local server with Sage data in the Azure cloud, forget it.

That's not the plan. We're moving all of the client's on-prem servers to Azure. So, they will have a Sage 300 VM in Azure and the database would be there too. Our hope was just to put it in Hosted SQL so we can eliminate the need for a separate Azure VM specifically to host the unmanaged version of MS SQL Server.

I think Azure SQL is different than SQL Hosted on Azure. Think of Azure SQL as SQL As A Service.

Sage does not support nor have they tested Azure SQL. I haven't tried it myself either.

I don't think sage support azure SQL - here's the requirement for sage 2023

LOL

he is asking about Azure SQL SaaS

This tell us what SQL product Sage 300 support?

but does not tell what features/functions/api/system-calls/etc...

Azure managed instance SQL (PaaS) supports everything in MS SQL 2017-2022

Azure SQL (SaaS) (DBaaS) does not.

What is Azure SQL? - Azure SQL | Microsoft Learn

Compare the database engine features of SQL Database and SQL Managed Instance - Azure SQL Database & SQL Managed Instance | Microsoft Learn

T-SQL differences between SQL Server & Azure SQL Managed Instance - Azure SQL Managed Instance | Microsoft Learn

Other than WebScreen, Sage 300 still looks like a Windows 95 Application.

Even the concept of how the network setup is done, it's like it was built before Windows workgroup or NetWare.

There is no Server & Workstation concept in its design, it's like a DOS v6.22 btrive system.

 All that it is a File Server & a SQL Server, then the client, that access those Server.

From Windows Server 2003, most software companies build real Server & Client Apps (3 tire), most of them were Java, but they were real. Only a few really good companies manage to build html5 apps.

it was the best most could do, plus it was more secure compared to what Sage 300 does.

no client had direct access to the database.

does Sage know what features of SQL they use or support?

Hey Gerry, I am curious what ended up being the answer here.  We are also in the process of buiding out a new environment in Azure and was curious if you could use their SQL Databases service.

I'm also curious on the outcome of the above. If it works l would rather not go with the lift and shift option (IaaS) but PaaS. Any response will be appreciated. 

There was an issue several years ago where long Azure SQL Server hostnames were a problem, and a more recent post (I can't find) complaining of poor performance due to latency between the Sage 300 Azure application VM and the Azure SQL service.  Considering it takes less than an hour to install a quick Sample data system, I *highly* recommend just going ahead and installing Sage 300 on your Azure VM (then take a snapshop for later before proceeding) and create SAMSYS, SAMINC, SAMLTD, PORTAL, STORE, VAULT in Azure SQL, link them to Sage 300, load up SAMINC, SAMSYS and SAMLTD, login as ADMIN and see what performance is like.  If you're not using the HTML5 Web Screens client/service then make sure you use the same access method users will use (AVD/RDS published app for example) for performance testing.  Maybe you can get a lot done on free Azure credits.  I think it will definitely be worth the investment of setting up this test environment and testing performance yourself and have some finance team staff take it for a spin.  If its slow in the base configuration then Production will be way too slow.  If its snappy with the sample deployment then it will be acceptable with the live data in there.  Take the guesswork out

When l saw that there are no clear responses, l also thought the best option will be to test it myself. Thank you .