Mixing
Migration from Access to DynamoDB
I am trying to migrate 3,000,000 records from Microsoft Access to DynamoDB. I am trying to/ cannot find any information on how to most efficiently convert from a relational database to a NoSQL db. Does anyone have a method? Thanks!
amazon-web-services nosql access migrate
asked Jan 3 at 1:29
CraigCraig
767
add a comment |
I am trying to migrate 3,000,000 records from Microsoft Access to DynamoDB. I am trying to/ cannot find any information on how to most efficiently convert from a relational database to a NoSQL db. Does anyone have a method? Thanks!
amazon-web-services nosql access migrate
asked Jan 3 at 1:29
CraigCraig
767
add a comment |
I am trying to migrate 3,000,000 records from Microsoft Access to DynamoDB. I am trying to/ cannot find any information on how to most efficiently convert from a relational database to a NoSQL db. Does anyone have a method? Thanks!
amazon-web-services nosql access migrate
asked Jan 3 at 1:29
CraigCraig
767
I am trying to migrate 3,000,000 records from Microsoft Access to DynamoDB. I am trying to/ cannot find any information on how to most efficiently convert from a relational database to a NoSQL db. Does anyone have a method? Thanks!
amazon-web-services nosql access migrate
amazon-web-services nosql access migrate
asked Jan 3 at 1:29
CraigCraig
767
asked Jan 3 at 1:29
CraigCraig
767
asked Jan 3 at 1:29
CraigCraig
767
asked Jan 3 at 1:29
CraigCraig
767
asked Jan 3 at 1:29
CraigCraig
767
767
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
There is nothing inherently different between converting from Access to DynamoDB or from SQL server (or any other relational, b-tree indexed database, for that matter). One thing I can say is, if you have 3 million rows, you want to know that what you are doing is the right thing. NoSQL is very nice, when you have the right use case for it. It downright sucks if you are trying to accomplish something better done through relational data. I don't know your case so I don't have an opinion, but you may want to examine your decision to migrate. There are cloud-based relational database services.
Consult Amazon's documentation at https://aws.amazon.com/blogs/database/aws-database-migration-service-and-amazon-dynamodb-what-you-need-to-know/ for information on how to get the migration accomplished.
Beyond that, my approach would be:
A) Use SQL server integration services to extract the table into a SQL instance,
B) upload the data to an Azure instance,
C) Use the amazon database migration service to transfer into DynamoDB.
Your main pitfalls are going to be String encoding, date formats and BLOB/CLOBS. If you have any of the latter, I would suggest writing a short program to handle them separately. Encoding pages can and should be synchronized. Dates are best transferred in the international YYYY-MM-DD hh:mm:ss format.
answered Jan 3 at 3:03
Philippe DamervalPhilippe Damerval
614
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%2f54015262%2fmigration-from-access-to-dynamodb%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
There is nothing inherently different between converting from Access to DynamoDB or from SQL server (or any other relational, b-tree indexed database, for that matter). One thing I can say is, if you have 3 million rows, you want to know that what you are doing is the right thing. NoSQL is very nice, when you have the right use case for it. It downright sucks if you are trying to accomplish something better done through relational data. I don't know your case so I don't have an opinion, but you may want to examine your decision to migrate. There are cloud-based relational database services.
Consult Amazon's documentation at https://aws.amazon.com/blogs/database/aws-database-migration-service-and-amazon-dynamodb-what-you-need-to-know/ for information on how to get the migration accomplished.
Beyond that, my approach would be:
A) Use SQL server integration services to extract the table into a SQL instance,
B) upload the data to an Azure instance,
C) Use the amazon database migration service to transfer into DynamoDB.
Your main pitfalls are going to be String encoding, date formats and BLOB/CLOBS. If you have any of the latter, I would suggest writing a short program to handle them separately. Encoding pages can and should be synchronized. Dates are best transferred in the international YYYY-MM-DD hh:mm:ss format.
answered Jan 3 at 3:03
Philippe DamervalPhilippe Damerval
614
add a comment |
There is nothing inherently different between converting from Access to DynamoDB or from SQL server (or any other relational, b-tree indexed database, for that matter). One thing I can say is, if you have 3 million rows, you want to know that what you are doing is the right thing. NoSQL is very nice, when you have the right use case for it. It downright sucks if you are trying to accomplish something better done through relational data. I don't know your case so I don't have an opinion, but you may want to examine your decision to migrate. There are cloud-based relational database services.
Consult Amazon's documentation at https://aws.amazon.com/blogs/database/aws-database-migration-service-and-amazon-dynamodb-what-you-need-to-know/ for information on how to get the migration accomplished.
Beyond that, my approach would be:
A) Use SQL server integration services to extract the table into a SQL instance,
B) upload the data to an Azure instance,
C) Use the amazon database migration service to transfer into DynamoDB.
Your main pitfalls are going to be String encoding, date formats and BLOB/CLOBS. If you have any of the latter, I would suggest writing a short program to handle them separately. Encoding pages can and should be synchronized. Dates are best transferred in the international YYYY-MM-DD hh:mm:ss format.
answered Jan 3 at 3:03
Philippe DamervalPhilippe Damerval
614
add a comment |
There is nothing inherently different between converting from Access to DynamoDB or from SQL server (or any other relational, b-tree indexed database, for that matter). One thing I can say is, if you have 3 million rows, you want to know that what you are doing is the right thing. NoSQL is very nice, when you have the right use case for it. It downright sucks if you are trying to accomplish something better done through relational data. I don't know your case so I don't have an opinion, but you may want to examine your decision to migrate. There are cloud-based relational database services.
Consult Amazon's documentation at https://aws.amazon.com/blogs/database/aws-database-migration-service-and-amazon-dynamodb-what-you-need-to-know/ for information on how to get the migration accomplished.
Beyond that, my approach would be:
A) Use SQL server integration services to extract the table into a SQL instance,
B) upload the data to an Azure instance,
C) Use the amazon database migration service to transfer into DynamoDB.
Your main pitfalls are going to be String encoding, date formats and BLOB/CLOBS. If you have any of the latter, I would suggest writing a short program to handle them separately. Encoding pages can and should be synchronized. Dates are best transferred in the international YYYY-MM-DD hh:mm:ss format.
answered Jan 3 at 3:03
Philippe DamervalPhilippe Damerval
614
There is nothing inherently different between converting from Access to DynamoDB or from SQL server (or any other relational, b-tree indexed database, for that matter). One thing I can say is, if you have 3 million rows, you want to know that what you are doing is the right thing. NoSQL is very nice, when you have the right use case for it. It downright sucks if you are trying to accomplish something better done through relational data. I don't know your case so I don't have an opinion, but you may want to examine your decision to migrate. There are cloud-based relational database services.
Consult Amazon's documentation at https://aws.amazon.com/blogs/database/aws-database-migration-service-and-amazon-dynamodb-what-you-need-to-know/ for information on how to get the migration accomplished.
Beyond that, my approach would be:
A) Use SQL server integration services to extract the table into a SQL instance,
B) upload the data to an Azure instance,
C) Use the amazon database migration service to transfer into DynamoDB.
Your main pitfalls are going to be String encoding, date formats and BLOB/CLOBS. If you have any of the latter, I would suggest writing a short program to handle them separately. Encoding pages can and should be synchronized. Dates are best transferred in the international YYYY-MM-DD hh:mm:ss format.
answered Jan 3 at 3:03
Philippe DamervalPhilippe Damerval
614
answered Jan 3 at 3:03
Philippe DamervalPhilippe Damerval
614
answered Jan 3 at 3:03
Philippe DamervalPhilippe Damerval
614
answered Jan 3 at 3:03
Philippe DamervalPhilippe Damerval
614
614
add a comment |
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.
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%2f54015262%2fmigration-from-access-to-dynamodb%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
