This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SavexDir big MSSQL log when shrink tempdb extreme growth

We installed PureMessage for Exchange and we noticed it creates 4 databases on our MSSQL cluster. The SavexDir had a big log file and after shrinking it resulted in an extreem growth of the MSSQL system database "tempdb" that stopped our MSSQL cluster. After installation of PureMessage we did the following to shrink the SavexDir log file:

  1. Changed the recovery model to simple.
  2. Shrinked the database log file with SQL Server Management Studio. (And it shrinked)
  3. Changed the recovery model back to Full.

With did the above steps because there wasn't any other way it would shrink..

Microsoft told us they could see that the SavexDir database from our CAS/HUB Exchange servers where caussing the problems because some select statements did not close their workload in the temdb that was caussing the extreem growth on the SavexDir. We now stopped the Sophos services on the CAS/HUB servers so it would not cause any problem. Now we ask our self: Could this problem be caused bij the above 3 actions I did to shrink the database log file or is there something else rong in the Sophos configuration?

I hope someone noticed this problem and can explain to us what happens here?

Thanks,

Maarten

:39641


This thread was automatically locked due to age.