SQL 2012 doesn't have any limits on that, but your hardware certainly will. CPUs, RAM, I/O busses, etc., can only push so many bytes per second.

Most likely, I/O will...

Why not just have those three columns be unique? A unique constraint can contain multiple columns.

I don't get this part:

COALESCE('target.[Programability_TYP] <> source.[Programability_TYP] collate SQL_Latin1_General_CP1_CI_AS', '')

Why use a coalesce check on a string literal? There's no possible way for 'target.[Programability_TYP] <> source.[Programability_TYP] collate SQL_Latin1_General_CP1_CI_AS' to...

Definitely could be an issue with in-flight data conversions of one sort or another.

You'll probably need to get a more experienced .NET dev to review your code.

ScottPletcher (1/8/2013)

---

GSquared (1/7/2013)

---

paul.j.kemna (1/7/2013)

---

Wow, that makes a lot of sense. Such a simple concept that i may have overlooked in some places.

But in this case, we are assuming that...

That's always from either an out-of-range date or a malformed date.

Usually see it where American-style dates (MM-DD-YYYY) are being inserted into something expecting Euro-style dates (DD-MM-YYYY), or vice-versa....

GilaMonster (1/8/2013)

---

GSquared (1/8/2013)

---

I believe SQL Server will sometimes shortcut a "Where (select count(*) blah blah blah) > 1" into an Exists() check. But don't count on the optimizer being...

I've seen Count() kill a server where Exists() was fine.

A code-push was done on a Tuesday night. Everything went fine. Monday morning, however, the websites wouldn't come up,...

I guess I'm not clear on what end result you are trying to achieve here. Can you clarify that?

ScottPletcher (1/7/2013)

---

GSquared (1/7/2013)

---

ScottPletcher (1/7/2013)

---

GSquared (1/7/2013)

---

Assuming "correct results" means dates between the two variable values, including the end-date value, then yes.

As mentioned, using <= @EndDate can give odd results.

For example:

DECLARE @T...

Whichever part your script...

CELKO (1/7/2013)

---

I would build a calendar table with a ISO-8601 week-within-year format column in addition to the usual Common Era date. This format is 'yyyyWww-d' where yyyy is the year,...

Not really. You might be able to work around it using script objects, but you're probably better off building a .NET service that reads the file directly.

ScottPletcher (1/7/2013)

---

GSquared (1/7/2013)

---

Assuming "correct results" means dates between the two variable values, including the end-date value, then yes.

As mentioned, using <= @EndDate can give odd results.

For example:

DECLARE @T TABLE

...

paul.j.kemna (1/7/2013)

---

Wow, that makes a lot of sense. Such a simple concept that i may have overlooked in some places.

But in this case, we are assuming that I DO...