Adding any User objects to the Master DB is a very BAD idea.
Heh... At the risk of starting World War III, you are denying yourself one amazing tool for DBA's. Yeah, yeah... I know all the warnings everyone gives about MS maybe some day picking the same name as one of your procs (easily prevented by thoughtful naming) and MS maybe overwriting all of the master database and destroying your procs (easily overcome with a distribution sproc properly maintained in source control) but, as parenthetically indicated, those are minor almost trivial obstacles.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs