That looks good.

You don't need to store it in a temp table if you are dropping it straight away, it will display the result set from each database in its...

Take a look at the function sp_msforeachdb, and see if you can make your code work within that to iterate over each database to pull the information you wish.

Additionally you...

SQL on a Domain Controller, wow you're brave, if SQL is compromised so could be your entire domain.

So you need to setup a trace, extended event, audit to track failed...

SELECT prin.name, perm.permission_name
FROM sys.server_principals prin
INNER JOIN sys.server_permissions perm
ON prin.principal_id = perm.grantee_principal_id
WHERE prin.type = 'R' and prin.name = 'test'

Replace 'test' with the name of the role you have...

You may not for your...

It may be best adding an audit or an XE session to track more information about the login failure, more specifically the application name it is using, hopefully that will...

https://learn.microsoft.com/en-us/sql/relational-databases/databases/move-database-files?view=sql-server-ver16

Microsoft has a article in reference to what it is you need do to.

Please do take a look at this and come back with any further questions to this method.

That’s where xp_dirtree would come in handy

Something like the below would be the way to do it.  It mentions csv but you can tweak it to whatever file extension you...

Format files are notoriously tricky to get right.

However with your sample file and sample table you can import the data easily using

bulk insert saleshistory from 'c:\temp\sh.txt' with
(
fieldterminator...

Since the OP mentioned rebuilding from scratch, if that was me it would all be automated and replayable multiple times so that you know what you get each time you...

I think the title here has gotten me a little confused, but that may be my old school ways of looking at this.

When I see anyone mention a clustered SQL...

Ideally all your configuration like this should be stored in source control so you can easily recreate these things when they go wrong.

I would be looking at getting yourself familiar...

If you are using the SSISDB then you can query internal.packages and do some validation on that in the package_data column which you would have to do some manipulation against...

If it is SentinalOne I would recommend opening a case with MSFT, see if they can reproduce it as I know they update documentation based on 3rd party components which...

For the SQL Server Writer piece, change the default logging option to VERBOSE

C:\Program Files\Microsoft SQL Server\90\Shared\SqlWriterConfig.ini

Change "TraceLevel=DEFAULT" to "TraceLevel=VERBOSE"

Save the file, then restart the SQLServerWriter service.

This will give you more...