How is giving read-only access any different from giving the guy a copy?
With read-only access, he'll still be able to reverse engineer the database
structure. Only now, he also has (limited) access to your system.
When giving him a copy, you can always export just the database structure
without including any of the data.
--
Mosh Teitelbaum
evoch, LLC
Tel: (301) 942-5378
Fax: (301) 933-3651
Email: [EMAIL PROTECTED]
WWW: http://www.evoch.com/
-----Original Message-----
From: Phill B [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 30, 2004 11:18 AM
To: CF-Talk
Subject: OT: allow access to database
I have a developer that needs access to a database. They suggested I
give them a backup of it that they can work with. My first thought was
OK but then I started thinking about it. I don't like the thought of
some one having a complete copy of my database.
Here's my question. Wouldn't it be better to just create a user
account that has read only access to the tables that they will be
working with? The app they are writing only needs read access and I
can kill the account when they are done. To me, it seems more secure
doing it this way.
Thoughts?
Phillip B.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
