SQL tip #5: Be prepared for SQL 2016