Two days ago the transaction log filled up and my user's couldn't update or insert. One of my techs truncated the log, shrank the db, then did a full backup. The next day (Monday) we noticed that whenever our applications try to do a large number of multiple updates or inserts we get an S1008 "operation cancelled" error. You can do a small number of updates or inserts but after some limit is reached we get the error.
Here's a example of what is returned.
We've been running this db for probably ten years and never had an issue like this. Did the shrink db cause it? And what can I do to fix it?
Edit: I just discovered the "space available" on the db properties says 1.93 mb free when there's 14gigs left on the drive. I would think this could be the problem but I don't know why the db thinks it only has that much space left.
SELECT name, size, maxsize FROM sysfiles; returns:
name size maxsize CENTRAL_dat 6254000 -1 CENTRAL_log 128 -1 CENTRAL 1593 -1
The db file seems to be set so that it can grow as large as needed. The partition it's on has about 14 gigs free. I don't think it's running out of room.