• P (unregistered)

    @echo Database Backup in progress, Step frist / 69...

  • (nodebb)

    I could've submitted a hundred of these WTFs from a product I worked on a few years ago. SSIS packages with SQL and script tasks as far as the eye can see. I almost wish they never had the script task.

  • Aspie Architect (unregistered)

    OSQL? That's been dead and buried for a few years. SQL Server has built in maintenance plans. Why the lever with a million moving parts approach? You can run the backup direct from SQL Server Agent so why SSIS?

  • Black Mantha (unregistered) in reply to Aspie Architect

    As a wild guess, it was made with the specification that everything had to run through their system, so they could sell it as a system that handles everything.

  • Brad (unregistered)

    I worked a ton with SSIS awhile back. I was constantly repressing the urge to go somewhere and make someone pay. Riddled with cryptic error messages, super finicky, etc. Now there are dozens of flashy cloud-based replacements for it. All of which are VERY expensive. I'll bet they're filled with pain too. At least SSIS is (essentially) free.

  • DQ (unregistered) in reply to Aspie Architect

    Isn't that the question we always ask ourselves if we read an article on TDWTF: Why ?

  • James (unregistered) in reply to Brad

    That's nothing I used to work in place that had a lot of DTS packages (predecessor to SSIS). Those also offered a VBScript task.. It was possible someone discovered to get hold of the DTS COM object and change the current job step back to previous one. Of course DTS supported branches already this effective added loops..

    Now that DTS was made touring complete; you guessed they started designing not just ETL processes with it but basically ALL data batch processes in it. All kinds of complex business rules around order filling etc all done in giant flow-charty brilliance dotted with little VBS icons captioned with "loop"

  • SomeGuy (unregistered)

    I didn't know a SQL system could have store procuders... but I guess these systems do.

  • MiserableOldGit (unregistered)

    Looks like the result of migration from some other system, or an earlier system (osql might hint at that), where the PHB insisted they should use SSIS even though everyone knew it was wrong. So it just does a couple of noddy things and hands back to the place where it should be doing the work.

    osql was supposed to be replaced by sqlcmd, but I wouldn't be surprised if sqlcmd simple encapsulates and extends, and all the modern interactive whizzy tools are then just wrappers around sqlcmd.

  • LaughingItOff (unregistered)

    I still do a lot of stuff in SSIS. It is not that bad and being able to run C# or VB scripts is a good thing... sometimes.

    In this case, all could have been done in one script. The batch file was not necessary.

  • sizer99 (google) in reply to Brad

    This is typical for Microsoft. They've also got PowerBI, which is a 'free' replacement for the very expensive Tableaux. Except it's much crappier. So many headaches as you try to let someone make graphs with all the options of R or Matlab but without programming. So many widgets, so many hidden configuration settings, so much pain. But it's 'free!' Though of course they're constantly trying to get you to upgrade to the more expensive version. But then you'd be paying for something crappy.

  • M$ GUY (unregistered) in reply to sizer99

    PowerBI is not free, you dum dum.

  • WTFGuy (unregistered) in reply to Aspie Architect

    @Aspie Architect: The answer is probably pretty simple. This big enterprisy product sold around the world was not designed last year. It was designed in 1998. In 1998 that WAS the least bad way to accomplish the job. The fact that a fresh design begun in 2019 would use other better tools is immaterial.

    When new versions of whatever stack(s) you use in your product comes out you (I hope) don't redevelop your entire product stack to use only the latest and greatest features. Neither did Initech.

  • Ulysses (unregistered)

    TRWTF is that Remy chose 'they' for Kristoph.

  • medievalist (unregistered)

    That first paragraph is a golden truth bomb.

  • Vincent Vancalbergh (google)

    With all the WTFery that goes in an SSIS package and how hard it is to decode the (error) logs I am (piecemeal) moving them to PS scripts which are immensely more readable. Only downside is I have to put in a little bit more work in manually managing credentials and logging.

Leave a comment on “The Enterprise Backup Batch”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article