Sergiy (12/22/2015)

---

ScottPletcher (12/22/2015)

---

Seriously, what is the downside to leaving off the N'? I see none, whether the column is char or nchar. But I see a huge downside...

Lynn Pettis (12/22/2015)

---

ScottPletcher (12/22/2015)

---

Lynn Pettis (12/22/2015)

---

ScottPletcher (12/22/2015)

---

Lynn Pettis (12/22/2015)

---

ScottPletcher (12/22/2015)

---

Lynn Pettis (12/22/2015)

---

ScottPletcher (12/22/2015)

---

Of course when scanning the whole table the difference may be rather minor. It's the prevention of...

SELECT "Name"."ID", "Name"."LAST_NAME", "Name"."FIRST_NAME", "Name"."EMAIL", "Activity"."ACTIVITY_TYPE", "Activity"."PRODUCT_CODE", "Activity"."TRANSACTION_DATE", "Name"."BIRTH_DATE", DATEDIFF(YEAR, "Name"."BIRTH_DATE", GETDATE()) - CASE WHEN

CONVERT(char(5), GETDATE(), 101) < CONVERT(char(5), "Name"."BIRTH_DATE", 101) THEN 1 ELSE 0 END AS "AGE"

FROM "IMIS"."dbo"."Activity"...

Eirikur Eiriksson (12/22/2015)

---

ScottPletcher (12/22/2015)

---

Edit: Not at all "moving the goalposts". The only reason for the rule is the issue it causes if you get the type wrong, as I...

The really tricky part of this is deciding how you want to handle Feb 29 birthdays: in non-leap years, is that birthday Feb 28 or Mar 1? In certain...

Lynn Pettis (12/22/2015)

---

ScottPletcher (12/22/2015)

---

Lynn Pettis (12/22/2015)

---

ScottPletcher (12/22/2015)

---

Lynn Pettis (12/22/2015)

---

ScottPletcher (12/22/2015)

---

Of course when scanning the whole table the difference may be rather minor. It's the prevention of seeks that is...

Eirikur Eiriksson (12/22/2015)

---

ScottPletcher (12/22/2015)

---

Eirikur Eiriksson (12/22/2015)

---

My bad in the post before on the conversion, sorry about that.

😎

My point is that incorrect typing and implicit conversions do cause problems, I've lost...

Lynn Pettis (12/22/2015)

---

ScottPletcher (12/22/2015)

---

Lynn Pettis (12/22/2015)

---

ScottPletcher (12/22/2015)

---

Of course when scanning the whole table the difference may be rather minor. It's the prevention of seeks that is always the major...

Lynn Pettis (12/22/2015)

---

ScottPletcher (12/22/2015)

---

Of course when scanning the whole table the difference may be rather minor. It's the prevention of seeks that is always the major concern with implicit...

Eirikur Eiriksson (12/22/2015)

---

My bad in the post before on the conversion, sorry about that.

😎

My point is that incorrect typing and implicit conversions do cause problems, I've lost count of how...

To insure consistency in how the DELETE is done, you should always use an alias for the affected table when using DELETE [table_name] ... FROM ....

For example:

DELETE a

FROM tbl_a a

<join_type>...

I think the structure is good overall.

Here are some possible adjustments to consider:

TblClientPOC

1) Add a description / comments column

2) I'd get rid of the identity column here -- contrary to...

Of course when scanning the whole table the difference may be rather minor. It's the prevention of seeks that is always the major concern with implicit column conversions. ...

Eirikur Eiriksson (12/22/2015)

---

ScottPletcher (12/21/2015)

---

But if you put the N' when the column is not unicode, you'll force SQL to implicitly convert the column itself and that could be a real...

Yeah, everybody always "warns" about that, but who on earth would want to apply a 299GB log anyway??