May 30, 2011 at 4:24 am
I'm sorry if this question is daft, but what seems an obvious need has managed to utterly escape me.
I have been trying to figure out how to export associated data from one database and import it into another. I don't want to copy all of the data between the two databases, just assume one patient record. That individual patient record has associated data spread between about 80 other tables, and these tables develop over time.
Now I can write some C# myself to pull all of that data together and spit it out as xml, however I then need to maintain that over time, ensuring that it is both altered whenever a schema change occurs, and I will also need to ensure that the created data is able to be re imported as well.
Is there a way of saying I want this patients data, and all associated data that will automatically crawl the associations and collect that linked data for me? I'd have thought that there was but I'm afraid my google fu has failed me on this. I'd rather it was done at the database level rather than in an application (although that isn't a hard requirement).
If there is a simple way of doing this I'd love to know, however if there isn't what is the best practice way of sharing this data with the least risk of data loss but the lowest maintainance?
May 30, 2011 at 4:42 am
Do you have a script or query of any one of them export and import ?
Regards,
Syed Jahanzaib Bin Hassan
BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA
My Blog
www.aureus-salah.com
May 30, 2011 at 4:59 am
I don't have a sample script I'm afraid, currently this is being done in C#. Seems rather silly to me to load an entire casenote from the database, convert it to xml and save it, then load it into the application from xml, process it and save it into the database on the next machine.
Probably worth mentioning that this isn't real or even anonymised patient data. We're researching tailoring patient education from the patient record so we are sharing fake patient data to see how it affects the education material tailoring. Hence the rapid schema changes as we alter the system.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply