What can be affected includes the actual  number of people who can connect to your dbase (your PC store since it is dbase driven).      Depending upon your basic website configurations, and simultaneous web users,  you may experience connectivity time delays and unable to connect occurances.  What happens is that your server might limit the number of people who can connect to the dbase at the same time.  A new user wouldn't be able to connect if all resources are being used, until someone leaves the site AND that user session expires (by time or by closing a browswer window).

 

Also, your server has an application pool setting that may "crash" if you have too many resources using the same pool.   But chances are this won't be an issue with PC and regular sql settings.

 

OK, all this sounds alarming but if you  have a modern server, and limited leakage in web programs on the server, and running an SQL dbase versus an Access dbase, you shouldn't experience any real concerns.   Just check connection time to the server.

 

Best a suggestion would be to test it -  by using a ping program or someother type of program to "attack" your own server/storefront and checking the page load time.    Or - you can just ask all staff and people you know to try to place an order at the same time - and see what happens.  Pick the slowest day/hour and say at Wednesday 4:00PM lets try to place orders to confirmation page.  

 

How much traffic to your site do you receive and what is frequency of time on site?  These are some stats to look at. 

For admin, we decided to stay with current default times and just use password remember in FFox to assist in logging in again.  Afterall, if we are not actually doing anything from an admin stance, it makes sense to just log out.

 

/a