• Peter (unregistered) in reply to ObiWayneKenobi
    ObiWayneKenobi:
    The Real WTF here is that there was code that broke during an upgrade of SQL 2000 to SQL 2005! Seriously, that's not a major upgrade at all; I've upgraded a lot of servers like that and seen plenty more, and they all went smooth as hell. I agree this manager was an idiot to upgrade it out of schedule, but nothing should have even remotely broken due to it!
    I was involved in an upgrade from version 6.5 to 7.0. The folks who did it to our production environment didn't think there would be an impact, so none was checked. It turned out that a number of stored procedures failed/broke during the migration, without any warning that they were broken. 6.5 allows " and ' for string termination, 7.0 only allows '. The standard is '. As a result, several dozen stored procedures and triggers had been broken for 6-9 months before being identified. This was a pharmaceutical application that created formularies. The guy who was in charge of this was also someone who didn't check in code, and when his HD failed, it turned out that the VSS database was corrupted too, so the latest available copy of the code he worked on daily was almost a year old.

    At my current place, we have a far simpler system and even this broke going from SQL 2000 to SQL 2005. Every stored proc had to be reevaluated, and some required reworking, as the underlying table had changed and the procs wouldn't even compile anymore.

  • SwordfishBob (unregistered) in reply to waefafw
    waefafw:
    Old style outer joins are deprecated in SQL Server 2005 (the old, ambiguious *=, =* syntax). That's the biggest change.

    And by deprecated, I mean that a query containing old style joins throws an error.

    Then you don't mean deprecated, you mean removed. Deprecated is usually used to mean "It's still there, but only for backward compatibility. Stop using it. Remove your reliance on it before we bring out a future version where this feature will be removed."
  • (cs) in reply to Tailors Suit Ya

    If you would work in Europe, you would have a practically unlimited number of sick days - I've heard somebody who worked for the (Austrian) Government and was away THREE YEARS because his doctor testified that he was "allergic to the ringing of phones". He was "pragmatisiert", meaning he couldn't be fired until he did something REALLY wrong (like, killing a few people).

  • Anon (unregistered) in reply to
    :
    Anonymouse:
    That should (and usually will) happen to anyone in any enterprise who goes on vacation for a month at a time. If they can do without you for a month, they can do without you forever, even if you didn't bork anything up before you left.

    In many countries, 5 week of vacation a year is the norm. The real WTF is that people in the US are convinced that 2 weeks is "normal".

    If you are so essential that they can't do without you for 4 weeks, then your boss should be fired. Any company should be prepared for any one employee to get hit by a bus without collapsing.

  • RevMike (unregistered) in reply to Anon
    Anon:
    Any company should be prepared for any one employee to get hit by a bus without collapsing.

    That is one tough employee if he can be hit by a bus without collapsing!

  • Binsky (unregistered)

    But seriously, noone finds it strange that the manager came in on christmas weekend, and again during new years? :S

    When did that start being normal?

  • sol (unregistered) in reply to Binsky
    Binsky:
    But seriously, noone finds it strange that the manager came in on christmas weekend, and again during new years? :S

    When did that start being normal?

    In america that just means he is has a wife....

  • S (unregistered)

    Offtopicing the holidays, since it's so interesting for all.

    In Finland the first year gives the employee 2 days of vacation per month. Next years it's 2.5 days per month. So 30 days of vacation per year after the first year.

    But, there's a catch. We normally work only Mo-Fri but when calculating vacations, Saturdays are taken into account. So if you take a two week vacation it's 12 days off your vacation quota, not 10.

    And if you take a new job at, say, April, your next vacation can be next April since vacation days are calculated from the start of April to the next April and after that you can use them. Naturally most companies allow some summer/winter vacation though you haven't really earned it yet but that's off your next summer's vacation.

    Now, wasn't that interesting?

    On topic, I'm also surprised that some people don't downgrade PHP when problems are found and instead let errors occur. And as someone said, if SQL Servers are important, why isn't there any backups from which to get the system back to the original state when the problems arise?

    Of course, it could be that the backups were going to be run later before the real upgrade, but that doesn't seem logical if the data is important. It's backed up constantly then.

  • ck (unregistered)

    Upgrading one of our applications took three months because it uses DTS. Rewriting all those wasn't particularly simple.

Leave a comment on “Practice Makes Perfect”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article