DocumentDB Sequential record import (partitioned collection) – The DocumentDB sequential record importer allows you to import from any of the available source options on a record by record basis. You might choose this option if you’re importing to an existing collection that has reached its quota of stored procedures. This importer always uses serverside partitioning. Read more about partitioning data in DocumentDB . The format of the DocumentDB connection string is: AccountEndpoint=<DocumentDB Endpoint>;AccountKey=<DocumentDB Key>;Database=<DocumentDB Database>; Tip: Use the Verify command to ensure that the DocumentDB instance specified in the connection string can be accessed. To import to a collection, enter the name of the collection to which data will be imported. When importing to a collection, DocumentDB supports server-side hash sharding. In this scenario, specify the document property you wish to use as the Partition Key. The collection throughput allows you to specify desired throughput of the collection in Request (RUs). Tip: The collection throughput setting only applies to collection creation. If the specified collection already exists, its throughput will not be modified. You may optionally specify which field in the import source should be used as the DocumentDB document id property during the import (note that if documents do not contain this property, then the import tool will generate a GUID as the id property value). You may optionally specify which field in the import source should be used as the DocumentDB document id property during the import (note that if documents do not contain this property, then the import tool will generate a GUID as the id property value): There are number of advanced options available during import. First, when importing date types (e.g. from SQL Server or MongoDB), you can choose between three import options: String: persist as a string value Epoch: persist as an Epoch number value Both: Persist both string and Epoch number values. This option will create a subdocument, for example: "date_joined": {
DocumentDB – Sequential record import (partitioned collection) The DocumentDB sequential record importer allows you to import from any of the available source options on a record by record basis. You might choose this option if you’re importing to an existing collection that has reached its quota of stored procedures. This importer always uses serverside partitioning. Read more about partitioning data in DocumentDB . The format of the DocumentDB connection string is: AccountEndpoint=<DocumentDB Endpoint>;AccountKey=<DocumentDB Key>;Database=<DocumentDB Database>; Tip: Use the Verify command to ensure that the DocumentDB instance specified in the connection string can be accessed. To import to a collection, enter the name of the collection to which data will be imported. When importing to a collection, DocumentDB supports server-side hash sharding. In this scenario, specify the document property you wish to use as the Partition Key. The collection throughput allows you to specify desired throughput of the collection in Request (RUs). Tip: The collection throughput setting only applies to collection creation. If the specified collection already exists, its throughput will not be modified. You may optionally specify which field in the import source should be used as the DocumentDB document id property during the import (note that if documents do not contain this property, then the import tool will generate a GUID as the id property value). You may optionally specify which field in the import source should be used as the DocumentDB document id property during the import (note that if documents do not contain this property, then the import tool will generate a GUID as the id property value): There are number of advanced options available during import. First, when importing date types (e.g. from SQL Server or MongoDB), you can choose between three import options: String: persist as a string value Epoch: persist as an Epoch number value Both: Persist both string and Epoch number values. This option will create a subdocument, for example: "date_joined": {
DocumentDB%20Data%20Migration%20Tool%20v1.7.docx