Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Logging in...
Previously on "Have you heard the one about the developer who"
This staging environment was originally created on the same LAN segment as Prod with no firewalls.
The QA user account the engine uses had Admin writes to the production DB.
Their production systems got mangled when we turned it on.
A good DBA would have ensured that no changes can be made to databases, that no data can be put into databases and no data can be read from databases. Databases need to be locked away for everyone's best interests. Letting people near databases leads to sadness.
you know the others are idiots but you have to give them some access.
These are "hobbyists" you are working with, right?
A good DBA would have ensured that no changes can be made to databases, that no data can be put into databases and no data can be read from databases. Databases need to be locked away for everyone's best interests. Letting people near databases leads to sadness.
Leave a comment: