That seems about right.  I'd say also consider doing tables every day that get a manual update in 2 days' time; they're close enough to once-a-day anyway to me.  "Better...

SELECT ca.name, ca.nentry
FROM (
    SELECT
        SUM(CASE WHEN '.' + contents + '.' LIKE '%[^A-Za-z]bull[^A-Za-z]%' THEN 1 ELSE...

The Windowing functions tend to be extraordinarily efficient, so I'd do the request this way:

SELECT DISTINCT f.[Id] AS [FormId], ver.[FormVersion]
FROM @forms f
LEFT OUTER JOIN (
  ...

In a CASE <condition> THEN <result>, the <result> must be a single value (technically called a "scalar" value).  Not allowed are SQL keywords or operators (>=, <) as part of...

"Tell" SQL to always use a full table scan for those indexes that need it.  Do that by running this one time at your convenience:

-- index_name is optional, of course

UPDATE...

If necessary, you could even add a DDL trigger as a failsafe to make absolutely sure that user doesn't create (or drop) any tables in that db.

Grant the user the db_datareader and db_datawriter roles, etc., using the commands below.  You can ignore any errors except those dealing with the user's name:

ALTER ROLE db_datareader ADD MEMBER [your_user_name_here];

ALTER...

1. No.  You simply cannot restore a backup created in a later version of SQL to an earlier version.  You'd have to use some other method of moving the db...

Exactly.  I used a CASE in a SUM but not instead of a PIVOT, so...

You're likely wasting resources by using a CROSS JOIN.  Just do a standard INNER JOIN using the LIKE comparison as the join condition.

I can't tell specifically what you want.  Here's by best guess without further details from you:

;WITH cte_state_max_sales AS (
    SELECT StateCode, MAX(Sales) AS Sales...

SQL Server does not automatically determine a row sequence, so you'll need a column in Table B that provides an order, such as an date_inserted or a $IDENTITY column.  For...

If there's still interest for this, I'd be happy to write an article about Sequences, with: set up; uses, including shared uses across many tables; possible issues; etc..

You may not be rebuilding that specific index.

The easiest way to rebuild all indexes on a table is:

ALTER INDEX ALL ON dbo.POHeader REBUILD

The linked article states that "If a date is neither a holiday, nor a weekend day, it is a workday."  But that's not true.  Businesses may be shut because of:...