Son's picture

SQL in the Banking IT

Here is description of SQL from Wikipedia ( ):
SQL often referred to as Structured Query Language, is a database computer language designed for managing data in relational database management systems (RDBMS), and originally based upon relational algebra. Its scope includes data insert, query, update and delete, schema creation and modification, and data access control. SQL became the most widely used language for relational databases.

Today for the question “How important is SQL in the Banking IT?”, the answer would be “crucial”. Nowadays no Bank can afford to do operation without any SQL database. The SQL became basic and essential.

Customers get account statements (from Banks), which is result of using SQL. Banks users get financial reports (from their banking systems), which are results of using SQL as well. Banking data is processed by banking IT applications using SQL. Data processing consists of many complex workflows which executing SQL.

Let’s see one data processing for the case of customer deposit:
One customer (the Customer) requests to put some his money in deposit in one bank (the Bank). The Customer’s data like his name, birthday, personal ID,… and deposit requirements will be inputted (data insert) into the Bank’s system. When the deposit expires, the Bank’s system calculates interest and adds to the principal amount (data update). At the agreed time the Bank prints the deposit statement (data query) for the Customer.

I would like here to discuss about modeling of data processing in SQL terminology:
We can imagine that a data processing is consists of workflows. Each workflow consists of many SQL statements (SQL statement is one of data insert, update, delete, query). If we considered a SQL statement as a “molecule” then a workflow would be a “matter” and a data processing would be a “set of matters”.

You could ask the question: Why do we need this model?
My opinion is that the data processing is basically SQL centralized.
So we need to concentrate more on:
• Improving SQL skill for human resource
• Getting software, hardware which support this approach more efficiently