How to merge 2 duplicated database entry to 1 database after M&A?
After M&A (Mergers and acquisitions) 2 companies, we have 2 database systems with many duplicated data.
For example : 2 companies are Amazon and Alibaba, so I have many case like that : one customer bought the products from both of them. So I have 2 customer inside 2 database, but after M&A, I have to merge that to 1 database which store 1 customer will all productions which already bought by this customer.
P/s : 2 databases don't have the same schema.
Do you know any solution for this problem ?
Thank you in advance !
java database jobs
add a comment |
After M&A (Mergers and acquisitions) 2 companies, we have 2 database systems with many duplicated data.
For example : 2 companies are Amazon and Alibaba, so I have many case like that : one customer bought the products from both of them. So I have 2 customer inside 2 database, but after M&A, I have to merge that to 1 database which store 1 customer will all productions which already bought by this customer.
P/s : 2 databases don't have the same schema.
Do you know any solution for this problem ?
Thank you in advance !
java database jobs
add a comment |
After M&A (Mergers and acquisitions) 2 companies, we have 2 database systems with many duplicated data.
For example : 2 companies are Amazon and Alibaba, so I have many case like that : one customer bought the products from both of them. So I have 2 customer inside 2 database, but after M&A, I have to merge that to 1 database which store 1 customer will all productions which already bought by this customer.
P/s : 2 databases don't have the same schema.
Do you know any solution for this problem ?
Thank you in advance !
java database jobs
After M&A (Mergers and acquisitions) 2 companies, we have 2 database systems with many duplicated data.
For example : 2 companies are Amazon and Alibaba, so I have many case like that : one customer bought the products from both of them. So I have 2 customer inside 2 database, but after M&A, I have to merge that to 1 database which store 1 customer will all productions which already bought by this customer.
P/s : 2 databases don't have the same schema.
Do you know any solution for this problem ?
Thank you in advance !
java database jobs
java database jobs
asked Nov 12 at 3:03
BIZ
1036
1036
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Basic procedure:
- Make sure all your apps are writing to only one database, but reading from both as needed. If the schemas are very different you might need a wrapper app/library around the old database to wrangle things into the right shape for your apps.
- Once nothing is writing to the old database, you can create a process to read out the old records, transform them as needed, and load them into the new database. You'll have to make some decisions (together with business people) about what data to keep from the old database and how to transform it to fit into the new one.
- Stop your apps from reading from the old database.
- Remove the old database.
You'll need a lot of testing, preferably automated.
An alternative is to create a new DB with a schema that covers everything from both databases, but this may not be possible or desirable.
You can also search about "data migration" for more info.
1
Best thank @Ryan, that's exactly what I'm looking for.
– BIZ
Nov 12 at 7:42
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53255456%2fhow-to-merge-2-duplicated-database-entry-to-1-database-after-ma%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Basic procedure:
- Make sure all your apps are writing to only one database, but reading from both as needed. If the schemas are very different you might need a wrapper app/library around the old database to wrangle things into the right shape for your apps.
- Once nothing is writing to the old database, you can create a process to read out the old records, transform them as needed, and load them into the new database. You'll have to make some decisions (together with business people) about what data to keep from the old database and how to transform it to fit into the new one.
- Stop your apps from reading from the old database.
- Remove the old database.
You'll need a lot of testing, preferably automated.
An alternative is to create a new DB with a schema that covers everything from both databases, but this may not be possible or desirable.
You can also search about "data migration" for more info.
1
Best thank @Ryan, that's exactly what I'm looking for.
– BIZ
Nov 12 at 7:42
add a comment |
Basic procedure:
- Make sure all your apps are writing to only one database, but reading from both as needed. If the schemas are very different you might need a wrapper app/library around the old database to wrangle things into the right shape for your apps.
- Once nothing is writing to the old database, you can create a process to read out the old records, transform them as needed, and load them into the new database. You'll have to make some decisions (together with business people) about what data to keep from the old database and how to transform it to fit into the new one.
- Stop your apps from reading from the old database.
- Remove the old database.
You'll need a lot of testing, preferably automated.
An alternative is to create a new DB with a schema that covers everything from both databases, but this may not be possible or desirable.
You can also search about "data migration" for more info.
1
Best thank @Ryan, that's exactly what I'm looking for.
– BIZ
Nov 12 at 7:42
add a comment |
Basic procedure:
- Make sure all your apps are writing to only one database, but reading from both as needed. If the schemas are very different you might need a wrapper app/library around the old database to wrangle things into the right shape for your apps.
- Once nothing is writing to the old database, you can create a process to read out the old records, transform them as needed, and load them into the new database. You'll have to make some decisions (together with business people) about what data to keep from the old database and how to transform it to fit into the new one.
- Stop your apps from reading from the old database.
- Remove the old database.
You'll need a lot of testing, preferably automated.
An alternative is to create a new DB with a schema that covers everything from both databases, but this may not be possible or desirable.
You can also search about "data migration" for more info.
Basic procedure:
- Make sure all your apps are writing to only one database, but reading from both as needed. If the schemas are very different you might need a wrapper app/library around the old database to wrangle things into the right shape for your apps.
- Once nothing is writing to the old database, you can create a process to read out the old records, transform them as needed, and load them into the new database. You'll have to make some decisions (together with business people) about what data to keep from the old database and how to transform it to fit into the new one.
- Stop your apps from reading from the old database.
- Remove the old database.
You'll need a lot of testing, preferably automated.
An alternative is to create a new DB with a schema that covers everything from both databases, but this may not be possible or desirable.
You can also search about "data migration" for more info.
edited Nov 12 at 6:00
answered Nov 12 at 5:54
Ryan
469615
469615
1
Best thank @Ryan, that's exactly what I'm looking for.
– BIZ
Nov 12 at 7:42
add a comment |
1
Best thank @Ryan, that's exactly what I'm looking for.
– BIZ
Nov 12 at 7:42
1
1
Best thank @Ryan, that's exactly what I'm looking for.
– BIZ
Nov 12 at 7:42
Best thank @Ryan, that's exactly what I'm looking for.
– BIZ
Nov 12 at 7:42
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53255456%2fhow-to-merge-2-duplicated-database-entry-to-1-database-after-ma%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown