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?


1 Answer 1


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.

  • i call my utility database DBA
    – swasheck
    Dec 11, 2012 at 20:47
  • I call mine Utility. Dec 11, 2012 at 23:49

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