Please don't ever do that. There's a critical security flaw in your code (SQL Injection). NEVER concatenate parameters into a string and execute the string.

Have a look...

WAITFOR DELAY '00:00:10';
SELECT 1/0;

Yours fails instantly because the last query throws a parsing error, and the batch is parsed before any part of it starts...

Keep in mind that if you have any monitoring tools that calculate the change in wait stats over periods in time, clearing them will break the tool.

You should be learning constantly. Whether it's R or Python (I prefer R) for data work that can't easily be done in the DB engine, or Powershell/Bash for automation, or...

To be clear, Daniel, what you probably want to do is, each night download the .trn files from that day, and restore them in order WITH STANDBY. That'll give you...

No, that's the table (index 1 is the clustered index)

You can try dropping the clustered index, but do it on a copy of the DB, not the production...

I don't reset them when doing monitoring. I record them at intervals and calculate what changed in those intervals

I'd probably start with an Extended Events session to capture exactly what statements are run by each, and get their execution characteristics.

Corruption is usually related to problems with the IO subsystem.

Min memory has nothing to do with cached plans or plan size.
I strongly recommend that you leave that setting alone.

In a busy OLTP system, most queries...

That's how identity works. You can and will have gaps, and those gaps are expected. The identity value should be meaningless and not something taken to have some relation to...