1
I don't know if I should post this here or in SQL Server, but thought I'd start here.
We have been using the default ASPState database that microsoft creates for session state tracking. Even though we sometimes only have 10-15 users connected, it is the highest source of database waits on our entire SQL Server. The waits are always on CPU and "LCK_M_U", whatever kind of lock that is.
I used to only delete expired sessions 1 x per week and there were 60k rows in the db. Since then, I have implemented various types of jobs to delete the expired sessions - they run every minute now, and there are only about 400 rows in the table. But the waits have not changed. Does anyone have any ideas about why there are so many waits on it or what is happening to it? The transaction logs have started growing so fast I have started to truncate them every 10 minutes just to make sure they don't take up the entire disk... and the DB is in SIMPLE recovery mode! Any ideas to try would be much appreciated.
Amy
