Hello Guys,
I'm looking to get some advice on the best method to parse a CSV into my SQL Server 2k5 database. The idea is that the data will be passed in as a string to a web service. In the past I've spoken to people who seem to think that the DTS is the best method for getting the text into the database but to be honest it seems less fitting now the data is passed into a web service, by the time the server has placed it into a file and then DTS has auctioned it, I may as well use a Query or a StoredProc. What are your thoughts on this? The data comes in as something like this. GF:34:00:3F:FD, 6, 1, 2007-01-01 13:00:00, 1 GF:34:00:3F:FD, 6, 2, 2007-01-01 13:01:00, 1 GF:34:00:3F:FD, 6, 1, 2007-01-01 13:04:00, 1 GF:34:00:3F:FD, 6, 4, 2007-01-01 13:08:00, 1 GF:34:00:3F:FD, 6, 1, 2007-01-01 13:10:00, 1 GF:34:00:3F:FD, 6, 1, 2007-01-01 13:20:00, 1 GF:34:00:3F:FD, 6, 1, 2007-01-01 13:22:00, 1 GF:34:00:3F:FD, 6, 5, 2007-01-01 13:26:00. 1 GF:34:00:3F:FD, 6, 1, 2007-01-01 13:29:00, 1 GF:34:00:3F:FD, 6, 5, 2007-01-01 13:29:00, 1 GF:34:00:3F:FD, 6, 1, 2007-01-01 13:30:00, 1 GF:34:00:3F:FD, 6, 2, 2007-01-01 13:32:00, 1 Ideally this data would be placed into two tables, the first table would store all the MAC address's that are listed in the first column of the CSV, the other elements of the log would then be stored in a second table which would reference the MAC address using a foreign key. I'd be interested to hear your thoughts, these would most likely come in through the web service a few times an hour and be perhaps a hundred records long at tops. Thanks, Rob ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 by Adobe® Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:275329 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
