Create a database project using Visual Studio (I believe that 2008 and 2010 support it). Store object scripts within the project. Check the project and its associated files in the form of version control software (SVN, git, hg, SourceSafe ...).
You must have a database administrator or a dedicated person who is responsible for deploying code changes to your work environment. You can customize the database project using scripts before and after deployment, which will simplify working with them.
I cannot recommend saving user objects to master
; IMHO, you are better off with copies in each database. If you manage your code as described above, it doesnβt matter that they are duplicated, since the source is in the same managed location.
source share