Take the 2-minute tour ×
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. It's 100% free, no registration required.

I have a windows server for host about 4500 data bases for same application. And this application have 34 fulltext catalogs on it, and the CHANGE_TRACKING for this fulltext index are AUTO.

And the point is, same times I need to shut down the server or move between clusters nodes, and when it’s starting up, all this 4500 databases was taking on line, and SQL server fulltext engine start the change tracking the fulltext index, all of the 153000 (34 catalogs x 4500 databases) at the same time. And this server takes a wile to bee online again. At the last time that was happen, I sow, after run SP_WHO2 on console, lots of FT_Gather command running, I know that this command is involved on fulltext crawl, but I’m not sure.

We are reviewing same aspects of this application, like: 1) We are taking off same of this fulltext indexes, 2) We are reducting the number of databases hosted on this server. 3) We are studing a change on CHANGE_TRACKING and force incremental reindex, with a Timestamp column.

But one doubt still alive, 1) Why the SQL SERVER take this lots of time to take online my fulltext catalogs?

Anyone can help us with this questions?

share|improve this question
1  
Can you be more specific on how long it takes to bring the server back online? Recovery needs to run on each database, which will take some time with 4500 databases. Auto change tracking is not known to cause slow recovery. Much more common causes for slow recovery are VLF fragmentation and Recovery interval set to high. –  StrayCatDBA Feb 8 '13 at 19:13
    
How many files and filegroups per each db? –  Marian Feb 8 '13 at 21:10
    
Explaining my previous question: SQL Cat's - How many files should a database have?. Quote: "Another factor to consider, from an administrative perspective, is database startup recovery. File recovery after server restart or after a SET ONLINE operation on the database are done sequentially. If you have many files (hundreds) in your database, this recovery process can take a long time because each file is opened sequentially." –  Marian Feb 8 '13 at 22:23
add comment

migrated from stackoverflow.com Feb 8 '13 at 19:41

This question came from our site for professional and enthusiast programmers.

Your Answer

 
discard

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