SQL Show (4/30/2013)
sqlnaive (4/29/2013)
All the DBs were configured with Full recovery but the backups were were never taken afterwardsCorrect me if am wrong. If backup never taken, then db will go into auto-truncate option, even in full recovery model.So it could not be your problem.
Nope. if you are not taking backups then log file will start growing to an extent where you will face disk issue. So once your DB has been set to bulk-logged ot full reovery, you MUST schedule log backups. Auto-truncate does not automatically gets enabled in full recovery. It is the feature in simple recovery model.
I had the same problem few years back, no space in ldf drive. But users were able to logon. We received error only when try to run dml statements.
This was because logging in is not an event that is getting written in log. In case you fire any DML, then there is the data change and that's when there is necessity to write in log file which is showing disk issue.