Every time I perform a restyling of the FTS SQL Server 2008 catalog, my server remains in a state where the SQL Server process has 2.8 GB of memory and causes degraded machine performance. When you re-use the SQL Server service, it returns up to approximately 350 MB, and the performance returns to normal.
Is it okay to restart the service after completely rebuilding the text? Not sure what's really going on behind the scenes, but it looks like it's a significant memory leak, if I can call it.
I am open to any advice. Thanks in advance!
Scott source
share