i have a process that does something exactly like this; the issue is the remote server has the "freshest" data, but we want the dbo table available  without significant locking.

for a stored procedure, the EXECUTE AS must name  to a USER in the database

it cannot use a LOGIN who is not an EXPLICIT USER in the database.

if you keep insisting on active connections, then as Gail said, the answer is basically no.
people do not connect to tables.

 you cannot track who is actually...

maybe the system DMV sys.dm_db_index_usage_stats has info you might be looking for?
with that, you could see how many times a table has been accessed,and the lasttime it was accessed,...

Database Mail is asynchronous, so anything using sp_send_dbmail just inserts mail into the table dbo.sysmail_mailitems, which the engine just sends the emails out one at a time anyway.
throughput wise,...

what specific error are you getting?
I would suspect that the issue is you are using a temp table instead of a permanent table,and unless you've got the setting "RetainSameConnection"...

i did this once.
once.
my mail server / domain was banned by most large ISP's for spamming. my list of contacts was just shy of 5000 people, and i...

the items are from cache, and are not the currently running as of this moment queries; the users could have disconnected long ago. you also get an execution count, so...

SQL does not keep a history of data changes. 
unless you already have some kind of audit system in place, an audit table with a trigger, change tracking, change data...

Right, but the administration of everything else except availability groups or replication can be simplified. So yes, the  cname is not helpful for that, but it will save time on...

we create CNAMES and make our Developers use those for connection strings specifically so we can upgrade or replace servers behind the scenes.
if everyone connects to the cname [SuperServer],...

if this is deployed to the SSISDB catalog, then there is a detailed log you can check(SSMS>>Object Explorer>>Integration Service Catalogs>>SSISDB>>TheSpecificProject
since you say it runs on Saturday without errors, but...

yes, SSRS can use an expression to validate the length of your input; 
this stackoverflow has an example that was testing a credit card length = 16, basically the same...

As always, it depends on the implementation. 
if it is just an SSMS consumption,
at the procedure level, all you can do is add an error;
IF LEN(@param)...

yes, that was it, thank you Jacob and Sue!
i was locked into search dmvs with *xe* in them.
Awesome, and thank you again!