> I do keep a separate table of robot UAs and match traffic rows to them > with op=eq to populate another table with robot IPs and non-robot IPs > for the day to speed up the report. Don't you think it would be > slower to match/no-match each IC request to a known robot UA and write > to the traffic table based on that, instead of unconditionally writing > all requests to the traffic table? If not, excluding the robot > requests from the traffic table would mean a lot less processing for > the report and a lot fewer records for the traffic table. > Perhaps you should create a column called "spider" in the traffic table and save a true or false value depending upon the [data session spider] value. You can then generate reports "WHERE spider = 0", for ordinary users, or "WHERE spider = 1" for robots etc. An index on the spider column would be nice, of course.
I let this roll around in my head for quite a while and I ended up writing the IC page accesses to my traffic table based on [data session spider] like you suggested. This should mean a much smaller traffic table and less processing when running a report on it. We'll see how much time it buys me before running the report takes too long again. I also need to set up indexes. Thanks a lot for your help. - Grant _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.