The Question and Answer Board

[Bob Zumbrunnen]

Dammit, that's still happening?

The new database server is running the newest version of SQL Server, and though it apparently handles locking the same way as the previous version by default (took hours of reading to find that nugget), it's seeming too aggressive. I backed it off a notch last night and thought that'd take care of that problem.

I'll back it way down tonight. It's not something to be done when the server's really busy or when there are a lot of folks around who will get timeouts while it makes the change.

Finishing the new version of post_info.asp will also likely make this problem go away completely, as the new version uses fewer locks and does all of its activity right at the db server in one fell swoop rather than the webserver hitting it a step at a time.