Just now, I used the import wizard, and there's an option to overwrite data on production (right now, the servers don't have the rights to each other's file systems).
How does this compare to the "backup on development/restore on production" strategy? Thanks, Jamie On Thu, 28 Feb 2002 16:32:22 -0000, in cf-talk you wrote: >Backup your dev database to a file, upload it to live server, and force >a >restore over the current db, works for me. > >-----Original Message----- >From: Jamie Jackson [mailto:[EMAIL PROTECTED]] >Sent: 28 February 2002 16:37 >To: CF-Talk >Subject: Moving MSSQL DB from Dev to Prod > > >What's the typical way to copy one's development DB to production >(SQL2000)? Changes will commonly be made on Dev, and there will be an >existing version on production which will need to be overwritten. > >I know about the "copy database" wizard, but AFAIK, it doesn't work if >the DB already exists on the production server. > >Finally, is there a resource concerning general CF/MSSQL interaction >issues and best practices? > >Thanks, >Jamie > > ______________________________________________________________________ Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation · $99/Month · Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
