Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well, specifically with regards to Couch and Mongo, the first issue you will have to deal with is converting the SOAP XML payload in some relevant JSON payload, since that's what these DBs understand.</p> <p>Next, most of these DBs require you to have a good understanding of what queries you want to make from them up front, during initial design, and ideally before you start loading data in to them. Adding new indexes can be expensive for existing data sets, particularly large ones.</p> <p>It's all very doable, but you want to get out of your head any concept of an "ad hoc" query like in an RDBMS. They simply don't typically perform well in NoSQL systems.</p> <p>Finally, since you have to convert the data from XML to JSON already, you may well be better off extracting the "interesting fields" from your SOAP requests, the ones you want to query on, and simply populate your own index fields and rows and store the data in your (I assume) already existing SQL database.</p> <p>Edit for comment:</p> <p>It's not transparent to you, the users, because the burden of conversion to JSON falls upon you, since the two DBs mentioned require a JSON document to be passed to them.</p> <p>That said, you could simply extract the few bits you care about rather than marshall the entire document. You would have to marshall everything you're interested in, including for filtering, in that case.</p> <p>So, you can create a document: </p> <pre><code>{ "user":"Bob", "methodName" : "helloWorld", "soapDate" : "2010-09-01 12:23:45", "soapRequest" : "...escaped XML goes here..." } </code></pre> <p>Then you could build views or indexes off of anything exposed within the JSON document. You won't be able to (easily) query anything from within the raw SOAP request. Only elements you specifically extract and put in to the JSON payload will you be able to access readily through the DB.</p> <p>My basic point is, tho, that if you have to go through any marshalling process to convert your data and make it ready for the database, then you likely may as well use a database you already know and is supported at your company (i.e. likely your existing RDBMS) rather than introduce another brick in to your stack by adding a new DB.</p> <p>If you were already native JSON, or, say, found a NoSQL-esque DB that supported native XML vs JSON, then that might be worthwhile since you can skip that part of the process.</p> <p>But you can easily create a table (or tables) to handle this data in most any modern RDBMS.</p>
    singulars
    1. This table or related slice is empty.
    1. PONoSql for saving SOAP requests to DB for audit logging - and then querying?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USWill Hartung
    1. USWill Hartung
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PONoSql for saving SOAP requests to DB for audit logging - and then querying?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COI guess the XML to JSON conversion could be done transparently? In most cases I think I'd be fine with an index on: user, WS method name, soap-requestDate. Any other field would probably not be indexed (although I would do some filtering on them). As it is for auditing purposes only, it wouldn't have to be lightning fast. Only reasonable
      singulars
      1. PO
      1. USAtliB
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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