ASP/XML-based Tracker

Server load implications...

[NetGrease]

I've managed to "fudge" some ASP so that it adds visitor entries to an XML database every time someone views a page. This is going to be coupled with a major SEO offensive later this month, and only included on those SEO pages.

My question is this; what would the server load implications be for this, and therefore is it actually wise to track visits using this dynamic combination of ASP and XML "on the fly"?

Any comments appreciated.

[mark_roach]

Since there has been no response in the Tracking and Logging Forum to your question, I will move it to the Server Side Scripting Forum [webmasterworld.com]. There maybe someone there that can help.

There is a discussion over there already that whilst not exactly concerning your question might of interest to you.

flat text vs. dbms vs mySQL vs whatever [webmasterworld.com]

The idea you have seems reasonable to me, however if you are expecting a lot of activity beware of the comment regarding locking by Xoc:

I use XML for most things that you would use a database for. Has lots of advantages. There are still things that are appropriate for a database: when you have lots of data, although a SAX parser on XML may work just as well. By lots, I mean gigabytes. But the main thing for databases is when you need multiple users to write. None of the XML parsers that I know of support locking except at a file level.