jm.hwsn
jm.hwsn at gmail.com
Thu Jul 28 14:06:00 CDT 2011
All the ideas presented so far are great... some I never considered. I would be concerned about cost. As Rusty stated below, do they have a server is a major consideration. The cost of a server, the cost of the software and possibly the cost of an SQL Server Administrator if they don't have one on staff. - How many users are currently using the system and how many will use it once converted? - What is the time-line for conversion? 2-months, 6 months or longer - Do the PCs currently being used need to be upgraded/replaced once the conversion is completed? If the conversion is six months away, is the current plan to replace the user machines adequate? - If the major consideration is performance, then upgrading to Express is a viable option if all things are static. Express has a 4GB data limit so that might also be a consideration. Jim H. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rusty Hammond Sent: Thursday, July 28, 2011 1:53 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Article on upgrading Just off the top of my head: - Do they have network stability issues (ie computers losing connections, slow internet connection speeds, etc...) If so, if they think they need to go to SQL because the database is slow or the backend keeps getting corrupt, it may be they need to invest in the network and moving to SQL won't be required. - What kind of machine is the backend hosted on currently? Maybe an upgrade to that machine, or putting the backend on a more robust machine will take care of any issues. - Are they running a frontend/backend setup currently? Splitting up the database to a frontend and backend and putting copies of the frontend on each user computer may alleviate issues they may currently be having. - Is user level security becoming a requirement? Access security is easy to break and, if I remember correctly, non-existent in Access 2007 and 2010 - Using multiple versions of Access on your network to run your frontend? I've seen issues pop-up when different versions are hitting a backend and causing slowness and corruption in the backend. Moving to a SQL backend took care of the issues. - If they move to SQL, do they have a server? If not, a robust pc on a peer-to-peer network (Express only)? If not, are they willing to invest in one? - Are they hesitant to move to SQL because of cost? SQL Express is free. - Are they anticipating a lot of growth? Might be wise to make the move to SQL now so they aren't having to scramble to upgrade later. Rusty -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins Sent: Thursday, July 28, 2011 11:55 AM 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 ********************************************************************** WARNING: All e-mail sent to and from this address will be received, scanned or otherwise recorded by the CPI Qualified Plan Consultants, Inc. corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. ********************************************************************** -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com