Whether there is a data export framework in the net or something. Under the development of legacy and data from old / legacy applications, I need tool tools to export new applications, there are approximately three similar systems to give you an idea to have an employee table of three. Is there any framework or DSL device for this? Or do I have to come up with all the code? When you want to migrate customers to a new product, how do you do it?
From our NN tool to our application, I can tell you that "easy way" is not. Each piece of software adheres to its own internal database structure and it will be never when you will design your own
Keeping this in mind, the most complex task Usually divided into two parts:
1) Determine what and how is the data stored in the heritage system. You know the table of PAXNOST Meaning Patient_Note_Statistic or things like that ... Once you have a The idea is where the data is (in one or more tables) ...
2) Export it and send it: Data Import due to "Errors" as a result of an Import Wizard in SQL Server Data can be deducted, zero values where permission should not be allowed, wrong format (eg 01/02/1009) and date with things like that. These types of problems vary from migration to migration but it all depends on the compulsions (or no!) Of the old system.
If you manage to do all of the above, you can import into your DB option (I can assume SQL Server) and then, when all the data is in the same DB and the minimum "Things with weird numbers", you can move to using T-SQL (or any other more automated process, I can move T-SQL to replace the old tables -> New Tables, If I am using Ipion which I can also be saved and again).
Always save every script you execute. Suppose you may have to re-apply it to everyone.
Always Back up your DB after "Important steps" so that you can restore -> OK -> Redo if you have
And remember that you'll have to do some more things by hand to almost always (Ie: update xxx set yyy = '' where zzz = null; and things like that still, all of this source data Depending on the quality, always the worst value.
Make a good text editor, in which you search fast / Be careful from the line Ending and Field Separator If you use a mix of Windows / Unix (if you use ASCII files, which I often use); MS Access for quick table import / sanitize Or even using MS Excel is never bad if you have those tools (excel per line can not be more than 65535 lines, remember, use access.)
data tr Transferable objects (DTOs) are very good, but depending on the work, sometimes it becomes PITA. / P>
Good luck.
Comments
Post a Comment