We help IT Professionals succeed at work.

DocumentDB

dear all,

I am reading this:

http://azure.microsoft.com/blog/2015/04/08/nosql-database-service-azure-documentdb-now-generally-available/

What is DocumentDB for ? only as a purpose on allowing applications to query and process JSON data at scale ? and it is delivered as a fully managed database-as-a-service (DBaaS) with built in high availability, SQL query over indexed JSON and multi-document
transaction processing.
?

what good is noSQL when compare with tranditional SQL ?

did DocumentDB compliance with ACID and SQL compliance ? it should not be as it is not tranditional SQL, like MS SQL, Oralce and DB2 ?
Comment
Watch Question

Éric MoreauSenior .Net Consultant
Top Expert 2016

Commented:
DocumentDB is the Microsoft version of NoSQL. You don't define schemas for your table, you just store data into your Documents.

For example, OneNote has been storing your data in DocumentDB for a long time (Microsoft tested that technology over the last few years).

Document DB can be queried with Rest calls.
marrowyungSenior Technical architecture (Data)

Author

Commented:
"DocumentDB is the Microsoft version of NoSQL. You don't define schemas for your table, you just store data into your Documents.
"

excellent! this can save a lot of time ! but is that mean no more data modelling design is needed ?

"For example, OneNote has been storing your data in DocumentDB for a long time (Microsoft tested that technology over the last few years).
"

tks, but how can you know it? your can check out version ?

so with the DocumentDB migration tools, we can just upload and run ?
marrowyungSenior Technical architecture (Data)

Author

Commented:
is the exchange notes item is one example of DocumentDB? no need structure, right? just a notes there.
Senior .Net Consultant
Top Expert 2016
Commented:
>> no more data modelling design is needed ?

If you have a need to store relational data, continue to use SQL Server or one of its competitor. If you have data for which there is not a known schema, then you should use a NoSQL solution. If you find yourself storing big string or XML data in a regular database, or if you have tables with many fields but most are NULLs, this is a good sign that it is not the best solution. Reporting and querying from a NoSQL solution is really not easy.

>>but how can you know it?

I have seen it at a Microsoft presentation and it could be read from http://www.eweek.com/cloud/microsoft-raises-limits-on-nosql-documentdb-cloud-service.html
Users of Microsoft's cloud-enabled note-taking app, OneNote, have already been leveraging the tech, likely without knowing it, to store, sync and share their content. "Microsoft consumer applications like OneNote already use DocumentDB in production to support millions of users," claims the company on the DocumentDB website.

As for Exchange, I don't know.
marrowyungSenior Technical architecture (Data)

Author

Commented:
"If you find yourself storing big string or XML data in a regular database, or if you have tables with many fields but most are NULLs, this is a good sign that it is not the best solution"

you mean in this case go to the relational data side, which is SQL server,etc?

"Reporting and querying from a NoSQL solution is really not easy.
"

so this DocumentDB is the solution for us to manage the noSQL well, right?
Éric MoreauSenior .Net Consultant
Top Expert 2016
Commented:
>>you mean in this case go to the relational data side, which is SQL server,etc?

No, if you store big XML data into a relational database, it is often a sign that a NoSQL solution would better fit your storage requirements.

>>so this DocumentDB is the solution for us to manage the noSQL well, right?

DocumentDB is the Microsoft version of NoSQL. Competitors have other names like MongoDB.

Have a look at http://en.wikipedia.org/wiki/NoSQL