Not perfect, but this should get you much closer:

SELECT 
    ReferencingObjectType = o1.type,
ReferencingObjectName = o1.type_desc,
ReferencingObject = SCHEMA_NAME(o1.schema_id)+'.'+o1.name,
ReferencedObject = ISNULL(ed.referenced_database_name, DB_NAME()) + '.' +
 ...

I'm a bit confused about "Return values" being plural.  Isn't there only a "return value"?  Yes, somewhat pedantic mood as well :-).

I could think of 4 rather easily, I'm sure there's more, as others have noted.

Be sure to specify "WITH (TABLOCK)" on the table being loaded.  It's not technically needed at 2016+ level but it doesn't hurt.

The very first page of a table that SQL...

• This reply was modified 6 years ago by ScottPletcher.

If you don't have permission, you won't have permission period, but the command-line way to get the text is:

EXEC sys.sp_helptext 'view_name'

Here's the main article I was basing my comments on about minimal logging in SQL Server 2016:

https://sqlperformance.com/2019/05/sql-performance/minimal-logging-fast-load-context

SQL Server 2016 does allow far more minimally-logged INSERTs to an existing clustered index than any earlier version of SQL.

And, in some instances at least, it does allow simultaneous INSERTs...

I'm not sure.  I don't know if SQL can do parallel writes to a new clustered index.

Given all the possible table options -- data compression, large value types out of...

I think it could.

I'd certainly expect the initial SELECTs from the table to be done in parallel, and thus likely the sorting as well.  But the writes to the final...

Try using datetime as the destination data type, rather than smalldatetime.

Instead of using WITH (NOLOCK) on every system table, use SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED for the session.  That way you don't have to worry about missing one...

I tried to come up with something other than Extended Events because of this in OP's q:

Extended events is an option, but it's doubtful that my company will approve this...

I'd avoid INFORMATION_SCHEMA views completely.  I've found them to be slow (I understand that the view definition doesn't look like it should be slow, but real-world use says otherwise; if...

You can use "WITH (NOLOCK)" on system views, and I suggest you do so here.

Your join on the types table is incorrect, you should use user_type_id not system_type_id.

If you're worried...

It's not really an instance-level trigger, it's a db level trigger for the master db, because all logins are created in the master db.  The DDL event would be CREATE_LOGIN...