ALWAYS is a bit strong.
We will have to agree to disagree. I'm sticking with my statement.
SQL devs should know this stuff.
But they don't. Or they are in a hurry, or their coffee spilled and distracted them, etc. Build a box around them (and yourself) with a VERY simple construct (that can be auto-created with SQL Prompt et al).
If you know that the people who are going to be maintaining the code are not that proficient, then maybe.
You may have 100% rock-star TSQL types at your company right now. What about starting next week, or 6 months or 3 years from now??
the problems you mention should be sieved out during testing.
Sorry, but that one is actually laughable!! If I had a nickel for every client I have ever had in about 20 years of database consulting that actually did GOOD (if any, usually) database testing I would have ... $0.00. :blink:
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service