MS SQL hosting for Access Front End

Posted on 2011-09-10
Medium Priority
Last Modified: 2012-05-12
I am looking for a MS SQL 2008 (preferrable R2) database.  I have looked and read through many many reviews but would like the opinions of you professionals.  

Basically the front end will be MS Access and connect through ODBC to my hosted DB.  One step further I am looking at Sharepoint hosting for some of the Access web forms (2010), but the DB is the most important part as of now.  

I have looked very close at 1&1, WebHost4Life, ServerMart and a couple others.  These three stand out to me the most but what is your opinions?  Thanks in advance.
Question by:pskeens
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +2
LVL 42

Expert Comment

ID: 36517838
I have to question whether you will get acceptable performance with the FE-BE connection at WAN speeds.  You may be hosting the Access web forms sooner than you think.

Author Comment

ID: 36517847
I have done it before and performance was pretty good.  THis is one reason I want a good host with good performance and stability.  

Expert Comment

by:Kishan Zunjare
ID: 36518650
You can go with ServerMart.

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

LVL 23

Expert Comment

ID: 36518664
If you want an enlightened advice about how a hosted SQL Server database would perform using an Access Front end, you must to provide more details about connectivity, network bandwidth and host database size.  You also need to provide us with information as to how many people will be using the database front end.  

If on the other hand, you already made up your mind onto the solution and simply want us to provide you with a good host for SQL Server, then the question seems to have been already answered.
LVL 23

Expert Comment

ID: 36518665
<<I have done it before and performance was pretty good.  >>
Some words of caution: the fact that you had good performance by using the system by yourself does not mean you will get good performance if many people connect at the same time.   Sorry but that is the way SQL Server works.

Hope this helps...

Accepted Solution

Armen Stein - Microsoft Access MVP since 2006 earned 1000 total points
ID: 36519069
You can't use Access 2010 web forms for data hosted in SQL Server.  They are restricted to SharePoint tables only.  And Access client forms cannot be converted to Access web forms.  So if this is a direction you think you might go, be aware that you might be looking at a rewrite later.

You'll need to make sure your Access FE is optimized for using SQL Server, especially over a WAN.  It can be done, but you have to be careful.  I've written a PowerPoint presentation on techniques for using Access as a client-server front-end to SQL Server databases.  It's called "Best of Both Worlds" at our free J Street Downloads Page:


It includes some thoughts on when to use SQL Server, performance and security considerations, concurrency approaches, and techniques to help everything run smoothly.

Regarding SQL Server hosting, there are a lot of options.  There are many hosting companies that provide it, including us.  You can get shared hosting (yours is one database among many on a server) or you can get virtual private server (you get the whole server).  In all of these, prices vary greatly based on capacity, reliability, flexibility, customer service, etc.  I've heard stories of problems with the cheap ones.

And then there's SQL Azure - have you considered that?  It has its own pros and cons over regular SQL Server hosting.  Luke Chung has an article on using it:

Hope this helps,
LVL 42

Expert Comment

ID: 36520665
Some very good and relevant comments.  I do concur...

The proposed configuration does not scale well and does not migrate to Sharepoint Access Services without abandoning SQL Server.  If the backend is SQL Server hosted over a WAN connection, then you need a middle tier that's also hosted such that you can get much higher bandwidth between the application and the data.


Author Comment

ID: 36540456

What are you referring to as a middle tier?

I have it hosted now over WAN and the performance is good for development.  Yes this will differ when I get concurrent users but we are only talking about 5-8 concurrent users at the same time maximum.  On average it will be 2-3 I would imagine for now.  

The future plan is to move it all in house but I have to get it running for now.
LVL 42

Assisted Solution

dqmq earned 1000 total points
ID: 36540678
>Middle Tier
The FE is at the workstation. The FE presents info to the user and accepts user input, makes requests to the middle tier when, for example the "submit" button is pressed.  The middle tier processes the input and submits requests to the data BE.  

This is the architecture of a 3-tier client-server.  In ASP, for illustration, the browser is the FE, the ASP page is the middle tier, and the DBMS is the back end.  Sharepoint Access Services is another example of a middle tier: the browser on the workstation, Sharepoint in the middle and SQL Server in the backend.

The important part of the equation is that there is relatively little traffic on the WAN between the FE and the middle tier.  But the middle tier can be connected to the BE at LAN speeds which are needed for moving lots of data.

Two tier configurations (which you are considering) work fairly well at LAN speeds, but they don't scale so well at WAN speeds.  It's not so much about the number of users, but about the amount of data moving between FE and backend.  For example, it's entirely possible that Access will pull an entire table over the network in order to extract a single record from it.  And performance obviously goes south.

Having said that, Access is really pretty good about pushing data work to the backend.  And good designs, use of passthru queries and other server-side mechanisms can minimize the amount of traffic that flows between the FE and the BE.  But, it still takes a fair amount of dilligence and server-side expertise to avoid performance issues when the FE and BE are connected over the WAN.  



Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Windocks is an independent port of Docker's open source to Windows.   This article introduces the use of SQL Server in containers, with integrated support of SQL Server database cloning.
Instead of error trapping or hard-coding for non-updateable fields when using QODBC, let VBA automatically disable them when forms open. This way, users can view but not change the data. Part 1 explained how to use schema tables to do this. Part 2 h…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…
Visualize your data even better in Access queries. Given a date and a value, this lesson shows how to compare that value with the previous value, calculate the difference, and display a circle if the value is the same, an up triangle if it increased…

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question