OrientDB Distributed Graph Database http://orientdb.com OrientDB is a Multi-Model NoSQL Database with a true Graph engine Thu, 26 May 2016 19:00:23 +0000 en-US hourly 1 Released OrientDB 2.1.18 http://orientdb.com/released-orientdb-2-1-18/ http://orientdb.com/released-orientdb-2-1-18/#comments Wed, 25 May 2016 12:34:42 +0000 http://orientdb.com/?p=14434 London, May 25, 2016 The OrientDB Team has just released OrientDB v2.1.18, resolving 26 issues from v2.1.17. This is the last stable release. Please […]

The post Released OrientDB 2.1.18 appeared first on OrientDB Distributed Graph Database.

]]>
London, May 25, 2016

The OrientDB Team has just released OrientDB v2.1.18, resolving 26 issues from v2.1.17. This is the last stable release. Please upgrade your production environments to v2.1.18. For more information, take a look at the Change Log.

Download OrientDB v2.1.18 now: http://orientdb.com/download

As you know v 2.2 GA is out, with many additional fixes, enhanced security and a lot of new features, so we strongly suggest you to upgrade.

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

The post Released OrientDB 2.1.18 appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/released-orientdb-2-1-18/feed/ 0
Let’s Talk about OrientDB Stability, Code Coverage and Bugs http://orientdb.com/orientdb-stability-bugs-benchmark/ http://orientdb.com/orientdb-stability-bugs-benchmark/#comments Mon, 23 May 2016 16:31:20 +0000 http://orientdb.com/?p=14092 After 11 months of development and QA testing, we’re thrilled to finally release Production-Ready OrientDB v2.2 GA!   We’ve worked day and night to […]

The post Let’s Talk about OrientDB Stability, Code Coverage and Bugs appeared first on OrientDB Distributed Graph Database.

]]>
After 11 months of development and QA testing, we’re thrilled to finally release Production-Ready OrientDB v2.2 GA!

 

We’ve worked day and night to provide our users with tremendous performance improvements. Users are reporting from 2 to 10 times the performance! We increased security so much (encryption at rest, password salt, Kerberos support, etc.) that as of date, there is no other NoSQL DBMS on the market that is more secure (More to come on that, as a global top tier bank has chosen to partner with OrientDB as their NoSQL DBMS of choice and has helped us to improve our security even further!). Finally, we added new features we knew our users would be excited about: like the Incremental Backup, Load Balancing, Command Cache, Parallel Queries, Sequences, Reactive Live Query, Pattern Matching, Teleporter and much more.

In this period, we fixed about 2,000 issues and increased the code coverage by +11 points (from 55% to 66% of covered lines as we speak), even though the actual code base grew:

jacoco

How does code coverage work?

OrientDB decided to make this test code coverage report publicly accessible to offer our users complete transparency. Want to take a look at our competitors’ code coverage to compare? I’m unable to find any that actually publish their code coverage, but please send me the links if you’re able to find that info.

Even though we already have more than 3,850 test cases, we’re constantly working to improve the quality of OrientDB by adding more and more test cases. Do you want to contribute? Help improve OrientDB’s test coverage by sending in your test cases.

Why is the average coverage so far below 100%?

These are some factors to consider that impact the average:

  • The core engine has excellent coverage, however other components such as the HTTP API have less coverage. This brings the average down.
  • There are components needed for older OrientDB version compatibility that are not well covered by test cases. This brings the average down, but they are never used by the last version of OrientDB.
  • There are experimental components of OrientDB (not even documented yet) that have not reached maturity. They usually have few or no test cases. Many times, we stop development on them before the first RC. This also brings the average down.

What about our Open Bugs?

Today we have 343 open bugs. Too many, right? A DBMS should be reliable. How can I trust a software with so many issues? Well it’s a bit more complex than that.

A young player in the DBMS space could seem like a better product due to their low number of bugs. Or a simple product that handles a few use cases can seem like they have less issues compared to one that is more complex. However, the more people that use a DBMS and the more complex the functionality and number of possible use cases, the more bugs it will have. Let’s take a look at other DBMS projects. (Click on the DBMS name to check the issues.)

OrientDB Cassandra MongoDB CouchBase MariaDB MySQL Neo4j

OrientDB is way below the average. Comparing our 343 bugs with 5,252 of MySQL means we have only 6% of their amount. For Postgres, it seems that they don’t have a public issue tracker, because they handle all the bugs via email, so I’m not able to provide any number for them.

So from this analysis, is MySQL the most buggy and unstable database on the market? I’m sure you can agree that’s not the case. It’s still the most popular DBMS in the world with hundreds of thousands of users and thousands of applications and websites that are running on it.

There is no perfect software. Any complex, highly-used software like OrientDB will always have bugs due to its complexity, vast range of use cases and the thousands of users around the globe that open issues. Also, please keep in mind that OrientDB is a pure multi-model DBMS with much more functionality/capabilities than the leading document, graph and relational NoSQL DBMSs combined. When you look at it that way, our bug numbers are actually quite low. Finally, while our competitors usually take a couple of years to follow in our path in regards to features, by then we’ve already ironed out the issues in OrientDB, maintaining our lead ahead of the DBMS market and solidifying our promise to our users that OrientDB will always be cutting-edge technology.

What else is OrientDB doing to improve quality?

Are we satisfied with the amount of OrientDB bugs? Absolutely not. That’s why we continue to work hard to bring this number down to as close to zero as possible and why we are constantly improving and increasing our QA tests and documentation.

Now that OrientDB 2.2 GA is available, our Development Team has stopped development on further versions (apart from the current work packaging the OrientDB Enterprise Edition v2.2 that will be released shortly) and will spend the next month heads-down resolving issues, bugs, etc. So, if you have any problems, please send those in asap.

I’ll keep you posted about our results on this and for any questions, please don’t hesitate to write to our Open Community where more than 3,000 passionate users work together to improve OrientDB everyday.

If you have any additional questions or would like to receive more information go ahead and contact us.

Best Regards,

Luca Garulli

Founder & CEO
OrientDB Ltd

The post Let’s Talk about OrientDB Stability, Code Coverage and Bugs appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/orientdb-stability-bugs-benchmark/feed/ 0
OrientDB v2.2 GA – Improved Security, Performance, Operations & APIs http://orientdb.com/released-orientdb-v2-2/ http://orientdb.com/released-orientdb-v2-2/#comments Wed, 18 May 2016 13:10:26 +0000 http://orientdb.com/?p=14104 Most of you have downloaded it, tested it and seen what it’s capable of. Now the wait is finally over!   After 11 months […]

The post OrientDB v2.2 GA – Improved Security, Performance, Operations & APIs appeared first on OrientDB Distributed Graph Database.

]]>
Most of you have downloaded it, tested it and seen what it’s capable of. Now the wait is finally over!

 

After 11 months of development and QA testing, we’re thrilled to finally announce that the GA release of OrientDB 2.2 Community Edition is now available for download! We couldn’t be more excited to make this announcement as OrientDB 2.2 stands out as one of the most secure and reliable DBMS systems on the market to date. With the help of a dedicated and brilliant development community, we’ve created an open source powerhouse which proves that multi-model systems are not only here to stay, but that they’re quickly becoming the new NoSQL DBMS standard.

OrientDB 2.2 is packed full of new features (I’m sure you’ve all heard of Teleporter), though the main focus for this release was to strengthen security and improve stability & performance. We’ve optimized our core engine, worked hard on correcting bugs present in previous versions and made our system more user-friendly. With Teleporter, we’ve made it easy for you to say goodbye to your old relational database and OrientDB studio provides a powerful, yet straight-forward, web interface.  Whether you’re using OrientDB for commercial purposes or taking your first steps working with graphs, OrientDB v2.2 will not disappoint!

So take a look at some of the new features in OrientDB’s latest version and don’t forget to sign up for our webinar on June 1st (details below).

OrientDB v2.2

Security

Your precious data is safe! Security for us is paramount as customers are storing their valuable, critical and confidential data in OrientDB. With improved auditing and authentication, password salt and data-at-rest encryption, Kerberos support and more, OrientDB is one of the most secure DBMS on the market.

Performance & Stability

OrientDB 2.2 is fast! We’ve done multiple optimizations to the core engine and, in many cases, performance increased tenfold! Our distributed capabilities are also constantly improving and we’ve introduced fast-resync of nodes. OrientDB supports the new configurable Graph Consistency to speed-up change operations against graphs.

Operations

Looking for Incremental Backups? We’ve got that covered. What’s more, with OrientDB’s latest 2.2 version, the new OrientDB Studio (a workbench replacement) adds a new peer-to-peer architecture and new modules. We’ve also officially released Teleporter: a new tool to sync with relational databases and simplify migrations to OrientDB.

APIs

“SQL is the English of databases” and we’re constantly improving our SQL access layer to simplify graph operations. New additions include Pattern Matching, Command Cache, Parallel Queries and Live Query graduating from experimental to stable. Also OrientJS, the official Node driver, now supports native unmarshalling.

Don’t Miss our Webinar!

Want to find out more about OrientDB 2.2 and all its new features? Sign up for our June 1st webinar where I will be talking about our latest release and answering your questions.  All of us here at OrientDB would love to hear your opinions and this is the perfect opportunity to engage with you directly. The webinar will take place at 5pm GMT+1 on June 1st so if you’d like to join us, go ahead and sign up here.

For those of you not willing to make the jump to OrientDB 2.2 just yet (though we strongly recommend you do!), not to worry, support for OrientDB 2.1 will go ahead as usual with regular updates being provided along with support. Though we are already working on our next release, there are no plans to phase out previous ones just yet.

Best Regards,


Luca Garulli
OrientDB Founder & CEO

The post OrientDB v2.2 GA – Improved Security, Performance, Operations & APIs appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/released-orientdb-v2-2/feed/ 0
Released OrientDB 2.1.17 http://orientdb.com/released-orientdb-2-1-17/ http://orientdb.com/released-orientdb-2-1-17/#comments Mon, 16 May 2016 12:42:59 +0000 http://orientdb.com/?p=13962 London, May 16, 2016 The OrientDB Team has just released OrientDB v2.1.17, resolving 26 issues from v2.1.16. This is the last stable release. Please […]

The post Released OrientDB 2.1.17 appeared first on OrientDB Distributed Graph Database.

]]>
London, May 16, 2016

The OrientDB Team has just released OrientDB v2.1.17, resolving 26 issues from v2.1.16. This is the last stable release. Please upgrade your production environments to v2.1.17. For more information, take a look at the Change Log.

Download OrientDB v2.1.17 now: http://orientdb.com/download

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

The post Released OrientDB 2.1.17 appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/released-orientdb-2-1-17/feed/ 0
How to calculate maximum amount of memory consumed by OrientDB http://orientdb.com/memory-consumed-by-orientdb/ http://orientdb.com/memory-consumed-by-orientdb/#comments Tue, 26 Apr 2016 12:17:42 +0000 http://orientdb.com/?p=13920 April 26, 2016 By Andrey Lomakin, Lead Research & Development Engineer at OrientDB. Many users ask how much memory is consumed by OrientDB and which settings affect this. […]

The post How to calculate maximum amount of memory consumed by OrientDB appeared first on OrientDB Distributed Graph Database.

]]>
April 26, 2016

By Andrey LomakinLead Research & Development Engineer at OrientDB.

Many users ask how much memory is consumed by OrientDB and which settings affect this. This question becomes even more pertinent since the OrientDB 2.2 release. In this latest release, we allocate memory in big chunks (about of 1gb size each) and then split it between threads on demand.

There are 2 reasons why we have chosen this approach:ram logo

  1. To fix OS allocation issues like this one
  2. To prepare for the change when we assign adjacent memory chunks for each thread on demand. As an example, lets suppose the first thread got a page with address 0x1 but second thread got a page with address 0xFE. Then on the next request for a new page the first thread will get a page with address 0x2 and second thread will get a page with address 0xFF. We hope It will allow us to improve system performance because of better CPU cache locality feature usage.

So how do you calculate maximum amount of memory consumed by OrientDB?  The answer to that is simple.  OrientDB uses both heap and direct memory. Direct memory is used in disk cache and database journal.

Memory consumed by disk cache may be calculated looking at the value of the storage.diskCache.bufferSize configuration parameter, which shows the maximum amount of memory consumed by disk cache in megabytes. The page cache size in kilobytes may be retrieved by reading the value of the storage.diskCache.pageSize parameter. It may be done using the console CONFIG GET command for example.  

You may get the maximum amount of pages consumed by the database journal by reading the value of the storage.wal.cacheSize parameter. You should increase this value by 1 and multiply by the value of the storage.diskCache.pageSize parameter. In this way you will get the maximum amount of direct memory consumed by the database journal.  After that we need to add both calculated values and increase the result until not divisible by 1GB without reminder.

The rest is simple. Add the value which you calculated above and add the amount of memory consumed by heap and you will get the maximum amount of memory which will be consumed by OrientDB.

UPDATE 1: Maximum size of memory chunk in bytes which will be allocated by OrientDB may be set using the memory.chunk.size property.

If you have any questions about this blog entry or about any of OrientDB’s features please post your question on stackoverflow and we will answer it.  For a complete guide on OrientDB’s features and properties be sure to read our Documentation.

 

The post How to calculate maximum amount of memory consumed by OrientDB appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/memory-consumed-by-orientdb/feed/ 0
Released OrientDB 2.1.15 http://orientdb.com/released-orientdb-2-1-15/ http://orientdb.com/released-orientdb-2-1-15/#comments Mon, 04 Apr 2016 13:02:39 +0000 http://orientdb.com/?p=13883 London, April 4, 2016 The OrientDB Team has just released OrientDB v2.1.15, resolving 8 issues from v2.1.14. This is the last stable release. Please […]

The post Released OrientDB 2.1.15 appeared first on OrientDB Distributed Graph Database.

]]>
London, April 4, 2016

The OrientDB Team has just released OrientDB v2.1.15, resolving 8 issues from v2.1.14. This is the last stable release. Please upgrade your production environments to v2.1.15. For more information, take a look at the Change Log.

Download OrientDB v2.1.15 now: http://orientdb.com/download

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

The post Released OrientDB 2.1.15 appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/released-orientdb-2-1-15/feed/ 0
Released OrientDB 2.1.14 http://orientdb.com/released-orientdb-2-1-14/ http://orientdb.com/released-orientdb-2-1-14/#comments Thu, 31 Mar 2016 07:57:52 +0000 http://orientdb.com/?p=13845 London, March 31, 2016 The OrientDB Team has just released OrientDB v2.1.14, resolving 22 issues from v2.1.13. This is the last stable release. Please […]

The post Released OrientDB 2.1.14 appeared first on OrientDB Distributed Graph Database.

]]>
London, March 31, 2016

The OrientDB Team has just released OrientDB v2.1.14, resolving 22 issues from v2.1.13. This is the last stable release. Please upgrade your production environments to v2.1.14. For more information, take a look at the Change Log.

Download OrientDB v2.1.14 now: http://orientdb.com/download

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

The post Released OrientDB 2.1.14 appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/released-orientdb-2-1-14/feed/ 0
OrientDB launches its Open Source NoSQL Graph-Document Database through CenturyLink’s Cloud Marketplace http://orientdb.com/orientdb-on-centurylink-cloud/ http://orientdb.com/orientdb-on-centurylink-cloud/#comments Thu, 17 Mar 2016 10:37:16 +0000 http://orientdb.com/?p=13750 OrientDB launches its Open Source NoSQL Graph-Document Database through CenturyLink’s Cloud Marketplace   LONDON, UK – March 17, 2016 – OrientDB, the pioneer behind […]

The post OrientDB launches its Open Source NoSQL Graph-Document Database through CenturyLink’s Cloud Marketplace appeared first on OrientDB Distributed Graph Database.

]]>
OrientDB launches its Open Source NoSQL Graph-Document Database through CenturyLink’s Cloud Marketplace

 

LONDON, UK – March 17, 2016 OrientDB, the pioneer behind the world’s first Open Source, NoSQL distributed graph-document database, today announced its certification under the CenturyLink Cloud Marketplace Provider Program. Through this partnership, CenturyLink Cloud users are now able to deploy and manage OrientDB’s community or enterprise edition databases via CenturyLink’s Blueprints library.

OrientDB is a second-generation distributed graph database with the flexibility of documents and an open source Apache 2 license. By treating every vertex and edge as a JSON (JavaScript Object Notation) document, OrientDB enables the creation of multi-directional property graphs, allowing bulks of data to be traversed with ease. This new multi-model approach, with a polyglot engine, eliminates the need for multiple systems, ensures data consistency and optimizes the formation of complex relationships. Even for a document-based database, the relationships are managed, as in graph databases, with direct connections amongst records. Its versatility and rapid integration makes OrientDB a perfect candidate for use cases ranging from recommendation engines and fraud detection to real-time analytics and content management. Fortune 500 companies, government entities and startups all use the technology to build large-scale innovative applications.

CenturyLink Cloud customers can now benefit from OrientDB’s features:

  • All-in-one graph, document and object store database
  • Stores 220,000 records per second on common hardware
  • ACID (atomicity, consistency, isolation and durability) compliant
  • Support for HTTP and JSON
  • Supports schema-less, schema-full and schema-mixed modes
  • Strong security profiling system based on user and roles
  • Despite being a NoSQL database, it still supports SQL amongst the query languages, making it familiar to those coming from a relational database background
  • Supports multi-master replication

OrientDB Community Edition is free for any purpose (including commercial use). OrientDB Enterprise Edition serves as an extension of the Community Edition by providing enterprise-needed features such as: Query Profiler, distributed clustering configuration, metrics recording, and Live Monitor with configurable alerts.

The CenturyLink Cloud Marketplace Provider Program allows participating technology companies, like OrientDB, to integrate with the CenturyLink Cloud platform. These additional business-ready solutions are available to CenturyLink’s cloud, hosting and network customers.

“Companies hoping to leverage big data are getting tired of dealing with multiple systems and increasing infrastructural costs,” said Luca Garulli, CEO of OrientDB. “Customers choose OrientDB for its innovative Multi-model database capabilities and affordable nature. Expanding our capabilities to the cloud through CenturyLink provides the perfect accessible solution without the need for multiple database systems or costly servers.”

“The foundation of the big data revolution on our platform has been software innovation around unstructured data management,” said David Shacochis, vice president of platform enablement at CenturyLink, “OrientDB is a great example of this trend, allowing our customers to manage their unstructured data relations in a scalable model that drives insight out of their business workloads”

To start using OrientDB on CenturyLink Cloud today, refer to the “Getting Started” guide on the CenturyLink Cloud Knowledge Base.

About OrientDB

OrientDB is an open source 2nd Generation Distributed Graph Database with the flexibility of Documents and a familiar SQL dialect. With downloads exceeding 70,000 per month, more than 100 community contributors and 1000’s of production users, OrientDB is experiencing tremendous growth in both community and Enterprise adoption. First generation Graph Databases lack the features that Big Data demands: multi-master replication, sharding and more flexibility for modern complex use cases. See for yourself, Download OrientDB and give it a try.

Editorial Contacts:
Paolo Puccini
OrientDB Ltd
+44 203 3971 609
info@orientdb.com

The post OrientDB launches its Open Source NoSQL Graph-Document Database through CenturyLink’s Cloud Marketplace appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/orientdb-on-centurylink-cloud/feed/ 0
Released OrientDB 2.1.13 http://orientdb.com/released-orientdb-2-1-13/ http://orientdb.com/released-orientdb-2-1-13/#comments Tue, 15 Mar 2016 09:12:32 +0000 http://orientdb.com/?p=13732 London, March 15, 2016 The OrientDB Team has just released OrientDB v2.1.13, resolving 16 issues from v2.1.12. This is the last stable release. Please […]

The post Released OrientDB 2.1.13 appeared first on OrientDB Distributed Graph Database.

]]>
London, March 15, 2016

The OrientDB Team has just released OrientDB v2.1.13, resolving 16 issues from v2.1.12. This is the last stable release. Please upgrade your production environments to v2.1.13. For more information, take a look at the Change Log.

Download OrientDB v2.1.13 now: http://orientdb.com/download

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

The post Released OrientDB 2.1.13 appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/released-orientdb-2-1-13/feed/ 0
OrientDB Teleporter – Making Migrations Easier (Part 2) http://orientdb.com/orientdb-teleporter-making-migrations-easier-part-2/ http://orientdb.com/orientdb-teleporter-making-migrations-easier-part-2/#comments Mon, 14 Mar 2016 14:50:39 +0000 http://orientdb.com/?p=13692 By OrientDB Developer Gabriele Ponzi Teleporter to Sync your DB and OrientDB This is Part 2 of our step by step guide on how to […]

The post OrientDB Teleporter – Making Migrations Easier (Part 2) appeared first on OrientDB Distributed Graph Database.

]]>
By OrientDB Developer Gabriele Ponzi

Teleporter to Sync your DB and OrientDB

This is Part 2 of our step by step guide on how to use Teleporter to migrate and synchronize your database with OrientDB.

If you are interested in a detailed description of the tool, of its inner workings and features, please read the previous post (part 1) or the official documentation.

In short, OrientDB Teleporter is a tool that synchronizes a RDBMS to an OrientDB database. You can use Teleporter to:

- Import your existing RDBMS to OrientDB.

- Keep your OrientDB database synchronized with changes from the RDBMS. In this case the database on RDBMS remains the primary one and the database on OrientDB a synchronized copy. Synchronization is one way, so all the changes in the OrientDB database will not be propagated to the RDBMS.

This means that the first execution process performs a migration from scratch, whereas all subsequent migrations on the same target OrientDB graph database carry out a synchronization between your source database and OrientDB.
This dual behaviour is transparent to the user who will always follow the same procedure.

Teleporter is fully compatible with several RDBMS that have a JDBC drivers: we successfully tested Teleporter with Oracle, SQLServer, MySQL, PostgreSQL and HyperSQL. Teleporter manages all the necessary type conversions between the different DBMSs and imports all your data as a Graph in OrientDB.
This tool is really easy to use thanks to a completely automatic and clear execution which require few important parameters. At the same time, it’s possible to enrich the migration process by specifying different strategies and customizations which allow you to obtain more refined results.

Now let’s start from the simplest migration case. First of all, you can invoke the tool through  the oteleporter.sh (Unix and OS X platforms) or oteleporter.bat (Windows platforms) scripts. Then you must type 3 mandatory arguments to begin your import:

- -jdriver: is the driver name of the DBMS from which you want to execute the import.

- -jurl: is the JDBC URL giving the location of the source database to import.

- -ourl: is the URL for the destination Orient graph database.

 If credentials are required to access your source database you have to type two  more arguments:

- -juser: is the username to access the source database.

- -jpasswd is the password to access the source database.

Thus, in this case the generic call to Teleporter looks like this:

oteleporter.sh -jdriver <jdbc-driver> -jurl <jdbc-url> -juser <username>

-jpasswd <password> -ourl <orientdb-url>

 

All other parameters are optional: now let’s start with a standard migration from each compatible DBMS.

When you specify the DBMS you want to connect with through the argument -jdriver, you must choose amongst the following values:

- Oracle

- SQLServer

- MySQL

- PostgreSQL

- HyperSQL

N.B.: the driver identification is not case sensitive, so you may also type  “oracle”, “sqlserver” etc.

Migrating and Syncing with your database

Let’s suppose we want to import the source database “source-db”  into an OrientDB graphDB called “myTargetDB” and that the source database relies on our local machine with credentials admin|admin.
Depending on our specific DBMS we’ll type the different commands reported in the following table:

DBMS

SOURCE DB URL FORMAT

TELEPORTER COMMAND

Oracle

jdbc:oracle:thin:@<HOST>:<PORT>:<SID>

oteleporter.sh -jdriver Oracle

-jurl jdbc:oracle:thin:@localhost:1521:xe
-juser admin -jpasswd admin
-ourl /ORIENTDB_HOME/databases/myTargetDB

SQLServer

jdbc:sqlserver://<HOST>:<PORT>;databaseName=<DB>
oteleporter.sh -jdriver SQLServer

-jurl jdbc:sqlserver://localhost:1433;databaseName=source-db
-juser admin-jpasswd admin
-ourl /ORIENTDB_HOME/databases/myTargetDB
(*)

MySQL

jdbc:mysql://<HOST>:<PORT>/<DB>
oteleporter.sh -jdriver MySQL

-jurl jdbc:mysql://localhost:3306/source-db
-juseradmin -jpasswd admin
-ourl /ORIENTDB_HOME/databases/myTargetDB

PostgreSQL

jdbc:postgresql://<HOST>:<PORT>/<DB>
oteleporter.sh -jdriver PostgreSQL

-jurl jdbc:postgresql://localhost:5432/source-db
-juser admin -jpasswd admin
 -ourl /ORIENTDB_HOME/databases/myTargetDB

HyperSQL

jdbc:hsqldb:hsql://<HOST>/<DB>

(connection to a database server)

jdbc:hsqldb:file:<filepath>,
jdbc:hsqldb:mem:<DB>,
jdbc:hsqldb:res:<package name>

(connection to a resource)

oteleporter.sh -jdriver HyperSQL

-jurl jdbc:hsqldb:hsql://localhost/source-db
-juser admin-jpasswd admin
 -ourl /ORIENTDB_HOME/databases/myTargetDB

(*) If the source database contains spaces in the name you have to use a URL like this:
“Source DB” →  -jurl “jdbc:sqlserver://localhost:1433;databaseName={Source DB};”

Next, we must simply wait for the process to end.

Migration with optional parameters

If you want to enrich the migration process from your specific DBMS with optional parameters, you just have to type them following the syntax described in the documentation and in the previous post [link].
Here I report the complete command syntax:

oteleporter.sh -jdriver <jdbc-driver> -jurl <jdbc-url> -ourl <orientdb-url>

[-juser <username>] [-jpasswd <password>] [-s <strategy>]
[-nr <name-resolver>] [-v <verbose-level>]
([-include <table-names>] | [-exclude <table-names>])
[-inheritance <orm-technology>:<ORM-file-url>]

 

I hope this post was helpful and interesting.

Stay tuned,

Gabriele Ponzi
OrientDB Ltd

Download OrientDB Teleporter!

References:
Teleporter full documentation: https://github.com/orientechnologies/orientdb-labs/blob/master/Teleporter-Index.md

 

 

The post OrientDB Teleporter – Making Migrations Easier (Part 2) appeared first on OrientDB Distributed Graph Database.

]]>
http://orientdb.com/orientdb-teleporter-making-migrations-easier-part-2/feed/ 0