Bruce Young wrote:
> The server that does this has plenty of power and RAM but it still maxes
> out the CPU while it is converting the info from a text file to the DB
> format. It would quite often fail on that server if I asked CF to do a
> "transaction"; a method of keeping the old info while the new stuff was
> being put in with the ability to roll back if it all went horribly wrong.
Bruce, you did not say "how" you are getting the files from the outside
source, but let's assume that they are text files. If so, you should
consider using Perl on your NT with the DBI module to process the text file
into the Access tables. It is much more efficient than having CF do it. CF
just ain't built as a text processor.
> Ok... the question is... what are your thoughts about Access and MSSQL
> servers. Don't tell me it depends of load, transactions, number of records
> etc... ;-)
MS SQL Server can handle many more simultaneous users than can Access, which
will start getting fussy with just a few concurrent users. For the problem
you describe, though, I don't think you'd gain by moving to SQL Server,
since the problem lays in the method you are using to convert the data.
Jack
____________________________________________________________________
--------------------------------------------------------------------
Join The Web Consultants Association : Register on our web site Now
Web Consultants Web Site : http://just4u.com/webconsultants
If you lose the instructions All subscription/unsubscribing can be done
directly from our website for all our lists.
---------------------------------------------------------------------
