Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Possible Duplicate:
Setting up a central CLR stored procedure / function respository library for internal stored procs in other databases to use?

I have some simple user-defined functions for string manipulations. Most of them are actually CLR functions but not all of them are. I use them from multiple databases on the same server. What is the proper place to put these?

I've been placing them in the master DB so far. Is that a bad idea? If so, why? Is it standard practice to have a utility database that has no data but only progammability objects?

share|improve this question

marked as duplicate by Jon Seigel, Mark Storey-Smith, RolandoMySQLDBA, Mike Walsh, Martin Smith Dec 15 '12 at 10:14

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

up vote 8 down vote accepted

I would put them in a Utility database.

Putting stuff in the master database is something to avoid as it stores information related to the system configuration. If there is a problem with the master database, your SQL Server will go down. It's probably ok to put normal stored procedures used for server level troubleshooting like sp_WhoIsActive but I would never put a CLR based procedure in there.

share|improve this answer
i call my utility database DBA – swasheck Dec 11 '12 at 20:47
I call mine Utility. – Aaron Bertrand Dec 11 '12 at 23:49

Not the answer you're looking for? Browse other questions tagged or ask your own question.