Thanks for the clarification and I'm with Barry. Do not do this as it is asking for issues.

If this were an extremely busy system and the were performance problems from...

Was the service account changed? I've seen that cause the issue.

Also check the system time on the server and other machines, including the DC. Differences can cause this.

I'd listen to Chris, but I might look to add multiple indexes on these tables. Look at the queries and see what they're using for their WHERE clauses.

Right click the server in SSMS and select Generate Script.

You need to be sure you haven't set the server to not use parallel queries or the threshold is too high. If so, you might see one CPU working hard...

It's used in full-text indexing, and contains the indexes' data from that system.

select * gets expanded to all columns. If you do not want all columns, you must specifically name the columns in the query.

Identity has nothing to do with primary key. They can be the same, but don't have to be.

What's an occurence? Not sure what you mean here.

No easy way, you'd need to decode the information and look for patterns.

Hmmm, not a lot of responses. Guess lots of people don't do this, don't care, or are watching the markets.

Fisher-Price interfaces are good for management. Big buttons, lots of color.

Windows are fun. Cabinet doors are better with the trim. Need to replace one of those this weekend.

My pleasure, thanks for the update.

Security can be a pain when people are a member multiple groups. Not a bad reason to watch which groups you give SQL access.

Why can't anyone write to the db? Not to question your idea, but I'm wondering if there is something else we can come up with.

Is there a question here?

sysdepends doesn't "fix" things created out of order. What are you trying to do, update it? There might be some things that can do this, but why do you need...