You were trying to add a check constraint, therefore I mentioned check constraint in my reply, not because only check constraints are invalid.

And you'd create the AuditImport procedure in the database where you want the data to be imported to, not where the tables being audited are (shouldn't be the same place,...

SELECT * FROM sys.traces (fn_trace_getinfo has been deprecated for years)

Then consider the possibility that the problem is not in SSIS, but in Toad's display of the data that SSIS has loaded.
Double-check in SSMS before you go digging...

If it's happening in SSIS, then that's a problem. I can see a client tool weirdness, but SSIS is another matter.

Assuming SSIS is inserting into some table with...

What client is that?

Screenshot please? And where are you running this from?

Again, you don't have to run the setstatus separately (and you probably shouldn't), the script already contains the line to start the trace.

So leave...

What error are you getting?

Note that you don't have to run sp_trace_setstatus separately. It's part of the script already,

The first is the syntax for a default constraint (enforce a default value for a column). The second is referencing another block of syntax for creating check, unique and foreign...

https://docs.microsoft.com/en-us/sql/t-sql/statements/alter-table-transact-sql?view=sql-server-2017

You will note that ALTER TABLE ... ALTER COLUMN don't allow for the addition of a check constraint. You want ALTER TABLE ... ADD CONSTRAINT,...

Probably because it's in the process of reading the table and needs locks on both pages as it's locating the data. The ad-hoc SELECT, which is the one that has...

Nothing. It has no special meaning by itself.

This works fine, but has no meaning difference to any other variable
DECLARE @@i INT
SET @@i = 1;

Depends on how that snapshot is taken. Is it a block-by-block copy it's fine to checkDB.

You don't. Run CheckDB.

Nah, I've...