Unanswered Recreate SharedServices_Search_DB or delete

  • 8 กุมภาพันธ์ 2553 13:44
     
     
    Hi
    I've got an SharedServices_Search_DB  that have become rather large 700GB. We do think that something is wrong, so I would like to drop the current database and make/build a new one. Another alternative would be to empty all current data and repopulate. How can I do this?

    /MRW

ตอบทั้งหมด

  • 8 กุมภาพันธ์ 2553 14:08
     
     
    Hi,

    before deleting or recreating the database, can you please check the log database size
    it might needs to be truncated


    Best Regards, Ammar MCT http://ahmed-ammar.blogspot.com Posting is provided "AS IS" with no warranties, and confers no rights.
  • 9 กุมภาพันธ์ 2553 5:15
    ผู้ดูแล
     
     

    After log truncation, you can shrink the transaction log file to actually reduce the file size.

  • 11 กุมภาพันธ์ 2553 9:05
     
     
    Well the logfile is only 4,63MB with 3,26 mb available space, so that's not an issue. It's the datafile that is the problem. So i have to either drop the database or empty all data. How can this be done?

    /MRW
  • 11 กุมภาพันธ์ 2553 9:50
    ผู้ดูแล
     
     

    According to the Disk space requirements for the search database section in http://technet.microsoft.com/en-us/library/cc262574.aspx , both the metadata for all indexed content and the crawler history are stored in the search database. For this reason, the search database requires more storage space than the content index. If the size is too large to fit into one disk, you can configure the Search database to span multiple filegroups on different disks. Meanwhile, it will boost the search performance for SharePoint. For detail, please read:

     

    http://blogs.msdn.com/enterprisesearch/archive/2008/09/16/sql-file-groups-and-search.aspx

    http://blogs.msdn.com/agazzeri/archive/2009/04/16/sharepoint-server-2007-10-suggestions-for-a-reliable-low-latency-search-deployment.aspx

  • 11 กุมภาพันธ์ 2553 11:01
     
     
    I had a look at the disk space requirements, and I see that in the example they estimate 600Gb for the search database. But our installation is not this big, as far as I can understand. Now, I'm not a sharepoint guru, so how can I easilly verify how big this installation is? I only have 3 applications.

    /MRW
  • 11 กุมภาพันธ์ 2553 13:49
     
     
    Hi,

    How big are your Content databases ?
    I mean your Site colelctions and subsites

    The issue is we are trying to trace the problem before deleteing or recreating the Search Databases, which is a straight forward process


    Best Regards, Ammar MCT http://ahmed-ammar.blogspot.com Posting is provided "AS IS" with no warranties, and confers no rights.
  • 12 กุมภาพันธ์ 2553 7:35
     
     
    Hi
    WSS_Content is 474MB, and the 2 other content databases are 344MB and 287 MB. Admin_Content is 59MB. I also have  _PROF, _SERV, and site databases. These are 3MB, 13MB and 2,4GB. I guess these 3 are part of one of our sites.

    /MWR
  • 13 กุมภาพันธ์ 2553 2:48
    ผู้ดูแล
     
     

    Disk space requirements for the search database section in http://technet.microsoft.com/en-us/library/cc262574.aspx  use the following formula to calculate how much disk space you need for the search database:

     

    GB of disk space required = Total_Corpus_Size (in GB) x File_Size_Modifier x 4

     

    where File_Size_Modifier is a number in the following range, based on the average size of the files in your corpus:

    ·        if your corpus contains very small files (average file size = 1KB).

    ·        0.12 if your corpus contains moderate files (average file size = 10KB).

    ·        0.05 if your corpus contains large files (average file size 100KB or larger)

     

     Total_Corpus_Size means the total storage size of documents and list items crawled by SharePoint search crawler. If you only search information stored in SharePoint web applications, the size of data file (.mdf) for SharePoint content databases after shrinking can be a upper estimation. Alternatively, you can run the stsadm -o enumsites commands. The StorageUsedMB in the command output can be used as the upper estimation for search Corpus_Size.

     

    Your total content database size is less than 5GB, so

    Upper estimate for GB of search database  =5 (Total_Corpus_Size in GB) x 1 (File_Size_Modifier) x 4= 20 GB

    which is far less than your current search database (700 GB).

     

    Besides SharePoint web applications, do you configure SharePoint search to crawl other web sites, file storage or email storage? Please check Shared Services Administration > Search Administration > Content sources  

  • 15 กุมภาพันธ์ 2553 10:01
     
     
    Hi
    It seems like it only crawls local sharepoint sources.
    Under content surce details I have  the following:

    Content Source Type:    SharePoint Sites
    Current Status:             Crawling Incremental
    Current Number of Start Addresses:  4
    Last Crawled At:           2/15/2010 9:49 AM
    Errors in Last Crawl:      2

    All start adresses are lokal url's

    /MRW
  • 25 กุมภาพันธ์ 2553 14:05
     
     
    Any comments to my last post?

    /MRW
  • 7 พฤษภาคม 2555 17:48
     
     

    I aslo need assistance with this.

    I have a corrupted SharedServices3_Search_DB where it is in Emergency in SQL, the database still functions but is causing problems while I am trying to upgrade to SP2010. The Preupgradecheck report fails to complete. I found this error in the log.. Could not run BEGIN TRANSACTION in database 'SharedServices3_Search_DB' because the database is in bypass recovery mode. - File:d:\office\source\search\common\pkmutild\atldbext.cxx Line:1250

    I would like to create a new database from scratch so we can move on with our upgrade. Any ideas?