Interesting things about Relational Databases

Data here data there data everywhere. Data is my life, sorry our life. The growth of data is tremendous. We (I) used to store the data in paper. We used to sign with a pen, now obviously with digital signatures. There is parallel way of looking at the database world. But the fundamentals remain the same with core data. Data obviously has a fundamental role to play and here’s where there are rules set to govern and principiate the data.

Right from the inception of the database to its linear and analogous growth there were lot of discussions regarding:
1. How much data we have to store?
2. What would be max size of the database?
3. How do I secure my data?
4. How would I backup and how much will I backup?
5. How do I immediately recover from a failure?
6. How do I use best of analytical skills to leverage and tap new markets?

To answer all such questions a relational model proposed by E.F Codd came into existence.

Today the relational databases have gone leagues ahead in terms of timestamping (micro time stamping) to preserve
A — Atomicity — Individuality of the transactions
C — Consistency — Preserving a state of a transaction
I — Isolation — How would the transaction behave when it where to be considered as an individual entity?
D — Duration — The amount of time the transaction would persist.

Today data is huge. So database is a challenging domain. We have gargantuan task of replicating a huge database. Taking up the recovery in case of mission critical database goes offline partially or completely.

We have huge repository of offline and online database for analysis catching out the trends for efficiency be it in terms of sales or optimization of organizational process.

It’s almost like a time machine. Roll the database back in time or roll forward the database. You could get in time to see the world as it was then and as it is now.

Time is an asset at any point of time. There are lot of provisions to protect this asset. There is no room for ambiguity as we orchestrate with constraints

“A rule enforced to all”

So this how it is.

Databases have the following career paths:
1. A developer — Has to develop apps and should know database along with front-end tools
2. A DBA — Has to know data internals and obviously support smooth functioning 24/7
3. An OS admin — Has to know the internals of OS in relation with the databases
4. Database related Network Specialist — Networking is the way in which business functiona and the database leverages the functionality along with the network
5. Database Analyst –The huge repository of the data is like a gold mine which would turn your business profits

So “Join Database, Explore database and Shine your database career”