Hello,
I'm setting up a new environment and I would like to have the ability,
through a web UI to copy objects from our production database (separate
server) to a development/debugging database (separate server). My question
is not about how to implement this but rather whether this is bad
Putting production data source connections on the development server
is a practice you should avoid. I cringe whenever I see developers do
this.
Having the development DSN on the production server is less risky.
Another path would be having the two databases linked at the database
level and use
just take a copy of the live database and remove all sensitive data from it.
either remove all data and replace with demo data, or just run a query that
replaces the sensitive data with something else.
On Sat, Jan 28, 2012 at 10:15 PM, Mike Chabot mcha...@gmail.com wrote:
Putting production
-Original Message-
From: Brook Davies [mailto:cft...@logiforms.com]
Sent: Saturday, January 28, 2012 4:02 PM
To: cf-talk
Subject: Best Practice question about database access between Dev and
Production Servers
Hello,
I'm setting up a new environment and I would like to have the ability
4 matches
Mail list logo