Hi People,
I'm just wondering something about SQL. I maintain an accountancy
package for ISPs that still use dialup modems and the ones who allow
shell logins.
The package keeps track of data downloaded/uploaded, subscription
expirys, idle limits, user process cpu load, time limits, subscription
expiry notices and so on.
I want to know if I should be using SQL. I've had a few people ask me
for it in the last year or so, but I havn't been very keen to implement
it because I only see SQL slowing it down, causing more network
traffic, cpu load, etc.
What I really want to know is if SQL would be a good idea, and why, I
need some good points to SQL to get the enthusiasm up to actually do
it. I think I want to do it, but I'm not sure if SQL is going to be
all that great.
Also, does anyone know where I could find a *free* guide to writing sql
programs, and efficient sql commands or whatever?
If anyone's interested, the url for the package I'm talking about
is http://acua.ebbs.com.au
Thanks in advance,
Robert Davidson.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
