Rachel Byford (4/22/2009)

---

My belief was that as a consequence of the union removing duplicates, the output always came out ordered. Possibly not if you end up with several worker...

Agreed. Since there is no ORDER BY, both answer options #1 and #2 are correct. I chose...

I agree with the previous comments.

I think everyone of us has made the error of looking something up in BOL but missing the "MDX" or (more common for me) "SQL...

Are you sure? I just replied to the question,...

I have to disagree with half of the answer key.

First: The third statement ("when data in a FILESTREAM column is updated, the data in the filestream file is updated") is...

Chirag (3/20/2009)

---

In BOL under Creating Indexes (Database Engine) section its mentioned that there can be 249 non clustered indexes per table.

But In BOL under Create table sections...

Others have already pointed out the missing GROUP BY clause, so I'll skip that and limit myself to commenting the non-portable date format used. On many non-US systems, the date...

Balachandra (3/16/2009)

---

Hi All

I am not sure wichi is correct answer. Beacuse the same question is repeted twice.

1st time i entered as 0 and answer was wrong.

2nd time i entered as...

I don't have a test setup here to quickly double-check, but if I read the documentation correctly the NOT FOR REPLICATION will not cause the constraint to exist only at...

skjoldtc (2/18/2009)

---

Thanks Hugo for the explanation. I learn so much from this forum. It does seem to be a pretty odd way to handle time. Does this change in...

knechod (2/17/2009)

---

More of an avoidance than a hard-and-fast rule. As an ordering method, not a problem. As...

Steve Jones - Editor (2/17/2009)

---

OK, my head hurts.

I've awarded back points since there is obviously some issue here. I missed the correct answer with 1/30, so I've fixed that.

As far...

knechod (2/17/2009)

---

My guess is that if you truncated the date, you would not exercise any index on [InsertedOn]. However, IMHBIO (in my humble but inexperienced opinion), I would question...

skjoldtc (2/17/2009)

---

Points schmointz... who cares?

The takeaway is that SQL Server rounds time and don't use BETWEEN with a date range. But, this seems such a strange way to do this....

Lempster (2/17/2009)

---

Hi Hugo,

I don't get a conversion error, I simply get all of my results showing as '2009-01-31' plus whatever the hours, minutes and seconds are, so far from needing...