Greetings;
I recieve a monthly phone bill on cd. I am trying to autoimport these CD's into a SQL server database with a DTS in MSSQL 2000. I have noticed on the bills every so often they change the structure of one of the ACCESS DB tables by one row or something small.
I am trying to figure out how I can test the structure of the database before trying to do the actual imports, I want to do this so someone else can actually do the imports as we get the bills.
Is this a possibility? Or am I going about this all wrong?
Thanks
nhas
Then you want to check the structure of table and then execute different packages according to the actual table, right? But from your description it seems the chages of data structure come from source data, not detination tables in database--so will it help if we check the table structure in database? I don't thinks so. You may need to have serval tables with different schema in your database to host the bill data in different structure, and use different DTS tasks to import data in different sturctures.|||lori_Jay;
Yes the table scheme changes on the import, rarly - like last month. I just dont want to have to verify the MS Access visually before I do the import.
I was thinking of one DTS but import one table at a time, in steps. But having multiple DTS packages maybe easier to do.
Is there a way of telling DTS to do a trial run to make sure that the Access will import before firing off and not importing all fields because of a billing change?
Thanks
No comments:
Post a Comment