• 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.

Previously on "Have you heard the one about the developer who"

Collapse

  • MrMarkyMark
    replied
    Originally posted by suityou01 View Post
    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.

    Leave a comment:


  • MarillionFan
    replied
    Originally posted by MarillionFan View Post
    Yes, he's completed two in his time


    Project Balls Up


    and


    Project F**K Up




    Oh Suity.

    Leave a comment:


  • LondonManc
    replied
    I didn't know 123-reg were based in notloB

    Leave a comment:


  • _V_
    replied
    Originally posted by vetran View Post
    you know the others are idiots but you have to give them some access.
    No chance. Power off the DB server and lock it in a safe. Never had any DB issues that way.

    Leave a comment:


  • suityou01
    replied
    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.

    Leave a comment:


  • vetran
    replied
    Originally posted by _V_ View Post
    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.

    Leave a comment:


  • MarillionFan
    replied
    Originally posted by Churchill View Post
    Ever hear about a project that SY01 completed successfully?

    Nope?

    Me neither.


    Yes, he's completed two in his time


    Project Balls Up


    and


    Project F**K Up

    Leave a comment:


  • _V_
    replied
    Originally posted by MrMarkyMark View Post
    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:


  • MrMarkyMark
    replied
    These are "hobbyists" you are working with, right?

    Leave a comment:


  • Moose423956
    replied
    You should be happy that us developers create work for you and keep you in [disguised] employment

    Leave a comment:


  • NotAllThere
    replied
    Originally posted by Churchill View Post
    Ever hear about a project that SY01 completed successfully?

    Nope?

    Me neither.
    FTFY

    Leave a comment:


  • vetran
    replied
    hey we had the platform team change how tasks were scheduled (using local service user) not a dedicated user during go live.

    p1ssed away a good part of my weekend .
    Last edited by vetran; 19 April 2016, 12:13.

    Leave a comment:


  • SimonMac
    replied
    Could be worse, could have been in prod

    Leave a comment:


  • suityou01
    replied
    But it's not my fault

    Leave a comment:


  • Churchill
    replied
    Originally posted by suityou01 View Post
    Randomly renamed database columns in a migration staging area a week before dress rehearsal, and there were no backups?

    It's a cracker. I asked for him to back out his changes, but I have once again been ignored.

    SSIS packages are a rash of red this morning.
    Ever hear about a project that SY01 completed successfully?

    Nope?

    Me neither.

    Leave a comment:

Working...
X