I disagree on the fact that coupling mirc to a an sql database is using it in an 'odd way', though there's some perfectly valid reasons for not doing it.
I'd love to see something _LIKE_ SQL-Lite, whcih is a very trimmed down relational database and has started to be itegrated into php - but it would be of little value to many scripters.
Its perfectly logical if your scripts try to provide an IRC service, such as an anti-spambot service that listed X numebr of attacks from N addresses.
However, to overcome this we have access to things like myODBC and COM objects - which bridge the gap between mirc and a database (wheter local or remote).
Furthermore, if your interesting in writing a dedicated service, your better off writing the business logic side of things (the remote server) in a sturdier language (again, php, jsp, etc).
Then simply use sockets to access the server data.
If mirc were to change its aim from a 'text based IRC client' to a 'general text based communication client WHICH targets IRC' and started to provide some basic socket wrapper functions specific to protocols(languages?) like RSS, SOAP, and general XML functions, perhaps this would make this style of database + client integration a lot easier.
However, I think thats more a job for us scripters than for the mirc development team...