[AccessD] Article on upgrading

Susan,

1. Does your database need to be available at all times?  If so, then online
backups are required and JET is not your answer.

2. How many hours worth of data can you afford to loose?   If none or only
an hour or two, then look to something other then JET.

3. How much data do you have?  If tables with anything more then hundreds of
thousands of rows, then be looking to something other then JET.

4. How many users do you have? Generally if more then 15-20, you want to be
on something other then JET because if your DB corrupts, that many people
not working is costly.


  For some of the above, they are not hard and fast rules.  There are many
of apps out there that go further in terms or user or records and work quite
well.  The above should be considered the starting point of where you should
start becoming uncomfortable with using JET.

Jim.



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Thursday, July 28, 2011 12:55 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] Article on upgrading

I'll be writing about upgrading to SQL Server and I'd like to include as
many of you in it as possible -- you'll get credit and a link -- it's a nice
thing to show the boss and clients. 

The angle is -- questions you should ask when deciding whether to upgrade an
Access database to SQL Server (Express is Okay too) -- specific to the
decision-making process. Anything you think someone considering the move
should evaluate before doing so -- but I'll be writing it from a "questions
you should ask" perspective. 

It'll be interesting reading for the list too I think, so if nobody objects
-- I see no reason to ask for these responses off list. 

Thanks!
Susan H. 
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com