(imported topic written by mholder91)
OK, I know this topic has been beaten to death, but through all the threads, I’m not finding any answers.
clients - approx 2900
database size - approx 15 GB
trans log size - approx 5 GB currently, but we’ve seen it grow as large as 30 GB
We are running in simple mode, nightly SQL backups are performed and I have less than 40 open actions. About a month ago or so, we moved the database from being local to a remote SQL cluster. We never had an issue with the trans log growth when it was local. On the remote DB, we had it grow as large as 30 GB and it almost ran the SQL server out of disk space. Our DBA shrunk the file down to about 1 GB and that lasted several days, but then it grew to over 25 GB again without even doing any kind of abnormal activity within the TEM console (actions, deploys, etc). The DBA shrunk it to about 1 GB again and this morning it’s already back up to over 5 GB. I can open a support case, but I just thought I would see if anyone here can give me any ideas as to what could be causing this, or where I should even start looking. I did run a query against the database for number of deleted computers and it came back 8065. While that seems like a large number, since we only have less than 3000 machines in our environment, I didn’t think it was unheard of since I’ve read of other customers with database growth issues returning a number over 100,000 or more. Any suggestions would be appreciated.