It's two steps. One, gather the info. Two, based on that info, send an alert. So, a rough outline of psuedo-code would be something like:

SELECT COUNT(*)

FROM dbo.mact_data

WHERE dtstamp > (GETDATE()-60);

Then...

Yes. Just grant them read access to the view. Here's the documentation and examples.

I'm not sure what you're looking for in terms of help. Write a query that satisfies the criteria you outlined. Schedule that query to run using SQL Agent. Put an...

Ain't gonna lie, I'm shocked as heck that the optimizer didn't timeout on this query.

The good news, lots of index seeks. The bad news, scattered all over the place, all...

TRUTH!

Doggone it. Silly thing took me to an old post on the thread and I responded a second time. Sorry. I'll leave it up.

I hope that it was just the first,...

Looking at the plan, it's calculated columns or constraints. It has to retrieve the data in order to do the validations, so that's why you're seeing a lookup operation.

The execution plan would help a lot.

Also, two different ORDER BY statements going in different directions? Yikes. Maybe... maybe, two indexes ordered in each direction could help performance. That's a...

And then you toss in aggregations and columnstore gets faster. Or, an XML index can speed up Xquery. Spatial indexes can speed up spatial queries.

There isn't a single "This index...

Just reinforcing the correct answer. A TOP query without an ORDER by doesn't guarantee any particular order. Further, if you look at the execution plans for the two queries, you...

Without seeing the execution plan itself, I'm just guessing. However, it's likely that you're seeing lookups because of foreign keys. Modifying columns that don't contain any foreign keys will likely...

Do you really need all those DISTINCT statements? Shouldn't the one that fills the temporary tables do the job for the ones that follow? Each of those requires aggregation. Also,...

The deal with shrinking databases is not the simple act of a one-time shrink:

"Oops, we had a bad data load. Gotta shrink the database."

Despite the dire warnings you get all...

You may have to restore to a new database and then migrate the data over manually or using a tool.