Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

SI - Site Forums : Silicon Investor - Legacy Interface Discussion (2004-2011) -- Ignore unavailable to you. Want to Upgrade?

To: SI Bob who wrote (1024)	9/25/2004 12:49:31 PM
From: SI Bob	Read Replies (1) \| Respond to of 6035

I really hate to do this because we did so well with saying the site would come back up again sometime this weekend, but had it running in less time than it took to finally drive a stake through the old one, but I'm going to have to shut it down for at least a few hours sometime this weekend. Something just occurred to me that could very well be causing slow response on posts. messageid in the message tables isn't currently defined as an identity field because we had to make sure we matched the messageid from the old site when we imported messages. You can't edit or specify the contents of an identity field. Because of that, when a new message is posted, the system first determines what the last message number was, adds 1 to it, then uses that as the message number for the new post. Terribly inefficient when a lot of posting is happening and it's just begging for deadlocks, which is probably what's happening on the intermittent slow posting. So that means that I need to shut everything down sometime this weekend, make a backup of the message table (takes over an hour), let SQL Server turn that field into an identity field (that by itself takes a VERY long time, but when I tested it before, I found that it at least didn't change the contents that were there already), then edit any routines that touch the message table so they don't try to edit/populate that field. Will probably do it tonight, and it should make the posting slowdowns less frequent or nonexistent.