Data Migration

Hello! What we have currently is a large number of text files (over 5,000) containing data that needs to be moved into an SQL Server database (we use SQL Server 2000). The good news is that every text file contains data of the same type and can be easily exported to a relational database. There are about 100 pieces of data to be exported from each text file. I woud anticipate that the easiest way to do this would be either to write a VB application that would cycle through all of the text files and upload the data from each file into SQL Server or else to write a DTS script (Data Transformation Services in SQL Server) to import all of the data. Either way we prefer a Microsoft-based solution that we can maintain down the track (it could even be .asp if you like) and we would like it to be as maintainable as possible with a different function for each type of data rather than a 100 lines of consecutive code! ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). Customized Deliverables: We do require the data to be dumped into specific tables. Unless you know something about the game of cricket, you will need to ask questions about where the data can be found in the text files. The tables will look something close to this... MATCH_DETAILS TABLE Match_number, Match_type, ground, date, overs, result, toss, balls per over, attendance BATTING_INFORMATION TABLE Match_number, team, batsman_number, name, batted,how_out, bowler, fielder, runs, minutes, balls, 4, 6, WK, Captain INNINGS_INFORMATION TABLEMatch_number, total, team, overs, minutes, wickets, Total_Extras, lb, w, nb, byes FALL_OF_WICKET TABLE Match_Number, Team, Wicket_Number, Total, Overs_gone, Batsman_Out BOWLING_INFORMATION TABLEMatch_Number, Bowler_Number, Bowlers_Name, O, M, R, W, wides, nb * * *This broadcast message was sent to all bidders on Wednesday Aug 23, 2006 7:49:47 AM: In Response to common questions asked by most bidders: 1) Familiarity with Cricket is essential. Please do provide relevant knowledge. 2) A preferred solution would be to use Transact SQL within a stored Procedure. However VB6 is still an option. 3) The files referred to are all .htm files. I have used the phrases .htm file and text file interchangably as they are basically the same in terms of parsing data. Thanks! ## Platform The script will eventually neeed to be run on a Windows XP machine running SQL Server 2000. It also has VB environment set up.