Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I recently installed Sharepoint 2013 onto a test server to look at the possibilities of upgrading our 2010 instance. After the installation, I noticed that far more DBs were created on my SQL Server. The databases I am not familiar with are:

  1. AppMng_Service_DB
  2. Bdc_Service_DB
  3. Search_Service_Application_AnalyticsReportingStoreDB
  4. Search_Service_Application_CrawlStoreDB
  5. Search_Service_Application_DB
  6. Search_Service_Application_LinksStoreDB
  7. Secure_Store_Service_DB
  8. StateService

We have a very simple implementation of Sharepoint, where the core functionality we need is the Document Repository Piece, which works just fine with the few databases that were created on the 2010 instance. My question is, are these databases truly needed, and if not, what is the best process in removing them from my structure. Please let me know if anymore information is needed. Thanks

share|improve this question

1 Answer 1

up vote 0 down vote accepted

These databases are mostly used by specific service applications. If you navigate to central administration and manage service applications you'll see which service applications are currently running on your farm. Each service app generally uses its own database which you can decipher from the database name.

Turn off the services you don't require from central admin and delete the service applications. If you view the details of each respective service application, it will tell you the database its using.

share|improve this answer
    
Awesome thats what I was hoping, just wanted to make sure there wasn't some tie-in to these from the Content DBs –  Isaac Levin Mar 25 '13 at 16:05

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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