***** Apache Cassandra Certification Training : https://www.edureka.co/cassandra *****
In this Edureka Video, you will learn about Cassandra Data Model and similarities between RDBMS and Cassandra Data Model. You will also understand the key Database Elements of Cassandra (Keyspace, Clusters, Column Family and Rows) and learn about the concept of Primary Key and it's various types.
After the completion of 'Apache Cassandra' course at Edureka, you should be able to:
1. Understand Cassandra and NoSQL domain.
2. Create Cassandra cluster for different kinds of applications.
3. Understand Apache Cassandra Architecture.
4. Design and model Applications for Cassandra.
5. Port existing application from RDBMS to Cassandra.
6. Learn to use Cassandra with various programming languages.
Who should go for this course?
A developer working with large-scale, high-volume websites.
An application architect or data architect who needs to understand the available options for high-performance, decentralized, elastic data stores
A database administrator or database developer currently working with standard relational database systems who needs to understand how to implement a fault-tolerant, eventually consistent data store
A manager who wants to understand the advantages (and disadvantages) of Cassandra and related columnar databases to help make decisions about technology strategy
A student, analyst, or researcher who is designing a project related to Cassandra or other non-relational data store options.
This course assumes no prior knowledge of Apache Cassandra or any other NoSQL database. Though some familiarity with Linux command line is essential, minimal exposure to Java,database or data-warehouse concepts is required.
Why should you Learn Cassandra?
1. Cassandra is designed to handle Cassandra workloads across multiple data centers with no single point of failure, providing enterprises with extremely high database performance and availability.
2. World's largest Website (i.e Cassandra) is running over Cassandra.
3. Daily 100s of start-ups and large product companies are choosing Cassandra for their next generation computing and data platforms. Some companies using Cassandra are Facebook, Twitter, IBM, Cisco, Rackspace, NetFlix, eBay, Reddit, @WalmartLabs, Zoho, Digg and so on.
4. Apache Cassandra is open-source. It means you can deep dive into its source code and change it according to your own requirements.
5. The job market for Apache Cassandra is at peek and is growing at rate of 300%!
For more information, Please write back to us at [email protected] or call us at IND: 9606058406 / US: 18338555775 (toll-free).
A trigger is a named PL/SQL unit that is stored in the database and executed ( fired ) in response to a specified event that occurs in the database.
Overview of Triggers.
A trigger is a named program unit that is stored in the database and fired (executed) in response to a specified event. The specified event is associated with either a table, a view, a schema, or the database, and it is one of the following:
A database manipulation (DML) statement ( DELETE , INSERT , or UPDATE )
A database definition (DDL) statement ( CREATE , ALTER , or DROP )
A database operation ( SERVERERROR , LOGON , LOGOFF , STARTUP , or SHUTDOWN )
The trigger is said to be defined on the table, view, schema, or database.
A DML trigger is fired by a DML statement, a DDL trigger is fired by a DDL statement, a DELETE trigger is fired by a DELETE statement, and so on.
An INSTEAD OF trigger is a DML trigger that is defined on a view (not a table). The database fires the INSTEAD OF trigger instead of executing the triggering DML statement. For more information, see Modifying Complex Views (INSTEAD OF Triggers).
A system trigger is defined on a schema or the database. A trigger defined on a schema fires for each event associated with the owner of the schema (the current user). A trigger defined on a database fires for each event associated with all users.
A simple trigger can fire at exactly one of the following timing points :
Before the triggering statement executes.
After the triggering statement executes.
Before each row that the triggering statement affects.
After each row that the triggering statement affects.
A compound trigger can fire at more than one timing point. Compound triggers make it easier to program an approach where you want the actions you implement for the various timing points to share common data. For more information, see Compound Triggers.