Answer / bunty

Atomocity
Consistenct
Isolated
Durability

Answer / piyush sharma

ACID refers to the basic properties of a database
transaction: Atomicity, Consistency, Isolation, and
Durability.

All Oracle database, Oracle RDB and InnoDB transactions
comply with these properties. However, Oracle's Berkeley DB
database is not ACID-compliant.

Atomicity

The entire sequence of actions must be either completed or
aborted. The transaction cannot be partially successful.

Consistency

The transaction takes the resources from one consistent
state to another.

Isolation

A transaction's effect is not visible to other transactions
until the transaction is committed.

Durability

Changes made by the committed transaction are permanent and
must survive system failure

Answer / subir

ACID stands for
A-Atomicity
C-Consistency
I-Isolation
D-Durability

Answer / naveen

The means by which ACID is enforced in Oracle are :

Undo Segments - for Atomicity
Undo Segments - for Consistency
Undo Segments & Locks - for Isolation
Redo Logs - for Durability

Answer / bilal

ACID properties are an important concept for databases. The
acronym stands for Atomicity, Consistency, Isolation, and
Durability.

Atomicity:

The phrase "all or nothing" succinctly describes the first
ACID property of atomicity. When an update occurs to a
database, either all or none of the update becomes available
to anyone beyond the user or application performing the
update. This update to the database is called a transaction
and it either commits or aborts. This means that only a
fragment of the update cannot be placed into the database,
should a problem occur with either the hardware or the
software involved. Features to consider for atomicity:

* a transaction is a unit of operation - either all the
transaction's actions are completed or none are
* atomicity is maintained in the presence of deadlocks
* atomicity is maintained in the presence of database
software failures
* atomicity is maintained in the presence of application
software failures
* atomicity is maintained in the presence of CPU failures
* atomicity is maintained in the presence of disk failures
* atomicity can be turned off at the system level
* atomicity can be turned off at the session level

Consistency:

Consistency is the ACID property that ensures that any
changes to values in an instance are consistent with changes
to other values in the same instance. A consistency
constraint is a predicate on data which serves as a
precondition, post-condition, and transformation condition
on any transaction.

Isolation:

The isolation portion of the ACID properties is needed when
there are concurrent transactions. Concurrent transactions
are transactions that occur at the same time, such as shared
multiple users accessing shared objects. This situation is
illustrated at the top of the figure as activities occurring
over time. The safeguards used by a DBMS to prevent
conflicts between concurrent transactions are a concept
referred to as isolation.

As an example, if two people are updating the same catalog
item, it's not acceptable for one person's changes to be
"clobbered" when the second person saves a different set of
changes. Both users should be able to work in isolation,
working as though he or she is the only user. Each set of
changes must be isolated from those of the other users.
An important concept to understanding isolation through
transactions is serializability. Transactions are
serializable when the effect on the database is the same
whether the transactions are executed in serial order or in
an interleaved fashion. As you can see at the top of the
figure, Transactions 1 through Transaction 3 are executing
concurrently over time. The effect on the DBMS is that the
transactions may execute in serial order based on
consistency and isolation requirements. If you look at the
bottom of the figure, you can see several ways in which
these transactions may execute. It is important to note that
a serialized execution does not imply the first transactions
will automatically be the ones that will terminate before
other transactions in the serial order.

Degrees of isolation:
* degree 0 - a transaction does not overwrite data updated
by another user or process ("dirty data") of other transactions
* degree 1 - degree 0 plus a transaction does not commit any
writes until it completes all its writes (until the end of
transaction)
* degree 2 - degree 1 plus a transaction does not read dirty
data from other transactions
* degree 3 - degree 2 plus other transactions do not dirty
data read by a transaction before the transaction commits

Durability:

Maintaining updates of committed transactions is critical.
These updates must never be lost. The ACID property of
durability addresses this need. Durability refers to the
ability of the system to recover committed transaction
updates if either the system or the storage media fails.
Features to consider for durability:

* recovery to the most recent successful commit after a
database software failure
* recovery to the most recent successful commit after an
application software failure
* recovery to the most recent successful commit after a CPU
failure
* recovery to the most recent successful backup after a disk
failure
* recovery to the most recent successful commit after a data
disk failure


Thanks

Answer / pallis

Atomicity
The entire sequence of actions must be either completed or aborted. The transaction cannot be partially successful.
Consistency
The transaction takes the resources from one consistent state to another.
Isolation
A transaction's effect is not visible to other transactions until the transaction is committed.
Durability
Changes made by the committed transaction are permanent and must survive system failure.

Answer / kala

Atomicity
consistence

Isolation

Durability

Answer / sagar

Atomicity: is an all-or-none proposition.

Consistency: guarantees that a transaction never leaves your
database in a half-finished state.

Isolation: keeps transactions separated from each other
until they’re finished.

Durability: guarantees that the database will keep track of
pending changes in such a way that the server can recover
from an abnormal termination.

Above four rules are very important for any developers
dealing with databases.

Answer / c.vanitha

atomacity
consistency
integrity
durability

Answer / bilal

1. A characteristic sour taste;
2. Ability to change the color of litmus paper from blue to red;
3. React with certain metals to produce gaseous H2 ;
4. React with bases to form a salt and water.

can Constraints cannot be exported through EXPORT command ?

2 Answers   Grasim, Oracle, Suvidha,

Why c++ used in clipper?

0 Answers  

What is pcbs (program communication blocks)?

0 Answers  

Explain what is a deadlock and mention how it can be resolved?

0 Answers  

What are five advantages of a database?

0 Answers  

What is sorting in dbms?

0 Answers  

What is big data in database?

0 Answers  

What is view dbms?

0 Answers  

Why do we use databases?

0 Answers  

What is raid controller technology?

0 Answers  

difference between generalisation,specialisation and aggregation? with examples.

0 Answers  

How do I add a file to a database?

0 Answers