but the Data you provided...

the root of all harddrives are protected. N'D:\MyTrace.log' is invalid due to those protections.
you pretty much HAVE to put files in a subfolder.

I think that's partially incorrect.
what I read is that a linked server featuring the SQLOLEDB  is deprecated, and must be replaced with a server using the SQLNCLI) driver instead.

easy fix, the path for the file is wrong. it has slashes like a UNC path,a s well as a drive letter. it's one or the other. Maybe you mean...

this was kind of interesting, so I imported the file into a varchar max column, and used two CrLf as the delimiter, and the pipe character as the column delimiter(since...

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...