Is it possible, probably. Is it recommended, no. There's A LOT of traffic back and forth to the SQL server and Sage share. You risk unhappy users and possible data corruption.

You would be better off setting up a terminal server with a published app for users over the WAN.

Any idea on what that traffic is? 

Would the DB be currupted if session is lost or something like that?

any best practices articles? And bandwidth and latency requirements?

Thank you. 

I don't know what the average amount of traffic is. It depends on what they are doing and the size of the database.

The only articles I know of that you can check out are the Compatibility Guides. Afaik, they make no mention of bandwidth or latency requirements.

Ping is king. With the number of requests back and forth to the SQL server, latency will start to really add up. You could have an existing user on the LAN post a batch or run a report, but open the DBSpy utility that comes with Sage first, if you want to get an idea of the kind of traffic. Or you could probably monitor/trace on the SQL Server to see the kind of traffic.

And that is just the SQL server. There is also the Sage shared data directory to factor in. And, if you are not using the full client install, program files that go across the network.

You are welcome to try it, or ask Sage Support, but I would never recommend it to any of my customers. In this scenario, I would recommend a TS (on the LAN, of course) with a published app.

Have you ruled out using the web screens?