Cloud Based Back End... (1 Viewer)

[GUIDO22]

Having recently split my 80MB database into a front and back end parts ... if i were to host the 'back end' (tables) in the cloud .. what is required to enable connectivity to the _BE from the 'front-end' client interface ?
Are there any perceived issues running across the internet in this way... (we will shortly have a 'leased line' of upto 200 Mbps for connectivity so bandwidth shouldn't be too much of a problem....)

Thanks in advance.

 

[Minty]

We use Azure SQL databases in approx. 80% of our client applications.
Don't expect to host an Access backend in the cloud and get even slightly reliable performance.

With Azure SQL There are distinct advantages, but some things you should plan for.

• Don't drag an entire tables data over to a form, filter it or load it with an empty record first.
• Create views on the server where you have complicated multi-table queries.
• Keep local copies of seldom changed look-up lists (Countries, States, Currency Codes, etc.), refresh them on database load.
• Use the server power for complicated processes with pass-through queries and stored procedures.

A million other things will crop up but these are some of the basics.

 

[GUIDO22]

We use Azure SQL databases in approx. 80% of our client applications.
Don't expect to host an Access backend in the cloud and get even slightly reliable performance.

With Azure SQL There are distinct advantages, but some things you should plan for.

• Don't drag an entire tables data over to a form, filter it or load it with an empty record first.
• Create views on the server where you have complicated multi-table views.
• Keep local copies of seldom changed look-up lists (Countries, States, Currency Codes, etc.), refresh them on database load.
• Use the server power for complicated processes with pass-through queries and stored procedures.

A million other things will crop up but these are some of the basics.

Thanks for the your feedback, not quite what I had expected nor hoped for as a 'quick-fix'...

 

[CJ_London]

A simpler option but still with costs is to use terminal server or citrix - plenty of online providers about. Terminal server will host both front and back end, backend in a shared folder, front end in each user profile - much the same as on a LAN. Licensing is typically on a per user basis, with a minimum number, perhaps 1 perhaps 3 or 5 depending on the provider. Choose one that has servers in your locale (i.e. country/continent)

Benefits are:

• performance - similar to if users have the BE on their own machine plus the only internet 'traffic' are screen updates.
• Accessible from any device located anywhere with an internet connection that can run remote desktop (which is what users use to connect to terminal server) which includes iOS and Linux.
• To setup, simply copy across FE and BE and relink with the new path to the BE.
• Another benefit is if the user loses their connection, their FE will stay open (subject to any timeouts/maintenance routines) reducing the risk of corruption

Users will each require an access license or use runtime in which case so you may need to make some changes to your app if they require use of the ribbon, navigation window or right click menus.