2012년 5월 9일 수요일 오전 8:03
We are experiencing a problem with the Indexing Service on a Server 2008 SP2. We are running SQL 2005 on the server, and our intranet provider uses Indexing Service and it's required to run on the same server as our SQL database.
The Indexing Service is indexing a large amount of data and files, around 3 million files using around 400GB. Currently the index is using around 320GB of disk space.
I have tried adding the Indexing Service to a new server running Server 2008 R2 SP1 and added the same folders and it only requires around 2-5 GB to make the same index.
Has anyone seen this "problem" before?
- 편집됨 LasseF 2012년 5월 9일 수요일 오전 8:21
2012년 5월 9일 수요일 오전 8:20The strange part is that if I open Properties for the index through the console it tells me that the "Index size" is 7040, which I assume is in megabytes. If I right click the actual folder containing the index it uses 324GB.
2012년 5월 15일 화요일 오전 5:53중재자
The Windows Indexing Service uses a fair amount of disk space (approximately 30% the amount of the original files). If the shared directories on the network are large, it can consume a considerable portion of the computer's memory and processor cycles. There are several options for configuring the Indexing Service to improve performance.
For more details, please refer to the following article.
Note: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.
Jeff Ren TechNet Community Support beneficial to other community members reading the thread.
2012년 5월 15일 화요일 오전 9:51
Thanks for the reply.
If it should use 30% of the original files, according to my math 320GB out of 400GB is not 30% :-)
The thing I don't understand is why a Server 2008 uses 320GB and a Server 2008 R2 uses 2-5GB on the same folders?