You should / could have mentioned that an index persists the column (but only in the index itself) too.

Persisting on the table level safes you a little...

I did not make many tests for edge cases and wrote this only a short proof of concept, but this piece of code would return the same and would be...

Since we have to do diffent tasks (or little steps toward this tasks) every day, a good day would be the wrong measurement. When I have a big tasks that...

Here a version, which uses selfreferencing CTEs:

CREATE TABLE dbo.synonym (synonym VARCHAR(50) NULL, word VARCHAR(50) NULL, sort_order INT PRIMARY KEY);
INSERT INTO dbo.synonym (synonym, word, sort_order)
VALUES...

In my opinion this is a very bad script.
- Scalar functions (as those) are very slow
- creating a table variable (since you can't use #temp-tables inside a function)...

The whole, valid command would be (plus maybe some with-options)
RESTORE VERIFYONLY FROM DISK='\\SERVER1\Backup\my_big_db\FULL\SERVER1_my_big_db_FULL_20180803_210600.bak'

Sorry, but checking the disk space does not make any sense, since I do...

Question: why does Windows want / need more free space for itself on systems with more RAM than on systems with lesser?

The "core" of Windows should need...

I see, what you mean - when developer A works on a procedure for 4 days and developer B makes a small change (e.g. a new column or fixing a...

An important point, when working with own migration scripts, is defensive scripting. Do not just create a table, but check, if the table already exists before. The same with columns...

I used to comment every line of code, when I wrote scripts for the game Heroes of Migth and Magic 3 (WoG), but mostly, because it had a very "uncommon"...

it depends :-), but both queries could return different results when are used with real tables.

Your  first query (with UNION ALL) could return duplicates, when you have the...

Nice question, but when you use country specific date / time conversion, you should always add a SET language = 'englisch' to the query.

On my German SQL Server...

You are right about the missing OVER() in the third query - sorry, my fault,

On the other side the execution plans for query one and two are not...

This is a little inconsistency, since you can't set CONTEXT_INFO to NULL.
DECLARE @ci VARBINARY(128) = CONTEXT_INFO();
--<do some stuff as temporary setting CONTEXT_INFO to something else>
SET...