I'd stick with something more SQL-ish, and also more readily readable and understandable, like below.  If you're converting Access to SQL Server, it's convenient to use IIF, otherwise avoid it. ...

I'd make it less cluttered by using a variable for the literal single quote:

DECLARE @H CHAR(1) = '''';

the CONCAT version then becomes something like this:

            
March 19, 2020 at 7:53 pm
            
#3735699

            
            
                                                
        

 

'''' + p.firstname + ''',''' +
p.lastname + ''',''' +
i.city + ''',''' +
t.stateAbbrveation + ''',''' +
Convert(char(5), c.peopleId) + ''''
as insert_string

Every SQL database restore must start with a full backup restore.

After that, you can, if you want to, restore a differential backup (that was taken after the full backup you...

Use this to generate the SELECT statements to review.  After you've verified the statements, run them if / as you see fit.

DECLARE @DTCHANGEDON_found bit
DECLARE @DTCREATEDON_found bit
DECLARE @end_date...

You really should start using the new syntax, with parentheses around the row count:

SELECT TOP (2) *

FROM STRING_SPLIT(@s, ',') AS ss

Make sure you pre-allocate enough log space to handle any logging required.  If the log file has to grow dynamically, that will be very slow.

Make sure the new data files...

Maybe a permissions issue?  I don't see why drives wouldn't show up for that query.

That code is extremely inefficient though, since it pulls drive info once for every file, instead...

Ultimately any part of a disk drive file can be corrupted (or attacked?).  A bad controller, etc., can cause unexpected corruption.

Again, it's my understanding that there is no way to...

It's very difficult for many people to split the logical and physical design.  But, it's critical to a good design that you keep the two separate.  Getting a developer involved...

As I understand it, if you lose the certificate, you can't read the data, period.  Back up that certificate and make sure you can restore it!

IIRC, from the one time long ago I looked at SQL Diagrams, it is only a physical design, there is no separation of logical and physical.  If you don't distinguish...

I would think you could summarize the data just once, for all BSP ranges and WIN/LOSS combos, then join to that, if needed, to get the final result.  I can...

You simply do your best. If you are not...

The referencing_id would always be the current db, I would think.

You should check the referenced_server_name as well as the db name.  It's possible that local db1 could point to the...