Databases
StackOverflow2013
Postsdbo
POusing couch db and sql server side by side
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POusing couch db and sql server side by side
    text
    copied!<p>We currently have a nicely relational sql server 2008 database that is our master application database. We are looking to improve an existing document storage mechanism which uses xml data types with something more schemaless that can handle similar but not identical documents and thought that couchdb would be good fit. </p> <p>The idea is that the common meta data about the documents could be stored within sql server for ease of display/aggregation/reporting but the actual documents are stored in couch to handle the subtle differences in the documents. The idea is to make the most of the two different technologies.</p> <p>For example the status, type, related person and date created would all be common across all documents and stored in sql but an email and a letter (obviously with different fields) could be stored in couch.</p> <p>Then we can display our document grid for all types of document (thousands of docs) which can be queried through sql but the display of the doc gets its data from couch when the user requests to view it.</p> <p>Something to bear in mind is that some document types are generated from templates that are also documents themselves (think mail merge/find and replace).</p> <p>Application layer is asp.net 4.5, c#, repository pattern, Windsor for ioc, JavaScript</p> <p>So, to the question...</p> <p>Is this approach a sensible way to make the most of the two differing data storage paradigms?</p> <p>Are we making our programming lives needlessly complex in the desire to "use the most appropriate technology for the problem"?</p> <p>Does anyone have any experiences of trying something similar and if so, how did it go?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload