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
Generally, it is pretty bad practice to copy production data to any other
network. You would most definitely not pass a SaaS 70 audit if they found
that you were doing it. You would also not pass the same audit if they found
that all of your developers had direct access to that data without going
I have a report built with report builder and it appears that if you set the
body to stretch with overflow that cfreport will swallow a line or two
every time it paginates see attached for a simplified version of the report, I
have removed all but the body on this (actual report has a
I have a report built with report builder and it appears that if you set the
body to stretch with overflow that cfreport will swallow a line or two
every time it paginates see attached for a simplified version of the report, I
have removed all but the body on this (actual report has a
6 matches
Mail list logo
