restore with standby.

Again, I don't think you can add SQL2016 nodes. You'd add SQL 2012 nodes and upgrade them to SQL 2016 in place.

Ah, ok.

Then I believe the same  principle applies. You can't add a new SQL node at 2016 because the database version is different. What you do is...

Use SESSIONS_CONTEXT() instead. Still some dangers. What you can better used is actual SUSER_SNAME() results. Note that if you use this with groups, like ISMEMBER(), there is a load in...

Not that I know of either. There used to be a note at MS Support, but the article looks pulled.

I did find these:
https://dba.stackexchange.com/questions/66513/sql-server-cross-domain-transcational-replication

Remember that your system generates xx log per unit of time. You might see something like:

8am-5pm 5GB log space
5pm-7pm - 10MB log space
7pm-8pm - 10GB log...

I'm not sure what the question is here.

You can't add a 2016 node, AFAIK, but you can add a 2012 node and then upgrade that to 2016. The upgrade process is that you upgrade secondary nodes and...

Hyperlinks are directions to the host, and you have no control over whether a link opens in a particular browser. If you can call ieexplore.exe, you can pass in a...

No.

I don't think this is an issue. I had an AD user create a db and then removed the AD user. I don't see the user removed, so not sure...

I still see this doc for 2016/2017. Are you sure this is going away?

This isn't hard to write in T-SQL with dbmail, but it seems easier with...

Seems like a not-Jeff day

Legacy on 2012 or earlier?

I'm not sure you can get the database moved without some sort of backup/restore. Log shipping is just an elongated backup/restore, but since you...

When you execute the program, I assume you're executing the console program. That means your security context. Are you running this from your machine or the server?

Agent can...