That is normal behavior for a FULL JOIN.  You need to adjust the final SELECT to reflect the fact that any table's results could be NULL, like so:

            
September 19, 2020 at 5:19 pm
            
#3789655

            
            
                                                
        

You didn't provide nearly enough info to analyze your index needs.

However, keep in mind that SQL strongly favors equal (=) comparisons over other types.  So, if your conditions are "WHERE...

Uh, no, they are designed exclusively to help performance.  That is, increased...

Btw, you're wasting bytes making that column nvarchar rather than varchar, since the only values possible don't include any non-standard chars.

Much better would have been to create an SSMS server group(s) with all the relevant servers in it(them), then fire off the script for a given server group(s)...

DDL triggers are a great option.  I use them in nearly every db to prevent actions we don't want taken.  As examples, in some dbs we don't want objects created...

Much better would have been to create an SSMS server group(s) with all the relevant servers in it(them), then fire off the script for a given server group(s) whenever needed. ...

I agree.   I'd strongly urge to concentrate on the core aspects of SQL Server first, then learn about PowerShell later if you still want to.  There's enough to learn in...

For new db(s), the support team can "notify itself".  It's easy enough to check every day to see if a new db has been created, whether a user tells you...

SQL Server must pre-format log files (setting each page's non-control data to binary zeros, I think).  That will take quite a while for 95GB (apparently 3 hours on your system...

Get the best SQL administration book for whichever version of SQL you are on.  The "Inside SQL Server"/Internals books with Kalen Delaney are excellent.

For learning T-SQL, get books by Itzik...

To clarify, you can compress non-clus indexes, and should often do so, but you must compress each one separately.

Also, 80% is a very low number overall, are you sure you...

Be sure also to make sure the "cost threshold for parallelism" is not too low.  Hint: the default is too low, if you haven't changed it,  you should.

5. Avoid using reserved words as column names (PERIOD)

PERIOD is not a reserved word in SQL Server. (Nor is it reserved in ODBC, also not on the list of future...

Sorry, I had some difficulty figuring out specifically what you meant.