Unanswered: How do I stop a proc from dying when it errors?
Here is our situation, maybe someone has done this before:
At our company we have many databases on many different machines. We just wrote a proc which goes to every database on a machine and collects user info ie; all login ids, group info, aliases, and writes it to the machines common database. The problem is that due to security, the id we run this job with, may or may not have access to all databases on a machine. If the ID does not have access to the database, the proc dies. Instead of crapping, we want it to make a note in our common database saying that ids are unavalible from that database.
Anyone been through this situation before or know a solution?