Looks like we will need to monitor logins and login attempts, which is something rarely done. Does anyone track logins on their systems? Within a order of magnitude, how many...

What parts of this process can't be done by just straight T-SQL scripts?

Eric,

Are they just afraid of electronic signatures?

How did you decide on the license for this? It is a fairly restrictive license, is there a better term for it?

Maybe this will be a solid step in making me an armchair epidemiologist, or at least more useful to the people who ask those kinds of questions.

What license goes with the script?

Replication solves a lot of business problems, doing something well enough rather than technology problems, which do things in some guaranteed fashion.

I've spent more than a decade solving problems with open source tools running on Windows. I trade convenience and polish for utility.

I always appreciate seeing the underlying queries for stored procedures

the script here offers more flexibility then the sp_help function

Thanks!

Our main purpose for something like this is to do a database restore. Which method of killing processes do you prefer to do that?

I'd go between the idea of guidelines and best practices, with the notion of recommended practices, and giving the downsides of what ever you are adopting in a clear way.

Is anyone trying to make the tool look at system objects (registry/file) as well? Are their complimentary projects to do that?

Remember that when you talk to someone you will get a whole lot more communication then the initial ticket.

I think some of those geeks would also say that they want to supplant Microsoft licensing from their data.

Microsoft handles the needs of small numbers (less than 100) CPUs...

I like the cloud as a redundant backup. There is still a place for something I can use reliably once a week if the pricing makes sense.

It sure does help...