I was considering the value of null. Apparently, I mistakenly thought (null = 0) would return false (not unknown) and then the not operator would change it to True...

I too lucked out. I didn't like the question as posed. Having individual orders with odd quantities and pricing, was placed it out of the scope of a...

arun55 (10/8/2009)

---

vliet (10/8/2009)

---

Since the 'or' operator has lower precedence as the 'and' operator, when you ommit the parentheses the join condition means something completely different. Without parentheses the predicate behind...

Carl,

Thanks, I mentioned in the original "I am planning on having this be a domain account with access to the target destination"

I think this addressed your comment. As...

Somebody has their dates wrong, and if my wife has anything to say it would be me.

With that in mind the folks over at http://www.searchforancestors.com/utility/gregorian.html say that Greece adopted the...

SanDroid (11/5/2010)

---

Toreador (11/5/2010)

---

Don't worry about it, I've lived in England for all...

While I fall under US jurisdiction. I try to keep an international awareness. I prefer the ymd format for very selfish and pragmatic reasons outside of SQL, file...

Hugo Kornelis (11/5/2010)

---

Steve Eckhart (11/5/2010)

---

I also didn't want to just run the code to get the question, so I converted July 1, 2010 and January 1, 2010 to integers in...

Based on Hugo's LOGICAL progression where the group by preceeds the select. The alias is not yet defined so grouping is not possible against a column that does not...

Michael Valentine Jones (11/2/2010)

---

timothy bates (11/2/2010)

---

Accurate question. I think any question that uses a date with obvious notation to remove all ambiguity such as '2010-Jan-01' is fine. We...

Accurate question. I think any question that uses a date with obvious notation to remove all ambiguity such as '2010-Jan-01' is fine. We clearly understand which is the...

Nice QOTD.

I got it right but for different reasons. If you wanted to add an additional wrinkle try:

SELECT @Var2 = ' - ', @Var3 = CONVERT(DATETIME, '01/01/2010', 101),@Var1 =...

Nice question, I appreciate the intent of the question as I see it, 'Persisted does not mean permanent.'

Thanks for the comments.

In a view SQL Server returned n.n where in query analyzer it returned n.n0 for each.

My main point was to showcase that there is disparity in programs...

Use of the below could be argued as an acceptable solution.

if (@SearchMe is not null and @FindMe is not null and @ReplaceMe is not null) Select #1NormalReplace =...