Posted by Greg D. Moore \(Strider\) on 03/03/07 04:21

"Erland Sommarskog" <esquel@sommarskog.se> wrote in message
news:Xns98E7F04801BCBYazorman@127.0.0.1...
> SQL Learner (excelmodeling@gmail.com) writes:
>> I have a table with 8 millions records. Some of the fields needed to
>> be parse and modified. Example, "ABC DEF" will be parsed into two
>> fields "ABC" and "DEF". And If there is "123" in the field, if will
>> be replaced by "456". For example, "XYZ 123 AAA" will be "XYZ 456
>> AAA". Also, update query and append query will be used in the
>> project.
>>
>> Give the above information, what will be a faster database to do this
>> - MS-Access 2003 or SQL Server 2000?
>
> Benchmark, don't ask. Performance questions are very difficult to
> answer up front, because there are so many "it depends". What I can
> say, is that if you do this in Access, you should do it in a local
> Jet database, not not a linked SQL Server table.
>
> If you ask me to place my bets, I put them on Access for this one.
> String processing is not SQL Server's best game.
>

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.


> --
> 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




--
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com

[Back to original message]