I just looked at http://qa.sqlservercentral.com/TotalScores and it shows that the 30,000+ are SSChampion, hence my (incorrect) answer 🙁

To me, the explanation isn't quite right. I believe the right explanation should be something along this line:

Statement 1 : The SQL Database Engine converted the Val value to character...

Hah, didn't really read the sp_addmessage BOL, selected that one thinking it would have been added and someone ran a RAISERROR. I never knew you can actuall type on the...

Good question. never used an endpoint before, so I Googled it and the first thing that comes up is the conflicting BOL http://msdn.microsoft.com/en-us/library/ms162560.aspx :angry:

I picked the right answer but for a totally different reason.

I can easily run the script without error by highlighting/blocking the first batch excluding the NotGo word, same with the...

Thanks for your reply. We have 4 domains but that's small enough to manage. I will use the Domain Users then. Thanks again for your help.

The answer and the explanation contradicts each other (for the 2nd option, answer says C but explanation says D). I chose A & D, which are supposed to be the...

I guessed, and was correct, but the reference points to SQL 2000 BOL. I can't find this in current SQL 2008 BOL, but maybe I just haven't looked hard enough.

Thanks for this Craig. Whilst useful, I don't think I can use it because there will be case where the file will not exist, and hence, rather than throwing an...

Hey, that's a good idea, why didn't I think of it :hehe:

Thanks for that, will try that for sure.

Thanks Elliott for your reply. I have already set the DelayValidation to True, yet it still won't let me pass that Excel file connection complaining about non-existing file.

Re: the squiggly red underline after the GO command

Good to know they've got it fixed in the updates, minor things but still a good fix 😀

I got it right, but I just wonder, if GO is meant to take an optional [count], why does it has the red squiggly underline mark when writing it in...

Thanks for the question. interesting to know the null is treated differently in the function.

In regards to answer A and B being the same, I think it's because of copy...

I agree, the collation setting (whether it's case sensitive or not) would bring different results (1 for case-sensitive and 4 for case-insensitive).