I'm attempting to help a small company which has a credit card applicatoin that may need periodic (or temporary) database expertise. The issue is, the corporation has almost all their IP within this database, so that they are rightfully reluctant to provide someone can get on.

They'd typically meet and gain trust personally, however the talent pool within physical closeness for them is fairly limited. I must believe that they might still in some way take advantage of the global DBA expertise though...

The crappiest DBA will have the ability to dance SQL Circles around these men - so subjecting only bits of the database does not seem achievable in my experience, however i am wishing I simply have no idea how.

Anybody have tips about the way they may find a reliable company (or individual)? After I employ a programmer, I start them on fundamental items that when they screw up will not hurt an excessive amount of. Having a database, can there be something will be able to begin with that may limit their exposure. Maybe Profiler output for analysis or something like that?

The easiest factor is needing all employees and companies who begin to see the database, or its design, to sign non-disclosure contracts. You will find lots of boilerplate ones there, along with a good attorney can offer assistance with what you'd need in a single with under an hour or so of billing time. Everybody in the market can be used for them, and everyone knows why they need to sign them.

Obviously, that isn't a programming question, it is simply a legitimate problem.

Because the others have pointed out, NDA's make the perfect idea, that covers you against the perspective of the items they see...

However, I'm able to feel that you're also worried about any potential "damage" the individual could do in order to your database when they get some things wrong. To obtain around, and safeguard out of this is a little harder, but there a couple of good key products that I would suggest.

  1. BACKUP EVERYTHING before beginning, this really is good sense, but can't be overstated
  2. Supply the consultant an evaluation atmosphere if you can to duplicate production issues. This provides a remote atmosphere where testing can be achieved.
  3. Don't limit their database access. Database issues require digging in to the system, restricting their access, could really lead for an error instead of stopping them.
  4. Search for references, or proof of the individuals capabilities.

Provided these details like a consultant myself. I actually do .Internet and SQL Server talking to, and that i make sure that the suggestions above are true during my talking to cases, and that i haven't were built with a fault. Steven highlights the greatest type in all of this which is all an advisor has is his status. Serious consultants completely understand this, and due to it'll make certain that they don't put themselves into tricky situations.

consultants sign NDAs constantly, and also the high quality ones drive them seriously just because a consultant's status is all he's

whilst not a DBA, i'm able to recommend this fellow when i have known him my existence -)