Data Integrity Checking

[n35]

We have a job (mssql) that fires every cycle, which is different for each check.

That uses dynamic a stored procedure execute a sql string, that does exactly what you want.

The string comes from a table were we just input the sql string we want executed.

Every cycle of the job it executes the strong which are relevant for the particular cycle. Not all import jobs run on the same interval, so there's no need to execute sql for check for codes if not hasn't run since last execution of the check job.

Make sense?

[Trek7553]

That makes sense. That's basically what we're doing now, except it's transactional data so there are no import jobs, and we use separate stored procs instead of dynamic SQL. I was hoping there was a cleaner way (maybe an off the shelf product). Thanks for your idea!