Quote:
If i have to guess any loginscript can fast and esaily write ini files in a public folder and then pick it up with a scheduled process from the server to the database.
Jose, that's the general idea. Based on current design, Client attaches to MySQL server via ODBC and updates via ADO. Given the frequency, accuracy and data we're collecting, this scaled well for about 600 clients per server. (Which is not dedicated solely to MySQL). So, we're redesigning with an Asset Insight model in mind. Client writes data to a file, encrypts it, sends to a store and forward server which sends to the DB server. The DB server serially imports the files.
So I'm mulling over the options of having the server import the data via ADO or by using the DB utilities to import SQL directly. I'm thinking that the SQL method will lack the required flexibility without poking into the DB.
However, it might be a lot faster for the tables that don't require recordset results, which make up the bulk of the data.
Not sure which method would make implementing several server import processes easier.
_________________________
-Jim
...the sort of general malaise that only the genius possess and the insane lament.
