Byte Me: Compilation Vacation

  • Eric M Russell - Thursday, February 23, 2017 11:30 AM

    What's annoying are fire-and-forget monster queries, where the user disconnects their laptop and goes home for the day, leaving the orphan process running overnight with no one on the other end of the call to see the result. Too bad we can't KILL {user} in addition to KILL {spid}.  :ermm:

    Alas, I must admit to submitting jobs and getting the results back in an enormous printout a few hours later.  I'm so glad I don't work in that environment any more.

    Eric, I think they have that command - it's called DROP LOGIN now. 😉

  • Mark Dalley - Wednesday, February 22, 2017 2:30 AM

    BrainDonor - Wednesday, February 22, 2017 2:06 AM

    Hands up - who else is old enough to recall writing your code out by hand, posting it to a department in another part of the country, to be typed into the mainframe and then getting a huge printout of syntax errors several days later?

    Ah yes...the days of steam. Stuff was slower, no doubt about that. More tranquil too. A bit different than today's technology-fuelled headlong rush.
    Or maybe it's just that distance lends enchantment to the view.

    MarkD

    More probable that it is the distance to enchantment. 😀

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

Viewing 2 posts - 16 through 16 (of 16 total)

You must be logged in to reply to this topic. Login to reply