FYI to everyone.
I've started full-text index population on the new Public Message Search table. Right now, it's using about 65% of the database server's CPU. That's a bunch, but the remaining 35% is more than enough to handle night-time traffic around here.
Let's cross our fingers and hope it's done by tomorrow morning. If it's not, things could be a bit (an understatement) slow until it's done.
I started it 7 minutes ago and it's processed 70k messages. So call it 10k per minute. 4.2MM messages divided by 10k per minute equals 420 minutes equals 7 hours. We should be just fine.
Depending on other demands placed on me tomorrow, I should be able to make decent headway on rewriting the few lines of code it'll take in Advanced Search to make it use this table, the stored procedures to insert and update the search table when new public messages are posted, and add code to the posting routines to call the new procs.
I'm not going to give an ETA on that, mainly because I have no idea what other hands will be on my time tomorrow, but it's less than 8 hours of work involved and rest assured that fixing Advanced Search is my highest priority behind putting out bigger fires and dealing with advertisers.
I *might* work on it some tonight, but working on the site is more than a little painful and far less than 100% productive when dealing with a single laptop on dialup rather than the 3 monitors and DSL I have at the office.
Market Data 
Markets 
AI
