Reply to Message

View discussion in a popup

Replying to:
admin
Immortal
Immortal

To shed some light on the transaction log size with the SQL express and simple recovery model.

You do not have an SQL Server agent with the Express version, therefore everything on the database uses stored procedures and no jobs to move data from one table to another. This basically gets logged into the transaction log, when one full transaction is finished this should be automatically cleaned out of the log afterwards.

The SQL Express is not only limited in size but also in CPU and memory resources. What you are currently doing is hammering your artificially undersized (because MS actually wants to see money for full performance) SQL server with I/O and CPU usage with all the transactions for the logins and logouts.

Something is using your domain user to establish a connection to vCenter server. If you have a look at the tasks and events view for the events on vCenter level in the vSphere client you will see username@ip logged in messages flowing. The IP is important, if it is an external IP, look at that system to determine what is installed on there that could connect to vCenter Server. If it is local it is a service on the local vCenter Server system itself.

I have seen several vCenter Server plugins causing that kind of issue (NetApp from the top of my head in an older version), monitoring solutions like Nagios that are very aggressive also can cause those issues. I have also seen Heartbeat causing this kind of issue. It is pretty hard to determine what exactly it is and usually involves some kind of guessing to find the correct service to tweak.

You could buy a full SQL server license (I think standard starts at around 500 Euro or something like that, didn't check in quite a while) which would "resolve" your issue in the way that you are not crashing anymore because of a space limitation. Until your disk would be completely full and you would be crashing because of that. So full SQL would only mask the symptoms for a little longer but would not be a long term solution.

Reply
0 Kudos