Take care not to forget that this is...

<PEDANTRY>It's 5 extra characters, not 4. Typing WITHFORCESCAN will get...

CDOSYS

Hugo Kornelis (5/2/2013)

---

Rune Bivrin (5/2/2013)

---

Hugo Kornelis (5/2/2013)

---

However, to do some nitpicking:

1. If I were to try this code on my system, I would get five errors. All system table (*)...

Hugo Kornelis (5/2/2013)

---

(And I think every development server SHOULD be set up with case sensitive collation - developing there and deploying to a case insensitive server is okay, the...

GilaMonster (5/1/2013)

---

CREATE TABLE TelephoneDigits (

DigitID INT IDENTITY PRIMARY KEY,

Digit CHAR(1) NOT NULL UNIQUE -- todo. Check constraint to limit to 0..9, (, ) and +

);

CREATE TABLE TelephoneNumberDigits (

...

jasona.work (5/1/2013)

---

I just started reading through the topic, it almost sounds like two things to me:

1. A moving target. Every time a reasonable answer is proposed, "that won't...

Using what MS calls schemas to separate different parts of the data is fine, but I don't think a hierarhic relation between schemas would make sense: SQLServer is a (nearly)...

ChrisM@Work suggested that I should revisit the complex many-to-many relationship thread, so I've done so. I found it quite difficult to avoid calling the OP an idiot, since several people...

Ganga-236835 (4/26/2013)

---

It is not necessary to query per device type, as only the parent ID and parent type can be supplied to return X amount of records of varying phone...

ChrisM@Work (4/26/2013)

---

Show me a person table which doesn’t have columns firstname, middlenames, lastname. However, not every person has or is willing to reveal their middle name(s). Some are unwilling to...

Evil Kraig F (4/29/2013)

---

At the same time, I rarely take this approach for app devs to access my data because of all the intrinsic concerns that views bring into play,...

Sergiy (4/30/2013)

---

Actually, this syntax is one of the worst and most dangerous things introduced by MS in SQL2008.

I saw extremely powerful servers brought down by improper use of this syntax.

Not...

Hugo Kornelis (5/1/2013)

---

I think Ron expected the ANSI_WARNINGS setting to cause errors. Either because of the implicit conversion of 12.5 to integer, or because of the string truncation.[/QUOTE]

As the explanation...

See earlier post...