Source of Statements about 19 Appendix - Databases or Flat file Data stores (without imported statements)
Properties
History
Community
Source
You have no permissions to edit this model.
Saving has been disabled.
# Exported with the Erfurt API - http://aksw.org/Projects/Erfurt @base <http://www.archimind.nl/archimindLOD/index.php/view/r/> . @prefix dct: <http://purl.org/dc/terms/> . @prefix ns0: <http://archimind.nl/archimind/index.php/view/> . @prefix ns1: <http://www.archimind.nl/archimind/index.php/resource/properties/> . @prefix ns2: <http://www.archimind.nl/archimind/index.php/> . @prefix ns3: <http://www.archimind.nl/archimindLOD/index.php/view/r/> . @prefix ontology1288790966584: <http://www.semanticweb.org/ontologies/2010/10/Ontology1288790966584.owl#> . @prefix ontowiki_wikipage: <http://localhost/ontowiki_WikiPage/> . @prefix owl2xml: <http://www.w3.org/2006/12/owl2-xml#> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix sadocontology1: <http://www.archimind.nl/archimindLOD/index.php/view/r/sadocontology1.owl:> . @prefix sioc: <http://rdfs.org/sioc/ns#> . @prefix sioct: <http://rdfs.org/sioc/types#> . @prefix sysconf: <http://localhost/OntoWiki/Config/> . @prefix uva-sa-ontology: <http://www.archimind.org/archimind/UvA-SA-ontology.owl#> . @prefix view: <http://localhost/ontowiki/view/> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . <http://www.archimind.nl/archimindLOD/index.php/view/r/sadocontology1.owl:19_Appendix_-_Databases_or_Flat_file_Data_stores> ontowiki_wikipage:content """<h1> Appendix A</h1> <p> </p> <h2> Databases or Flat file Data stores:</h2> <p> The data collector needs to temporary stores his extracted data, to provide them to the SNA component. The data collector can accomplish that in two ways, store them in a database or in separate flat file formats, like xml, CSV or an own simple data structure.</p> <p> </p> <p> Advantages between the types of data stores systems:</p> <table border=\"1\" cellpadding=\"0\" cellspacing=\"0\"> <tbody> <tr> <td colspan=\"2\" style=\"width:281px;\"> <p> Database</p> </td> <td colspan=\"2\" style=\"width:281px;\"> <p> Flat file</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Advantage</p> </td> <td style=\"width:151px;\"> <p> Description</p> </td> <td style=\"width:104px;\"> <p> Advantage</p> </td> <td style=\"width:177px;\"> <p> Description</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Multi access, read & write</p> </td> <td style=\"width:151px;\"> <p> Multithreaded read and write access, managed by the database system.</p> </td> <td style=\"width:104px;\"> <p> No extra costs, except space</p> </td> <td style=\"width:177px;\"> <p> The flat files could be stored at the server hard disk.</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Transaction save</p> </td> <td style=\"width:151px;\"> <p> Data stay consistent through several writes in the same table.</p> </td> <td style=\"width:104px;\"> <p> No access lib’s</p> </td> <td style=\"width:177px;\"> <p> Every common programming language provides native.</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Relation between data</p> </td> <td style=\"width:151px;\"> <p> Relations can be queried, for example with the LDAP User ID.</p> </td> <td style=\"width:104px;\"> <p> -</p> </td> <td style=\"width:177px;\"> <p> -</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Optimized data storing</p> </td> <td style=\"width:151px;\"> <p> Optimized data storage in a relational way.</p> </td> <td style=\"width:104px;\"> <p> -</p> </td> <td style=\"width:177px;\"> <p> -</p> </td> </tr> </tbody> </table> <p> </p> <p> Disadvantages between the types of data stores systems:</p> <table border=\"1\" cellpadding=\"0\" cellspacing=\"0\"> <tbody> <tr> <td colspan=\"2\" style=\"width:272px;\"> <p> Database</p> </td> <td colspan=\"2\" style=\"width:296px;\"> <p> Flat file</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Disadvantage</p> </td> <td style=\"width:142px;\"> <p> Description</p> </td> <td style=\"width:123px;\"> <p> Disadvantage</p> </td> <td style=\"width:173px;\"> <p> Description</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Extra costs</p> </td> <td style=\"width:142px;\"> <p> In administration and hardware.</p> </td> <td style=\"width:123px;\"> <p> Single access, write</p> </td> <td style=\"width:173px;\"> <p> Only on thread can read and write. – in Performance.</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Extra connector lib’s needed</p> </td> <td style=\"width:142px;\"> <p> The disadvantages here are extra costs for commercial database connection libraries, but this only if commercial databases are used, for open source, it’s not a disadvantage.</p> </td> <td style=\"width:123px;\"> <p> Bottleneck</p> </td> <td style=\"width:173px;\"> <p> The Flat files create a bottleneck in focus on performance, because only one single thread could read and write at a time. For a more performance based read and writing service Flat files not very suited.</p> </td> </tr> </tbody> </table> <p> </p> <br clear=\"all\" /> <p> </p> <p> </p> <p> <strong>Conclusion:</strong></p> <p> As to see from the table, beside the extra costs compared with a flat file data store structure are only advantages to use an database system for the data collector component to store his transformed data.</p> <p> </p> <p> <strong>Decision:</strong></p> <p> The decision is based on the conclusion made before. The systems data collector component needs a Database system to store the raw data in a small, simple database table. A Database system brings more flexibility, security (Transaction save), data integrity, performance then a flat file structured data store.</p>""" ; sadocontology1:contains_knowledge_about sadocontology1:Business_rules_engine, sadocontology1:Cost, sadocontology1:Data_integrity, sadocontology1:Extractor, sadocontology1:Flexibility, sadocontology1:Performance ; a sadocontology1:WikiPage, owl:NamedIndividual ; rdfs:label "19 Appendix - Databases or Flat file Data stores" .
# Exported with the Erfurt API - http://aksw.org/Projects/Erfurt @base <http://www.archimind.nl/archimindLOD/index.php/view/r/> . @prefix dct: <http://purl.org/dc/terms/> . @prefix ns0: <http://archimind.nl/archimind/index.php/view/> . @prefix ns1: <http://www.archimind.nl/archimind/index.php/resource/properties/> . @prefix ns2: <http://www.archimind.nl/archimind/index.php/> . @prefix ns3: <http://www.archimind.nl/archimindLOD/index.php/view/r/> . @prefix ontology1288790966584: <http://www.semanticweb.org/ontologies/2010/10/Ontology1288790966584.owl#> . @prefix ontowiki_wikipage: <http://localhost/ontowiki_WikiPage/> . @prefix owl2xml: <http://www.w3.org/2006/12/owl2-xml#> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix sadocontology1: <http://www.archimind.nl/archimindLOD/index.php/view/r/sadocontology1.owl:> . @prefix sioc: <http://rdfs.org/sioc/ns#> . @prefix sioct: <http://rdfs.org/sioc/types#> . @prefix sysconf: <http://localhost/OntoWiki/Config/> . @prefix uva-sa-ontology: <http://www.archimind.org/archimind/UvA-SA-ontology.owl#> . @prefix view: <http://localhost/ontowiki/view/> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . <http://www.archimind.nl/archimindLOD/index.php/view/r/sadocontology1.owl:19_Appendix_-_Databases_or_Flat_file_Data_stores> ontowiki_wikipage:content """<h1> Appendix A</h1> <p> </p> <h2> Databases or Flat file Data stores:</h2> <p> The data collector needs to temporary stores his extracted data, to provide them to the SNA component. The data collector can accomplish that in two ways, store them in a database or in separate flat file formats, like xml, CSV or an own simple data structure.</p> <p> </p> <p> Advantages between the types of data stores systems:</p> <table border=\"1\" cellpadding=\"0\" cellspacing=\"0\"> <tbody> <tr> <td colspan=\"2\" style=\"width:281px;\"> <p> Database</p> </td> <td colspan=\"2\" style=\"width:281px;\"> <p> Flat file</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Advantage</p> </td> <td style=\"width:151px;\"> <p> Description</p> </td> <td style=\"width:104px;\"> <p> Advantage</p> </td> <td style=\"width:177px;\"> <p> Description</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Multi access, read & write</p> </td> <td style=\"width:151px;\"> <p> Multithreaded read and write access, managed by the database system.</p> </td> <td style=\"width:104px;\"> <p> No extra costs, except space</p> </td> <td style=\"width:177px;\"> <p> The flat files could be stored at the server hard disk.</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Transaction save</p> </td> <td style=\"width:151px;\"> <p> Data stay consistent through several writes in the same table.</p> </td> <td style=\"width:104px;\"> <p> No access lib’s</p> </td> <td style=\"width:177px;\"> <p> Every common programming language provides native.</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Relation between data</p> </td> <td style=\"width:151px;\"> <p> Relations can be queried, for example with the LDAP User ID.</p> </td> <td style=\"width:104px;\"> <p> -</p> </td> <td style=\"width:177px;\"> <p> -</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Optimized data storing</p> </td> <td style=\"width:151px;\"> <p> Optimized data storage in a relational way.</p> </td> <td style=\"width:104px;\"> <p> -</p> </td> <td style=\"width:177px;\"> <p> -</p> </td> </tr> </tbody> </table> <p> </p> <p> Disadvantages between the types of data stores systems:</p> <table border=\"1\" cellpadding=\"0\" cellspacing=\"0\"> <tbody> <tr> <td colspan=\"2\" style=\"width:272px;\"> <p> Database</p> </td> <td colspan=\"2\" style=\"width:296px;\"> <p> Flat file</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Disadvantage</p> </td> <td style=\"width:142px;\"> <p> Description</p> </td> <td style=\"width:123px;\"> <p> Disadvantage</p> </td> <td style=\"width:173px;\"> <p> Description</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Extra costs</p> </td> <td style=\"width:142px;\"> <p> In administration and hardware.</p> </td> <td style=\"width:123px;\"> <p> Single access, write</p> </td> <td style=\"width:173px;\"> <p> Only on thread can read and write. – in Performance.</p> </td> </tr> <tr> <td style=\"width:130px;\"> <p> Extra connector lib’s needed</p> </td> <td style=\"width:142px;\"> <p> The disadvantages here are extra costs for commercial database connection libraries, but this only if commercial databases are used, for open source, it’s not a disadvantage.</p> </td> <td style=\"width:123px;\"> <p> Bottleneck</p> </td> <td style=\"width:173px;\"> <p> The Flat files create a bottleneck in focus on performance, because only one single thread could read and write at a time. For a more performance based read and writing service Flat files not very suited.</p> </td> </tr> </tbody> </table> <p> </p> <br clear=\"all\" /> <p> </p> <p> </p> <p> <strong>Conclusion:</strong></p> <p> As to see from the table, beside the extra costs compared with a flat file data store structure are only advantages to use an database system for the data collector component to store his transformed data.</p> <p> </p> <p> <strong>Decision:</strong></p> <p> The decision is based on the conclusion made before. The systems data collector component needs a Database system to store the raw data in a small, simple database table. A Database system brings more flexibility, security (Transaction save), data integrity, performance then a flat file structured data store.</p>""" ; sadocontology1:contains_knowledge_about sadocontology1:Business_rules_engine, sadocontology1:Cost, sadocontology1:Data_integrity, sadocontology1:Extractor, sadocontology1:Flexibility, sadocontology1:Performance ; a sadocontology1:WikiPage, owl:NamedIndividual ; rdfs:label "19 Appendix - Databases or Flat file Data stores" .
OntoWiki
Search for Resources
User
Register New User
Extras
SPARQL Query Editor
News
Help
Documentation
Bug Report
Version Info
About
Knowledge Bases
Architecture Knowledge Domain Ontology
View
Show Hidden Knowledge Bases
Navigation
Search in Navigation
View
Number of Elements
10
20
30
Toggle Elements
Hidden Elements
Empty Elements
Implicit Elements
Reset Navigation
Type
Classes
Properties
SKOS
Groups
Login
Local
OpenID
FOAF+SSL
Username
Password
Remember me
Login
Register
OpenID
Login
Register
Login
Register