Job History

  • Comments posted to this topic are about the item Job History

    -------------------------------Posting Data Etiquette - Jeff Moden [/url]Smart way to ask a question
    There are naive questions, tedious questions, ill-phrased questions, questions put after inadequate self-criticism. But every question is a cry to understand (the world). There is no such thing as a dumb question. ― Carl Sagan
    I would never join a club that would allow me as a member - Groucho Marx

  • Nice and easy - only because I've seen this as well.

    Thanks for the question.

    -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle

  • Good one, I have experienced this too.

    M&M

  • Nice and Easy Question for the Weekend.

    Thanks. 😀

  • Easy. Link

  • Great question, thanks.

    In the context of QotD, easy, but I reckon in a real life scenario it would take me a lot longer to find that answer.

  • I guessed on this one. I've not experienced this error before.

  • nice easy one to round out the week - cheers!

  • Nice question, thanks! I saw a blog post saying that it has to do with the SMO version used. Didn't say what the difference was between the one used in 2008 and 2005 though.

  • KarenM (4/20/2012)


    I guessed on this one. I've not experienced this error before.

    +1

    In my case the reason I've never experienced it is that I've never used 2005; but the wrong answers seemed just too far-fetched, so the right one was a natural guess.

    Tom

  • According to BOL 2005 the message field in sysjobhistory is nvarchar(1024) in 2008 the field was expanded to nvarchar(4000).

    Good question though.

  • We've started using a 2008 R2 server with 2005 client tools. Haven't seen this error, but a couple of similar ones.

    Can't use Open Table, instead must use Select.

    If any new datatypes have been used, then Select won't work either.

  • Never seen this. Guessed this one. +1.

  • L' Eomot Inversé (4/20/2012)


    KarenM (4/20/2012)


    I guessed on this one. I've not experienced this error before.

    +1

    In my case the reason I've never experienced it is that I've never used 2005; but the wrong answers seemed just too far-fetched, so the right one was a natural guess.

    +1, Tom

    A nice one for a Friday afternoon. Thanks!

  • Easy guess.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

Viewing 15 posts - 1 through 15 (of 22 total)

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