Jim Dettman
jimdettman at verizon.net
Fri Feb 1 12:09:28 CST 2008
Rocky, There are a few methods depending on your needs: 1. Detach, do a simple file copy and reattach. 2. Use SQL backup/recover. 3. Copy Database Wizard 4. SQL Scripts. The typical way is the first, although it won't copy jobs you have defined in SQL and User Defined Error messages. It does require exclusive use of the database though. Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at Beach Access Software Sent: Friday, February 01, 2008 12:43 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] SQL vs Access Gustav: How do I transfer the SQL db from here to there? Rocky -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock Sent: Friday, February 01, 2008 8:59 AM To: accessd at databaseadvisors.com Subject: Re: [AccessD] SQL vs Access Hi Rocky As he has several running servers and a proven backup scheme, he has a valid point. /gustav >>> rockysmolin at bchacc.com 01-02-2008 17:49:53 >>> Dear List: I am looking at doing a job which is ideal for an Access back end (IMO) but IT would prefer a SQL back end for the reasons below. I expressed the opinion that SQL would be overkill. But they are concerned about stability and backup. How do I respond to this? Does he have a valid point? The database will have a relatively small amount of data and 4 initially and eventually up to 10 users. Light entry and update. ********************************************************** I think his response about it being overkill is from the perspective that it is a small application which normally wouldn't warrant a MS SQL license and overhead. Because we already have several servers, we would not require any additional licenses. The real reason we would like the MS SQL backend is for stability and backup purposes. We cannot backup an Access database the same way we can MS SQL because it is simply a flat file and can sometimes not properly backup if the file is currently in use (which will be the majority of the time). Additionally, in the past we have had problems with corrupt MS Access databases when multiple people are accessing it simultaneously. I think it would be valuable to have him quote the project if it were done only in MS Access and the side-by-side comparison of the same project with the MS SQL backend. Please let me know if you need further assistance in talking to Rocky about this. ****************************************** MTIA Rocky' -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.18/1254 - Release Date: 1/31/2008 8:30 PM -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com