You don't seem to remember that the table must have a key by definition. It s not an option! Since every column in your DDL is NULL-able, nothing here can...

>> Since I don’t know your first name do you mind if I call you J? <<

Actually, I go by "Celko" and have for the 30 something years I've been...

Actually the problem is that SQL Server does not have an interval temporal data type. This is part of the full ANSI/ISO standard SQL. Intervals are considered scalars. I would...

A useful idiom is a report period calendar. It gives a name to a range of dates. The worst way would be to use temporal math; it tells the world...

>> I'm looking for a smart idea on how to populate a field [sic: colums are not fields]]]] Priority with values H/M/L based on Column 1 (Activity type) and criticality...

The CASE expression has two forms. We stole the syntax from the Ada programming language. You are trying to use the form looks like a switch construct in other programming...

If the poster is using the old Sybase MONEY data types, be sure to tell him to look up the rounding errors in multiplication and division that make this illegal...

Our first problem is that you have no idea what a table is. There must be a key which means that all NULL-able columns. Next, identifiers cannot be numeric because...

No. SQL is based on a tiered architecture, like all modern programming. We do not format data for display in the database tier. Essentially you're trying to write some weird...

>> I have a Date calendar table which has a range of dates between 01/01/2000 to 31/12/2050. <<

Unfortunately, you never read a book on SQL. The only display format allowed...

> my problem is that some positions have the max salary listed as hourly rate and some are annual amount. Therefore,  I need to multiply the hourly rate by 2080...

https://www.red-gate.com/simple-talk/sql/t-sql-programming/state-transition-constraints/

Brent's point is that temporal data should be kept in a temporal data type, numeric data in numeric data types, etc. And not those insane kludges we see where someone...

You can do this easily with string functions, but it’s still a stinking kludge caused by bad design. Most of the work in SQL is done in the DDL, and...

I voted for this convention when we added the CHECK() to the SQL Standards on the same grounds; "benefit of the doubt" principle 🙂