Hello all, Window server admin here thrown into part time SP admin. I am having an issue with the above in a training env. For over a year this db was 185mb and one day last week it ballooned to over 70gb and the db log file grew over 90gb almost filling up the drive. I stop all services on the sp WFE, truncate the log and all is fine until I start up the sp services and WFE as the log file starts to grow out of control again until I repeat the above. The largest tables in the db are dbo.UserProfileEventLog at over 40gb and dbo.UserColleages at 30gb. Right now I have the site shut down. If I start the SP services back up the db log file will grow out of controls again, Has anyone ever experienced this before? Thanks Jim

This probably means that someone has configured the user profile import in the Shared Services settings on the SharePoint farm and defined a schedule and all user information is synchronized form Active Directory. If you stop the services, the SharePoint Timer job will pick up where it left of when the services are restarted. You should just have it complete the user profile import and the databases should stabilize. From the sizes of the database it looks to me that you are having a lot of user accounts in Active Directory. You should also check with the SharePoint admin that enabled the schedule. Usually the Windows server and database administrator should be notified when enabling the profile import.Dirk Van den Berghe