SELECT INTO cannot specify a filegroup. The created table will be created on the default filegroup. If you want something else, you have to use the full, explicit CREATE TABLE...

Restoring a backup of a database and running CheckDB on the restored backup is a perfectly acceptable way of doing integrity checks. The only problem with it is the potential...

You never block yourself. If you have just run a data modification, in that same session you can always see the data you modified.

As I said above, no. There is no guarantee that SQL will use max server memory, it's just...

Max server memory is just the upper limit that SQL is allowed to use. There's many cases where it won't reach that. Ones that immediately come to mind is it...

Not EXECUTE AS CALLER. EXECUTE AS and specify an explicit login that has insert permissions on the audit table, then you don't need permissions to public.

The way I usually recommend is to use impersonation on the trigger.

CREATE TRIGGER ...

WITH EXECUTE AS ....

And execute it as a login that has insert permissions into that audit table....

So you're looking for some scheduled windows script that's running against your databases. I would look first at Windows Scheduler, see what's in there.

Depends on the query, but TOP adds a row goal to the query which could result in the row estimations being wrong (the row goal gets used instead of the...

Something running as the local system is trying to log into your server and access the databases. Could be a service running as SYSTEM, could be an application, but the...

This.

That output is truncated.

I wasn't saying you truncated it. I'm saying that the package output, as shown in the job step history, is truncated. It's cut off when it's...

I mean exactly that. The output that you are looking at (that you've been posting) is truncated (cut off)

Architecture of what? What are you looking for information on?

All you're seeing there is truncated output.