|
|
Posted by Erland Sommarskog on 03/03/07 09:58
Greg D. Moore (Strider) (mooregr_deleteth1s@greenms.com) writes:
> And further, I'll again suggest perl.
>
> It may very well be faster to export the data, manipulate it in perl which
> is designed for string processing and reimport it.
>
> Especially if it appears to be a one time thing.
I could consider doing a thing like this in Perl, since I'm fluent in
that language, and thus I could cut down the total time, that is
development + execution. Assuming, that is, it is a one-off.
If there is need to do this on a regular basis, there should be other
factors to determine whether to do this in Access or SQL Server. Just
moving the data to SQL Server - or a file - and then back, is likely
to be a loser.
Of course, it's perfectly possible to use ADO from Perl to access the
Access database.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|