The biggest issue you’ll have is that “migration” from a relational to Cassandra is not a 1 to 1. The schemas will have to change.
DSE has other technology that is a little more useful - such as Spark / Spark SQL / Solr that is built in which helps meet the needs which Oracle was previously providing. Rahul Singh Chief Executive Officer m 202.905.2818 Anant Corporation 1010 Wisconsin Ave NW, Suite 250 Washington, D.C. 20007 We build and manage digital business technology platforms. On Sep 5, 2018, 10:47 AM -0500, Jeff Jirsa <jji...@gmail.com>, wrote: > All of Sean's points are good, a few more: > - Apache Cassandra (free, open source, official) is usually sufficient. DSE > may be faster, but really it's about whether or not you're willing to pay for > support. If you're trying to stop paying Oracle, I suspect you'd probably not > want to start paying someone else - try the free version first, and you can > look for proprietary options after that. > - http://shop.oreilly.com/product/0636920043041.do is relatively recent and > mostly pretty good > - Ask a lot of questions, use this list, but try things out first so people > have a way to point you in the right direction. > > > > > On Wed, Sep 5, 2018 at 7:58 AM Durity, Sean R <sean_r_dur...@homedepot.com> > > wrote: > > > 3 starting points: > > > - DO NOT migrate your tables as they are in Oracle to Cassandra. > > > In most cases, you need a different model for Cassandra > > > - DO take the (free) DataStax Academy courses to learn much more > > > about Cassandra as you dive in. It is a systematic and bite-size approach > > > to learning all things Cassandra (and eventually, DataStax Enterprise, > > > should you go that way). However, open source Cassandra is fine as a data > > > platform. DSE gives you more options for data models, better > > > administration and monitoring tools, support, etc. It all depends on what > > > you need/want to build/can afford > > > - Cluster sizing depends on your goals for the data platform. Do > > > you need lots of storage, lots of throughput, high availability, low > > > latency, workload separation, etc.? A couple guidelines – use at least 3 > > > nodes per data center (DC) and at least 2 DCs for availability. Use SSDs > > > for storage and keep node size 3 TB or less for reasonable > > > administration. If six nodes are too many – you probably don’t need > > > Cassandra. If you can define what you need your data platform to deliver, > > > then you can start a sizing discussion. The good thing is, you can always > > > scale (as long as the data model is good). > > > > > > > > > Sean Durity > > > > > > From: sha p <shatestt...@gmail.com> > > > Sent: Wednesday, September 05, 2018 9:21 AM > > > To: user@cassandra.apache.org > > > Subject: [EXTERNAL] Regarding migrating data from Oracle to > > > Cassandra.migrate data from Oracle to Cassandra. > > > > > > > > > > quote_type > > > > Hi all , > > > > Me new to Cassandra , i was asked to migrate data from Oracle to > > > > Cassandra. > > > > Please help me giving your valuable guidance. > > > > 1) Can it be done using open source Cassandra. > > > > 2) Where should I start data model from? > > > > 3) I should use java, what kind of jar/libs/tools I need use ? > > > > 4) How I decide the size of cluster , please provide some sample > > > > guidelines. > > > > 5) this should be in production , so what kind of things i should take > > > > care for better support or debugging tomorrow? > > > > 6) Please provide some good books /links which can help me in this task. > > > > > > > > > > > > Thanks in advance. > > > > Highly appreciated your every amal help. > > > > > > > > Regards, > > > > Shyam > > > > > > > > > The information in this Internet Email is confidential and may be legally > > > privileged. It is intended solely for the addressee. Access to this Email > > > by anyone else is unauthorized. If you are not the intended recipient, > > > any disclosure, copying, distribution or any action taken or omitted to > > > be taken in reliance on it, is prohibited and may be unlawful. When > > > addressed to our clients any opinions or advice contained in this Email > > > are subject to the terms and conditions expressed in any applicable > > > governing The Home Depot terms of business or client engagement letter. > > > The Home Depot disclaims all responsibility and liability for the > > > accuracy and content of this attachment and for any damages or losses > > > arising from any inaccuracies, errors, viruses, e.g., worms, trojan > > > horses, etc., or other items of a destructive nature, which may be > > > contained in this attachment and shall not be liable for direct, > > > indirect, consequential or special damages in connection with this e-mail > > > message or its attachment.
