Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan
Pro*C Experience
00:00
5 left

Pro*C Experience

MediumSQL · PostgreSQL

Problem

Tell me about your experience with Pro*C.

For this hands-on SQL exercise, demonstrate the data-reporting aspect by writing a PostgreSQL query over the supplied Pro*C batch and error-log tables. Include eligible batches even when they have no matching errors.

Output

  1. One row per eligible batch, excluding batches before 2025-01-01, cancelled batches, and batches with a null status.
  2. Columns: batch_id, run_date, program_name, status, error_count, critical_error_count, rejected_rows.
  3. Order by run_date ascending, then batch_id ascending.

Schema

proc_batches
ColumnTypeDescription
batch_idPKINTIdentifier for the Pro*C batch execution
run_dateDATEDate on which the batch ran
program_nameVARCHAR(100)Name of the Pro*C executable
statusVARCHAR(20)Execution status
proc_errors
ColumnTypeDescription
error_idPKINTIdentifier for the logged error
batch_idINTBatch associated with the error
severityVARCHAR(20)Error severity
error_codeVARCHAR(30)Application or database error code
rejected_rowsINTNumber of rows rejected by the error
Tablesproc_batchesproc_errors
Interviewer

Your question is Pro*C Experience. Start with the requirements and the two tables in the Question tab.

Run and submit as often as you like. When you're ready, talk me through your approach or go straight to the code.

You need to log in / sign up to run or submit.
CodePostgreSQL
Sign up free to run your codeLog inLn 1
Run your query to see results here.