How NLP Can Turn Questions into SQL Queries

Patient Tools

Read, save, and share this guide

Use these quick tools to make this medical article easier to read, print, save, or share with a family member.

Article Summary

A few years ago, the major bottleneck in data science was cleaning and processing huge volumes of data so that it could be analyzed. While new tools and processes have automated large parts of the data ingestion process, a new bottleneck has appeared: The analysis itself. Even though data science remains one of the fastest-growing jobs categories in the country, there still simply aren’t enough trained...

Educational health guideWritten for patient understanding and clinical awareness.
Reviewed content workflowUse writer and reviewer profiles for stronger trust.
Emergency safety firstUrgent warning signs are highlighted below.

Seek urgent medical care if you notice

These warning signs are general safety guidance. Local emergency numbers and clinical judgment should always come first.

  • Severe symptoms, breathing difficulty, fainting, confusion, or rapidly worsening illness.
  • New weakness, severe pain, high fever, or symptoms after a serious injury.
  • Any symptom that feels urgent, unusual, or unsafe for the patient.
1

Emergency now

Use emergency care for severe, sudden, rapidly worsening, or life-threatening symptoms.

2

See a doctor

Book a professional medical evaluation if symptoms persist, worsen, recur often, affect daily activities, or occur in a high-risk patient.

3

Learn safely

Use this article to understand possible causes, tests, treatment options, prevention, and questions to ask your clinician.

A few years ago, the major bottleneck in data science was cleaning and processing huge volumes of data so that it could be analyzed. While new tools and processes have automated large parts of the data ingestion process, a new bottleneck has appeared: The analysis itself. Even though data science remains one of the fastest-growing jobs categories in the country, there still simply aren’t enough trained data analysts to answer all the questions that organizations are creating.

As work across all industries becomes increasingly data-driven, the ability to quickly access and interpret data has become more important than ever. While it might be great if every worker just learned how to write perfect SQL queries, it’s not going to happen anytime soon. To reduce some of the burdens on already overstretched data teams, many organizations are looking for tools that allow non-developers to query their relational databases.

The importance of ad-hoc queries

There are plenty of business intelligence (BI) tools out there that provide dashboards with key metrics, but if you’re only looking at dashboards you’re missing out on all the insights that remain hidden inside your data. That’s why it’s important to be able to perform ad-hoc queries as well.

Unfortunately, writing a valid SQL query that answers the question you’re trying to ask isn’t always easy. Even seemingly simple questions, like “Which of our customers makes us the most money?” can be very hard to answer, let alone convert into a SQL query. How do you define your customer cohorts? By age, location, behavioral patterns? Are you looking at how much customers spend on a single visit, or over their entire customer lifecycle?

As more and more organizations try to integrate data into their decision-making processes, the ability of non-data specialists to write their queries can be the key to major gains in productivity and improved decision-making. Especially as functions that have traditionally been less data-driven, like Marketing and HR, begin to explore their data, employees need to be able to get answers to their questions promptly.

The advantages (and the shortcomings) of visual query builders

Lots of organizations turn to BI software to create dashboards with key performance indicators and other useful metrics. Some of these BI and visualization tools have begun offering support for more than just standard SQL queries, building drag-and-drop interfaces that allow people who don’t necessarily know how to structure a SQL query to get into the data.

These tools work by connecting to a database and then allowing users to select what variables they want and then map them onto a graph or chart. Unfortunately, these tools have several shortcomings. A visual query builder may generate technically valid SQL, but the query itself may end up being too complex to run or risk bringing your server down in the process.

Another shortcoming of visual query builders is that they still require users to know more or less what they’re asking for. To construct a query, you still have to manually select the right columns and input the appropriate conditions. In essence, the user still has to “convert” their question into terms a computer can understand even if they’re not writing the exact query.

This may be fine if a user is working with a database they’re already familiar with, but what if Marketing wants to ask a question about detailed user behavior on the company’s iOS app? Or what if a user isn’t sure which columns or operations are appropriate?

Looking to the future: Natural-language queries

What we’re asking here is how to convert natural human language into valid SQL queries. By itself, natural language processing (NLP) is one of the most challenging areas in AI research, and translating that question into a valid SQL query introduces a whole new layer of complexity. Still, there’ve been several efforts over the last few years to develop models that can do just that.

Salesforce released a research paper in 2017 detailing a model called Seq2SQL that uses neural networks and reinforcement learning to create valid and accurate SQL queries out of human questions. Salesforce’s work was a big deal for two reasons. First, the model used reinforcement learning, meaning it will improve over time as more and more people use it. Already Seq2SQL has shown significant improvements over the previous state-of-the-art.

Second, Salesforce has released a massive open source training set, WikiSQL, which it claims to be orders of magnitude larger than existing training sets. This way, other developers and researchers working on NLP interfaces can take advantage of a high-quality training set, saving them one of the most time-consuming and difficult steps of building and training an algorithm.

So how does it work? Say we want to answer the question: “How many presidents since 1900 have won with less than 50% of the national popular vote?” Let’s say we’re using a database called presidential_elections, which looks something like this:

YearPresidentPopVoteRawPopVotePerPopVoteMarRunner-upTurnout
1824John Q Adams113,14230.92-38,221Andrew Jackson26.9
1828Andrew Jackson642,80655.93140,839John Q Adams57.3
1832Andrew Jackson702,73554.74228,628Henry Clay57.0
1836Martin Van Buren763,29150.79213,384William Henry Harrison56.5

And so on. The model should recognize that the “presidents” in our question points to the “President” column, while “How many” indicates that we want the COUNT operation. Thus, the first part of our query should ideally look something like this:

SELECT COUNT (President)

FROM presidential_elections

Now’s the harder part. Hopefully, the model will be able to tell that “since 1900” and “with less than 50% of the popular vote” represent two separate conditions with greater than and less than operators, respectively. So hopefully, we’ll get a condition that looks something like:

WHERE Year > 1900

AND PopVotePer < 50;

If all goes well, our query should return the correct answer: Nine.

Looking for a data analyst?

For the moment, natural language-based query engines remain more of an intriguing concept than a practical reality. Until then, you may still want to turn to human data analysts for your querying needs. Fortunately, data analysis skills are increasingly widespread, and even junior-level data analysts should be able to produce ad hoc queries for a variety of database systems and create visualizations to help you interpret their findings.

Patient safety assistant

Check your symptom safely

Hi, I am RX Symptom Navigator. I can help you understand what to read next and what warning signs need care.
Warning: Do not use this in emergencies, pregnancy, severe illness, or as a substitute for a doctor. For children or teens, use with a parent/guardian and clinician.
A rural-friendly guide: warning signs, when to see a doctor, related articles, tests to discuss, and OTC safety education.
1 Symptom 2 Severity 3 Safe guidance
First safety question

Is there chest pain, breathing trouble, fainting, confusion, severe bleeding, stroke-like weakness, severe injury, or pregnancy danger sign?

Choose quickly

Browse by body area
Start here: Write or select a symptom. The guide will show warning signs, doctor guidance, diagnostic tests to discuss, OTC safety education, and related RX articles.

Important: This tool is educational only. It cannot diagnose, treat, or replace a doctor. OTC information is not a prescription. In an emergency, contact local emergency services or go to the nearest hospital.

Doctor visit helper

Prepare before seeing a doctor

A simple rural-patient checklist to help you explain symptoms clearly, ask better questions, and avoid unsafe self-treatment.

Safety note: This is not a prescription or diagnosis. For severe symptoms, pregnancy danger signs, children with serious illness, chest pain, breathing difficulty, stroke-like weakness, or major injury, seek urgent care.

Which doctor may help?

Start with a registered doctor or the nearest qualified health center.

What to tell the doctor

  • Write when the problem started and how it changed.
  • Bring old prescriptions, investigation reports, and current medicines.
  • Write allergies, pregnancy status, diabetes, kidney/liver disease, and major past illnesses.
  • Bring one family member if the patient is weak, elderly, confused, or a child.

Questions to ask

  • What is the most likely cause of my symptoms?
  • Which danger signs mean I should go to hospital quickly?
  • Which tests are necessary now, and which can wait?
  • How should I take medicines safely and what side effects should I watch for?
  • When should I come for follow-up?

Tests to discuss

  • Vital signs: temperature, pulse, blood pressure, oxygen saturation
  • Basic physical examination by a clinician
  • CBC, urine test, blood sugar, or imaging only when clinically needed

Avoid these mistakes

  • Do not use antibiotics, steroid tablets/injections, or strong painkillers without proper medical advice.
  • Do not hide pregnancy, kidney disease, ulcer, allergy, or blood thinner use.
  • Do not delay emergency care when danger signs are present.

Medicine safety and first-aid guide

This section is for patient education only. It does not replace a doctor, pharmacist, or emergency care.

Safe first steps

  • Rest, drink safe water, and observe symptoms carefully.
  • Keep a written note of symptoms, duration, temperature, medicines already taken, and allergy history.
  • Seek medical care quickly if symptoms are severe, worsening, or unusual for the patient.

OTC medicine safety

  • For mild pain or fever, ask a registered pharmacist or doctor before using common over-the-counter pain/fever medicines.
  • Do not combine multiple pain medicines without advice, especially if you have kidney disease, liver disease, stomach ulcer, asthma, pregnancy, or take blood thinners.
  • Do not give adult medicines to children unless a qualified clinician advises it.

Avoid these mistakes

  • Do not start antibiotics without a proper medical decision.
  • Do not use steroid tablets or injections casually for quick relief.
  • Do not delay emergency care because of home remedies.

Get urgent help if

  • Severe symptoms, confusion, fainting, breathing difficulty, chest pain, severe dehydration, or sudden weakness need urgent medical care.
Medicine names, dose, and timing must be decided by a qualified clinician or pharmacist after checking age, pregnancy, allergy, other diseases, and current medicines.

For rural patients and family caregivers

Patient health record and symptom diary

Write your symptoms, medicines already taken, test results, and questions before visiting a doctor. This note stays on your device unless you print or copy it.

Doctor to discuss: Doctor / qualified healthcare provider
Tests to discuss with doctor
  • Basic vital signs: temperature, pulse, blood pressure, oxygen level if needed
  • Relevant blood, urine, imaging, or specialist tests only after clinical assessment
Questions to ask
  • What is the most likely cause of my symptoms?
  • Which warning signs mean I should go to emergency care?
  • Which tests are really needed now?
  • Which medicines are safe for my age, pregnancy status, allergy, kidney/liver/stomach condition, and current medicines?

Emergency warning signs such as chest pain, severe breathing difficulty, sudden weakness, confusion, severe dehydration, major injury, or loss of bladder/bowel control need urgent medical care. Do not wait for online information.

Safe pathway to proper treatment

Patient care roadmap

Use this simple roadmap to understand the next safe steps. It is educational and does not replace examination by a doctor.

Go to emergency care if you notice:
  • Severe or rapidly worsening symptoms
  • Breathing difficulty, chest pain, fainting, confusion, severe weakness, major injury, or severe dehydration
Doctor / service to discuss: Qualified healthcare provider; specialist depends on symptoms and examination.
  1. Step 1

    Check danger signs first

    If danger signs are present, seek emergency care and do not wait for online information.

  2. Step 2

    Record the symptom story

    Write when symptoms started, severity, medicines already taken, allergies, pregnancy status, and test results.

  3. Step 3

    Visit a qualified clinician

    A doctor, nurse, or qualified healthcare provider can examine you and decide which tests or treatment are needed.

  4. Step 4

    Do only useful tests

    Do tests after clinical assessment. Avoid unnecessary tests, random antibiotics, or repeated medicines without diagnosis.

  5. Step 5

    Follow up and return early if worse

    If symptoms worsen, new warning signs appear, or treatment is not helping, return for review quickly.

Rural patient practical tips
  • Take a written symptom diary and all previous prescriptions/test reports.
  • Do not hide medicines already taken, even herbal or over-the-counter medicines.
  • Ask which warning signs mean urgent referral to hospital.

This roadmap is for education. A real diagnosis and treatment plan requires history, examination, and clinical judgment.

RX Patient Help

Ask a health question safely

Write your symptom story. A health professional or site editor can review it before any answer is prepared. This box is not for emergency care.

Emergency first: Severe chest pain, breathing trouble, unconsciousness, stroke signs, severe injury, heavy bleeding, or rapidly worsening symptoms need urgent local medical care now.

Frequently Asked Questions

The importance of ad-hoc queriesThere are plenty of business intelligence (BI) tools out there that provide dashboards with key metrics, but if you’re only looking at dashboards you’re missing out on all the insights that remain hidden inside your data. That’s why it’s important to be able to perform ad-hoc queries as well.Unfortunately, writing a valid SQL query that answers the question you’re trying to ask isn’t always easy. Even seemingly simple questions, like “Which of our customers makes us the most money?” can be very hard to answer, let alone convert into a SQL query. How do you define your customer cohorts? By age, location, behavioral patterns? Are you looking at how much customers spend on a single visit, or over their entire customer lifecycle?As more and more organizations try to integrate data into their decision-making processes, the ability of non-data specialists to write their queries can be the key to major gains in productivity and improved decision-making. Especially as functions that have traditionally been less data-driven, like Marketing and HR, begin to explore their data, employees need to be able to get answers to their questions promptly.The advantages (and the shortcomings) of visual query buildersLots of organizations turn to BI software to create dashboards with key performance indicators and other useful metrics. Some of these BI and visualization tools have begun offering support for more than just standard SQL queries, building drag-and-drop interfaces that allow people who don’t necessarily know how to structure a SQL query to get into the data.These tools work by connecting to a database and then allowing users to select what variables they want and then map them onto a graph or chart. Unfortunately, these tools have several shortcomings. A visual query builder may generate technically valid SQL, but the query itself may end up being too complex to run or risk bringing your server down in the process.Another shortcoming of visual query builders is that they still require users to know more or less what they’re asking for. To construct a query, you still have to manually select the right columns and input the appropriate conditions. In essence, the user still has to “convert” their question into terms a computer can understand even if they’re not writing the exact query.This may be fine if a user is working with a database they’re already familiar with, but what if Marketing wants to ask a question about detailed user behavior on the company’s iOS app? Or what if a user isn’t sure which columns or operations are appropriate?Looking to the future: Natural-language queriesWhat we’re asking here is how to convert natural human language into valid SQL queries. By itself, natural language processing (NLP) is one of the most challenging areas in AI research, and translating that question into a valid SQL query introduces a whole new layer of complexity. Still, there’ve been several efforts over the last few years to develop models that can do just that.Salesforce released a research paper in 2017 detailing a model called Seq2SQL that uses neural networks and reinforcement learning to create valid and accurate SQL queries out of human questions. Salesforce’s work was a big deal for two reasons. First, the model used reinforcement learning, meaning it will improve over time as more and more people use it. Already Seq2SQL has shown significant improvements over the previous state-of-the-art.Second, Salesforce has released a massive open source training set, WikiSQL, which it claims to be orders of magnitude larger than existing training sets. This way, other developers and researchers working on NLP interfaces can take advantage of a high-quality training set, saving them one of the most time-consuming and difficult steps of building and training an algorithm.So how does it work? Say we want to answer the question: “How many presidents since 1900 have won with less than 50% of the national popular vote?” Let’s say we’re using a database called presidential_elections, which looks something like this:Year President PopVoteRaw PopVotePer PopVoteMar Runner-up Turnout1824 John Q Adams 113,142 30.92 -38,221 Andrew Jackson 26.91828 Andrew Jackson 642,806 55.93 140,839 John Q Adams 57.31832 Andrew Jackson 702,735 54.74 228,628 Henry Clay 57.01836 Martin Van Buren 763,291 50.79 213,384 William Henry Harrison 56.5And so on. The model should recognize that the “presidents” in our question points to the “President” column, while “How many” indicates that we want the COUNT operation. Thus, the first part of our query should ideally look something like this:SELECT COUNT (President)FROM presidential_electionsNow’s the harder part. Hopefully, the model will be able to tell that “since 1900” and “with less than 50% of the popular vote” represent two separate conditions with greater than and less than operators, respectively. So hopefully, we’ll get a condition that looks something like:WHERE Year > 1900AND PopVotePer < 50;If all goes well, our query should return the correct answer: Nine.Looking for a data analyst?

For the moment, natural language-based query engines remain more of an intriguing concept than a practical reality. Until then, you may still want to turn to human data analysts for your querying needs. Fortunately, data analysis skills are increasingly widespread, and even junior-level data analysts should be able to produce ad hoc queries for a variety of database systems and create visualizations to help you interpret their findings.

References

Add references, clinical guidelines, textbooks, journal articles, or trusted medical sources here. You can edit this area from the RX Article Professional Blocks panel.