April 19, 2012 at 10:16 pm
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
April 19, 2012 at 10:18 pm
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
April 19, 2012 at 10:45 pm
Good one, I have experienced this too.
M&M
April 20, 2012 at 12:40 am
Nice and Easy Question for the Weekend.
Thanks. 😀
April 20, 2012 at 1:19 am
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.
April 20, 2012 at 7:22 am
I guessed on this one. I've not experienced this error before.
April 20, 2012 at 9:00 am
nice easy one to round out the week - cheers!
April 20, 2012 at 9:51 am
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.
April 20, 2012 at 10:43 am
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
April 20, 2012 at 12:01 pm
According to BOL 2005 the message field in sysjobhistory is nvarchar(1024) in 2008 the field was expanded to nvarchar(4000).
Good question though.
April 20, 2012 at 12:28 pm
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.
April 20, 2012 at 1:30 pm
Never seen this. Guessed this one. +1.
April 20, 2012 at 3:42 pm
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!
April 22, 2012 at 11:18 pm
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 21 total)
You must be logged in to reply to this topic. Login to reply