If I cannot find a book or info in a library, I always go to a librarian for advice and I have never been disappointed. However, whenever I need to find a solution or information about a specific problem in database adminitratin domain, I always do a google search and then spend hours and hours reading, analyzing, comparing, testing and finally deciding whether what I find is useful or not.

This prompts me to think why companies with complex database administration needs do not create a database administration librarian position, and I consider this librarian position will assume the following responsibilities:

1. Collect and categorize the database administration related scripts, which can be t-sql, PowerShell, VBScript, C++, C# etc

2. Collect and build the issue case library, for example,the librarian will collect the issues / error messages other users encounter and report in various forum, and the responses/solution from other users. This may also include the KB articles MS have published addressing a specific issue etc.

3. Research / collect / analyze the info of the SQL Server MVPs (and other distinguished experts, though they may not have MVP title), such as who is an expert at what and who frequently answer question in which sql server community etc.

4. Research / collect and document other useful information related to database administration, such as tips, undocumented SP / function, third-party tools, book reviews, interview questions etc.

I believe that if a team has a libraian of this type, the other DBAs will work more efficiently and effectively.