views:

83

answers:

0

Each time I perform a SQL Server 2008 FTS Catalog Rebuild, my server is left in a state where the SQL Server process is at 2.8+ GB of memory and is causing performance degradation of the machine. When recycling the SQL Server service, its goes back down to around 350 MB and performance is back to normal.

Is it normal to have to restart the service after a Full Text Rebuild? Not sure what is going on truly behind the scenes but seems like it is a significant memory leak if I could call it that.

I'm open for any advice. Thanks in advance!