It looks like my site is getting quite a few SQL timeout exceptions as of late…most likely due to my upgrade to SQL Server 2005. I’d like to blame it on the hundreds of trackback spams I’m getting on a daily basis, but that’s probably not it. So, I’m aware of the issue and am running some traces/looking into it. Unfortunately one of the issues of logging exceptions to a database (as Community Server does) is that database related exceptions won’t be logged (of course), so I’m kind of flying in the blind here…hopefully I’ll get it resolved soon, so bear with me. Hopefully I won’t have to revert to SQL Server 2000.
What a bummer.



No comments yet