IT Glossary
What is SQL?
Structured Query Language: the standard way to ask questions of relational databases — for half a century, everywhere.
Ask a relational database a question — say, every customer in London with orders above ten thousand this year, sorted by value — and that question is written in SQL, a syntax close enough to English that non-programmers can read it. Born in the 1970s and standardised ever since, it is spoken by every database engine that matters: PostgreSQL, MySQL, SQL Server, Oracle, SQLite. That longevity works like an insurance policy on your company's information. Records held in SQL systems are never hostage to one supplier: millions of specialists can query, export and migrate them, and applications built on top remain transferable. Three practical moments make the term relevant to a buyer. During procurement, 'which database does the system sit on?' has reassuring answers (PostgreSQL, MySQL, SQL Server) and answers deserving follow-up questions (exotic proprietary engines mean dependency). In reporting, SQL is how analysts and BI tools pull answers straight from your records — many 'impossible' reports are a ten-line query for someone with read access. And in security, SQL injection remains the classic web attack; asking a vendor how user input reaches queries is a standard audit question.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247
Why it matters for your business
Your data in a universal language
A standard known by millions of specialists means company records can always be queried, exported or migrated — by anyone, not only the current vendor.
The 'impossible' reports, unlocked
What an application's interface refuses to show, a ten-line query delivers in minutes — read access to data turns 'cannot be done' into numbers.
Half a century of maturity
SQL engines solved transactions, consistency and business-scale workloads decades ago — a default foundation nobody regrets choosing.
Frequently asked questions
Is SQL worth learning for someone outside IT?
Yes, and typically not by programmers: the analyst or manager who learns basic SELECT statements becomes autonomous on ad-hoc questions instead of queueing for vendor reports. AI assistants have lowered the barrier further — describe the question in plain language, receive the query, validate it against known figures. The practical prerequisite is read access to a reporting copy of the data, worth requesting with any new system.
What is SQL injection and should it worry me?
It is the attack where text typed by a user is crafted to become an executable part of a database query, with consequences ranging from reading the entire database to deleting it. Prevention is entirely the developer's job through parameterised queries, a standard for decades; your job is verification — any public-facing application deserves a security test, and vendors should answer 'how do you handle user input in queries?' without hesitation.
Our vendor refuses direct access to the database — is that normal?
For write access, yes: changes made around the application break integrity. For read access to your own records, no — it is a legitimate request, technically solvable through a reporting replica or scheduled exports without any risk to the application. A supplier refusing every form of data access is revealing their retention philosophy; negotiate that clause before signature, while you still can.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247