Database SoftwareCity & Guilds Limited End-Point Assessment Digital Skills & IT Revision

    This subtopic develops learners' ability to design and manage structured information using relational database software, a critical skill for roles requiri

    Topic Synopsis

    This subtopic develops learners' ability to design and manage structured information using relational database software, a critical skill for roles requiring data organisation, analysis, and reporting. Learners plan table structures to reflect real-world relationships, create and modify database objects, efficiently manipulate data, and use query and reporting tools to extract actionable insights, preparing them for administrative and technical workplace tasks.

    Key Concepts & Core Principles

    Exam Tips & Revision Strategies

    Common Misconceptions & Mistakes to Avoid

    Examiner Marking Points

    Database Software

    CITY & GUILDS LIMITED
    vocational

    This subtopic develops learners' ability to design and manage structured information using relational database software, a critical skill for roles requiring data organisation, analysis, and reporting. Learners plan table structures to reflect real-world relationships, create and modify database objects, efficiently manipulate data, and use query and reporting tools to extract actionable insights, preparing them for administrative and technical workplace tasks.

    20
    Learning Outcomes
    54
    Assessment Guidance
    58
    Key Skills
    18
    Key Terms
    61
    Assessment Criteria

    Assessment criteria

    City & Guilds Level 3 Award for IT Users (ITQ)
    City & Guilds Level 2 Diploma in IT User Skills
    City & Guilds Level 3 Diploma in IT User Skills
    City & Guilds Level 2 Award for IT Users (ITQ)
    City & Guilds Level 3 Certificate for IT Users (ITQ)
    City & Guilds Level 3 Diploma for IT Users (ITQ)
    City & Guilds Level 2 Diploma for IT Users (ITQ)
    City & Guilds Level 2 Certificate for IT Users (ITQ)
    City & Guilds Level 1 Diploma for IT Users (ITQ)
    City & Guilds Level 1 Award for IT Users - (ITQ)
    City & Guilds Level 1 Certificate for IT Users (ITQ)

    Topic Overview

    The City & Guilds Level 3 Award for IT Users (ITQ) is a vocational qualification designed to equip learners with advanced digital skills for the modern workplace. It covers a broad range of IT competencies, including word processing, spreadsheets, databases, presentation software, and using the internet securely. This qualification is ideal for those seeking to demonstrate proficiency in IT beyond basic use, preparing them for roles that require efficient and effective use of technology in business environments.

    This award is part of the ITQ framework, which is recognised by employers across the UK as a benchmark of practical IT skills. At Level 3, students are expected to work independently, solve complex problems, and apply advanced features of software applications. The qualification is structured into mandatory and optional units, allowing learners to tailor their studies to their career goals. Mastery of this award not only enhances employability but also builds confidence in using IT to increase productivity and streamline tasks.

    In the wider context of digital skills, this qualification bridges the gap between basic computer literacy and specialised IT certifications. It is particularly valuable for individuals in administrative, managerial, or technical support roles where advanced IT skills are essential. By completing this award, students demonstrate a deep understanding of how to leverage technology to achieve business objectives, making them valuable assets in any organisation.

    Key Concepts

    Core ideas you must understand for this topic

    • Advanced software features: Understanding and applying complex functions in word processing (e.g., mail merge, macros), spreadsheets (e.g., pivot tables, advanced formulas), and databases (e.g., queries, forms, reports).
    • Data security and GDPR: Knowing how to protect sensitive information, use secure passwords, encrypt data, and comply with data protection regulations in a business context.
    • Effective communication using IT: Using email, collaboration tools, and presentation software to convey information clearly and professionally, including managing attachments, calendars, and version control.
    • Problem-solving and troubleshooting: Identifying and resolving common IT issues, such as software errors, connectivity problems, and data corruption, using logical approaches and help resources.
    • Project management with IT: Planning, tracking, and reporting on tasks using software like Microsoft Project or Excel, including setting milestones, allocating resources, and monitoring progress.

    Learning Objectives

    What you need to know and understand

    • Plan, create and modify relational database tables to meet requirements, Enter, edit and organise structured information in a database, Use database software tools to create, edit and run data queries and produce reports
    • Plan, create and modify relational database tables to meet requirements, Enter, edit and organise structured information in a database, Use database software tools to create, edit and run data queries and produce reports
    • Create and modify non-relational database tables, Enter, edit and organise structured information in a database, Use database software tools to run queries and produce reports
    • Enter, edit and organise structured information in a database, Use database software tools to extract information and produce reports
    • Enter, edit and organise structured information in a database, Use database software tools to extract information and produce reports
    • Create and modify non-relational database tables, Enter, edit and organise structured information in a database, Use database software tools to run queries and produce reports
    • Plan, create and modify relational database tables to meet requirements, Enter, edit and organise structured information in a database, Use database software tools to create, edit and run data queries and produce reports
    • Plan, create and modify relational database tables to meet requirements
    • Enter, edit and organise structured information in a database
    • Use database software tools to create, edit and run data queries and produce reports
    • Design appropriate field properties and establish table relationships
    • Apply data validation techniques to maintain data integrity
    • Create and customise forms for efficient data entry
    • Develop reports with grouping and summary calculations
    • DBE:1 Enter, edit and organise structured information in a database, DBE:2 Use database software tools to produce reports
    • DBE:1 Enter, edit and organise structured information in a database, DBE:2 Use database software tools to produce reports
    • DBE:1 Enter, edit and organise structured information in a database, DBE:2 Use database software tools to produce reports
    • Create and modify non-relational database tables, Enter, edit and organise structured information in a database, Use database software tools to run queries and produce reports
    • Create and modify non-relational database tables, Enter, edit and organise structured information in a database, Use database software tools to run queries and produce reports
    • Enter, edit and organise structured information in a database, Use database software tools to extract information and produce reports

    Assessment Criteria

    Key criteria assessors look for in your portfolio

    • Award credit for demonstrating clear planning of database tables, including identification of necessary fields, primary keys, and appropriate data types to meet specified requirements.
    • Evidence should show ability to establish and enforce relationships between tables using foreign keys and referential integrity, ensuring data consistency.
    • Credit given for accurate data entry and editing, including use of validation rules, input masks, and lookup fields to maintain data quality.
    • Successful creation and execution of multi-table queries, such as parameter or action queries, with evidence of correct criteria and joins to fulfil information needs.
    • Reports must be professionally formatted with grouped data, calculated fields, and appropriate headers/footers, demonstrating ability to present information effectively for end users.
    • Award credit for demonstrating the ability to plan a relational database structure, including correctly identifying tables, fields, primary keys, and relationships based on given requirements.
    • Award credit for creating and modifying tables with appropriate data types, field properties, and validation rules.
    • Award credit for entering and editing data accurately, ensuring consistency and compliance with data integrity constraints.
    • Award credit for constructing and running queries using single or multiple criteria, sorting, and calculated fields as specified.
    • Award credit for generating reports that present summarised data with appropriate formatting, grouping, and professional layout.
    • Award credit for correctly creating a non-relational database table with appropriate field names, data types, and properties.
    • Award credit for accurately entering and editing records, demonstrating understanding of data validation and organisation.
    • Award credit for using query tools to filter, sort, and aggregate data according to specified criteria.
    • Award credit for producing clear, formatted reports that summarise queried data effectively.
    • Award credit for demonstrating accurate data entry into database tables with appropriate data types and field properties.
    • Award credit for editing existing records, modifying field values, and maintaining data consistency.
    • Award credit for organising data logically through meaningful table structures and establishing relationships.
    • Award credit for using database tools to extract specific information via filters or query criteria.
    • Award credit for producing formatted reports that summarise extracted data with appropriate headers, grouping, and sorting.
    • Award credit for correctly creating table structures with appropriate field names, data types, and a defined primary key.
    • Demonstrate accurate data entry and editing, including the use of forms for efficient record management.
    • Provide evidence of organising data, such as sorting on multiple fields and applying filters to display specific subsets.
    • Construct queries that use criteria, calculated fields, and logical operators to extract meaningful information.
    • Produce a well-designed report with grouping, sorting, and formatting that clearly communicates extracted data.
    • Award credit for demonstrating the ability to create a new database table with appropriate field types and properties, ensuring data integrity through validation rules.
    • Evidence of accurate data entry and editing, including the use of import tools or forms to maintain consistency.
    • Successful execution of queries with multiple criteria, and production of a formatted report that meets given requirements.
    • Award credit for demonstrating the ability to plan a relational database structure by identifying appropriate tables, fields, and primary keys with correct data types.
    • Credit should be given for accurately creating and modifying tables, including setting field properties such as validation rules and default values.
    • Evidence must show entry and editing of data with consistent formatting and organisation, including sorting and filtering records appropriately.
    • Marks are allocated for creating editable queries that extract specified data using correct criteria, joins, and calculated fields where required.
    • Award credit for generating professional reports that present summarised data clearly, with appropriate grouping, sorting, and layout formatting.
    • Award credit for demonstrating ability to create tables with appropriate data types and primary keys
    • Award credit for entering data accurately and using validation rules to restrict invalid entries
    • Award credit for constructing queries that correctly filter and sort data as per task brief
    • Award credit for generating a report that summarises data effectively, including grouping and totals
    • Award credit for modifying table structures, such as adding or deleting fields, without data loss
    • Award credit for accurately entering new records into a database table, completing all mandatory fields without errors.
    • Credit given for successfully editing an existing record to update specific fields, demonstrating the ability to locate and modify data correctly.
    • Credit for organising data by applying a single-field sort (ascending or descending) to arrange records logically.
    • Award credit for using the report wizard or design tool to generate a simple report that includes relevant fields, a clear title, and appropriate formatting.
    • Award credit for accurately entering data into correct fields without typographical errors, ensuring consistency and completeness.
    • Award credit for demonstrating the ability to edit and update existing records, including modifying field values and adding or deleting records as instructed.
    • Award credit for organising data using basic features such as sorting alphabetically or numerically, and applying simple filters to display specific subsets of information.
    • Award credit for generating a predefined report from the database, showing clear selection of report type and verification that all required fields are included and correctly formatted.
    • Award credit for demonstrating accurate data entry without typographical errors and consistent use of appropriate data types (e.g., text, number, date).
    • Award credit for editing existing records correctly, such as updating specific fields or correcting erroneous entries using appropriate navigation and editing tools.
    • Award credit for organising data using basic sorting or filtering functionalities, showing an understanding of how to structure information logically.
    • Award credit for generating a report that selects specific fields, applies a clear layout (e.g., headings, column widths), and is saved or printed appropriately.
    • Award credit for following given instructions precisely, including naming conventions, saving locations, and output requirements.
    • Award credit for demonstrating the ability to create a new database table with appropriate field names and data types, ensuring the table structure reflects the purpose of the data.
    • Award credit for entering and editing data accurately, including the use of basic data validation techniques to maintain data integrity.
    • Award credit for using database tools to sort and filter data based on specific criteria, and for generating a simple report that presents the data clearly.
    • Award credit for demonstrating the ability to create a table with appropriate field names and data types that match the intended data.
    • Credit accurate and consistent data entry, including the use of edits such as find and replace or sorting to organise information logically.
    • Expect clear evidence of running at least one query with specified criteria (e.g., filtering records) and generating a report that summarises or presents the query output professionally.
    • Award credit for demonstrating the ability to create a new database table with appropriate field names and data types.
    • Award credit for entering records accurately and editing existing data using form or datasheet view.
    • Award credit for using sorting and filtering tools to organise data meaningfully.
    • Award credit for designing a simple query to extract specific information based on given criteria.
    • Award credit for producing a formatted report that includes selected fields, grouped data, and a header/title.

    Assessment Guidance

    Guidance for achieving higher grades

    • 💡Always provide a design narrative or entity-relationship diagram as part of your planning evidence to demonstrate systematic thinking and meet assessment criteria for planning.
    • 💡Test all queries and reports with both typical and edge-case sample data before final submission to ensure they handle real-world scenarios correctly.
    • 💡Use validation rules and input masks consistently throughout your database to show advanced data entry skills and reduce marking deductions for data errors.
    • 💡Customise report layouts with logos, consistent fonts, and conditional formatting where appropriate, as examiners look for professional presentation indicative of workplace-ready outputs.
    • 💡Before starting, read the task brief carefully and sketch the required table structures and relationships on paper to avoid costly redesigns.
    • 💡Make use of the software's built-in 'relationships' window to visually confirm that all necessary links and referential integrity rules are applied.
    • 💡When creating queries, always switch to datasheet view to test and validate the output before moving on, ensuring it matches the specification exactly.
    • 💡For reports, pay attention to the assessment criteria regarding headers, footers, group levels, and formatting—these are easy marks if done correctly.
    • 💡Keep backups of your database file at different stages; if something goes wrong, you can revert to a previous version without losing all work.
    • 💡When creating tables, always define primary keys and set appropriate data types to prevent data inconsistency.
    • 💡Use sample data to test queries before applying them to the full dataset, ensuring expected output.
    • 💡In reports, include summaries and grouping where appropriate to enhance data presentation for assessors.
    • 💡Familiarise yourself with the specific database software (e.g., Microsoft Access) used in the assessment environment.
    • 💡Always plan your database structure by identifying fields, data types, and primary keys before starting data entry.
    • 💡Use consistent naming conventions for tables, fields, and reports to ensure clarity during assessment.
    • 💡Test queries with small data sets first to verify correct criteria and outputs before applying to the full database.
    • 💡Check report layouts carefully—ensure all required fields are included and the output is clearly formatted for intended users.
    • 💡Document your database design and query parameters as evidence of your understanding for the portfolio.
    • 💡Annotate all screenshots or evidence with notes on what was done and why, directly referencing the assessment criteria.
    • 💡Use descriptive names for all database objects (tables, queries, reports) to make the portfolio easy to navigate.
    • 💡When creating reports, customise headers, footers, and layouts to produce a polished, business-ready document.
    • 💡Test queries with a small subset of data first to verify they return expected results before using on larger datasets.
    • 💡Ensure that your database tables are well-structured with clear field names and appropriate data types, as this forms the basis of all subsequent tasks.
    • 💡Practice building queries using the software’s query builder or by writing simple commands, and always test with sample data to verify outputs before final submission.
    • 💡Always start by carefully reading the scenario or specification to identify required data entities and relationships before creating any tables.
    • 💡Use meaningful field names and consistent naming conventions to avoid confusion during queries and reporting.
    • 💡Test queries with different criteria to ensure they return correct results before saving them for evidence.
    • 💡When producing reports, consider the end-user: clear headings, aligned columns, and appropriate use of grouping and totals demonstrate advanced skills.
    • 💡Always read the task brief carefully to determine required table structures and relationships before starting
    • 💡Use meaningful field names and avoid spaces to prevent syntax errors in queries
    • 💡Test queries with a small dataset first to ensure correct logic before applying to full data
    • 💡Save reports in a suitable format for the intended audience, such as PDF for sharing
    • 💡Document any assumptions made during database design in your assessment evidence
    • 💡Carefully review the assignment brief to identify exactly which fields must appear in reports and any sorting or filtering conditions required.
    • 💡Always verify data entries against provided source documents before submitting evidence to avoid avoidable errors.
    • 💡Use the print preview function before finalising a report to check that all columns fit on the page and the layout is clear and professional.
    • 💡Remember that some edits (like bulk updates) may not be undoable; pause and confirm critical changes to avoid irreversible mistakes.
    • 💡Always double-check each data entry against the source document to avoid transposition errors and ensure full marks for accuracy.
    • 💡When asked to produce a report, first verify that the underlying data is correct and complete; then preview the report before final submission to catch any layout issues.
    • 💡Follow task instructions precisely—if an objective requires editing a specific record, ensure that record is selected and changes are confirmed before moving on.
    • 💡Use the software's help function or task pane if unsure about a feature, as basic proficiency in navigating the interface is part of the assessment.
    • 💡Read the assignment brief thoroughly before starting; highlight keywords like 'sort', 'filter', 'report', and 'specific layout' to ensure you meet all criteria.
    • 💡Always double-check your data entry against the source information, and use the software’s built-in validation or spell-check if available.
    • 💡When generating a report, plan its content first: decide which fields to include, what sorting/filtering is needed, and how it should look on paper.
    • 💡Practise common tasks such as creating a simple query, adjusting column widths, and adding a title to a report to build fluency under assessment conditions.
    • 💡Save your work frequently and keep backups; if you make a mistake, use ‘undo’ rather than starting over.
    • 💡Always double-check data entry for accuracy and consistency before submitting, as even minor typographical errors can lead to lost marks.
    • 💡Save your work regularly and use descriptive names for tables, queries, and reports to make your assessment evidence clear.
    • 💡When creating queries, test them with different criteria to ensure they return the expected results; this demonstrates understanding of filtering logic.
    • 💡Always plan your table structure before opening the software: list required fields, decide on data types, and note any validation rules needed.
    • 💡When constructing queries, test them step by step with simple criteria first; then gradually add complexity to ensure accuracy.
    • 💡For reports, pay attention to header/footer details and grouping options—examiners look for a well-presented, professional output, not just raw data.
    • 💡When completing assignments, always label your evidence clearly and include screenshots showing step-by-step use of database features to meet all criteria.
    • 💡Before generating a report, verify that your query returns the correct records and that sorting/filtering is applied appropriately to present information as required by the task.
    • 💡Always read the task instructions carefully. Many students lose marks by not following specific formatting requirements or by missing key steps. Underline the action words like 'create', 'modify', 'analyse', and 'present' to ensure you address each part.
    • 💡Use the help function within software applications. In the exam, you are allowed to use built-in help, so if you forget a step, use it rather than guessing. This demonstrates resourcefulness and can save time.
    • 💡Save your work regularly and check file names. Examiners often see incomplete work due to crashes or incorrect file saving. Use the 'Save As' function to create backups and ensure your final file is correctly named as per the instructions.

    Common Mistakes

    Common errors to avoid in your coursework

    • Confusing data types, e.g., storing numeric identifiers as text, which prevents proper sorting, calculation, or relationship enforcement.
    • Failing to normalise tables, leading to data redundancy, update anomalies, and inefficient storage without recognising the importance of atomic fields.
    • Ignoring referential integrity when creating relationships, resulting in orphaned records or inconsistent data across related tables.
    • Using 'all-in-one' query approaches instead of building structured queries, often leading to incorrect results or performance issues with large datasets.
    • Neglecting to save queries and reports with descriptive names and proper documentation, making maintenance and assessment evidence difficult to locate.
    • Selecting incorrect data types, such as using a 'Text' field for numerical IDs, which leads to sorting and calculation errors.
    • Failing to establish relationships and enforce referential integrity, resulting in orphaned records and data inconsistencies.
    • Manually entering data into lookup fields rather than using subforms or the related table, causing data not to appear correctly in relationships.
    • Misapplying wildcard characters in query criteria, e.g., using '=' instead of 'LIKE' or forgetting the '%' / '*' symbol.
    • Overlooking the need to save both queries and reports with descriptive names, causing confusion during assessment evidence capture.
    • Confusing non-relational (flat-file) tables with relational databases involving multiple linked tables.
    • Entering data without adhering to defined field types, leading to validation errors.
    • Using inappropriate criteria in queries, producing irrelevant or incomplete results.
    • Neglecting to format reports for readability, such as including titles or column headers.
    • Entering inconsistent data formats (e.g., mixing date styles) which causes query and reporting errors.
    • Failing to define primary keys, leading to duplicate records and inefficient data retrieval.
    • Overlooking the need to validate input data against set criteria before running queries.
    • Confusing the functions of filters versus queries—using filters for simple, quick filtering but queries for complex, saved extractions.
    • Producing reports that lack clear structure or headings, making them unusable for business purposes.
    • Choosing an unsuitable field as the primary key, such as a name that may not be unique, leading to data integrity issues.
    • Inconsistent data entry (e.g., variations in spelling or date formats) causing inaccurate query results.
    • Editing records without considering referential integrity, resulting in orphaned records or broken relationships.
    • Confusing the purpose of queries and reports, attempting to format data in a query instead of a report.
    • Forgetting to back up the database before performing bulk operations, risking data loss.
    • Confusing non-relational with relational database concepts, leading to improper table design or unnecessary relationships.
    • Entering data without adhering to defined field constraints, causing errors and inconsistencies.
    • Misunderstanding query logic, particularly when using AND/OR conditions, which can produce incorrect result sets.
    • Confusing flat-file and relational database concepts, leading to redundant data and lack of table relationships.
    • Incorrect data type assignment (e.g., using text for numeric fields) causing query or calculation errors.
    • Failing to enforce referential integrity when establishing table relationships, resulting in orphan records.
    • Writing query criteria with logical errors, such as using 'AND' instead of 'OR' or missing wildcards in pattern matching.
    • Neglecting to preview and adjust report formatting, leading to cut-off data or unprofessional presentation.
    • Not setting a primary key when creating tables, leading to data redundancy and query errors
    • Entering inconsistent data due to lack of validation rules
    • Creating queries that return incorrect results because of misunderstanding of criteria operators (AND/OR)
    • Failing to update related tables when modifying data, causing orphan records
    • Believing that closing a form or table automatically saves a new record; learners must explicitly save or move to a new record to commit changes.
    • Accidentally deleting a record when attempting to clear a field, often due to confusion between record deletion and field editing functions.
    • Not verifying entered data against source documents, leading to transposition errors or incomplete information.
    • Producing a report that includes all table fields indiscriminately rather than selecting only those required by the task, resulting in cluttered and unprofessional output.
    • Failing to save changes after editing records, leading to loss of data and incomplete assessment evidence.
    • Entering data into the wrong field (e.g., placing a surname in the first name column), which disrupts the database structure.
    • Not understanding the difference between field types (text, number, date), resulting in incorrect formatting and potential sorting errors.
    • Producing reports that omit necessary fields or include extraneous details because of not selecting the correct report template or range.
    • Misunderstanding data types, leading to incorrect data entry (e.g., entering text into a numeric field or using inconsistent date formats).
    • Accidentally overwriting or deleting records while attempting to edit due to not using proper find-and-edit techniques.
    • Confusing sorting with filtering; applying a sort when a filter is needed, resulting in only reordered rather than subsetted data.
    • Generating a report that includes unnecessary fields or omits required ones, and failing to check print preview before submission.
    • Saving files with incorrect names or in the wrong location, causing evidence to be misplaced.
    • Students often confuse database tables with spreadsheets, failing to appreciate the structured, record-based nature of databases.
    • Learners commonly forget to define appropriate data types for fields, leading to data entry errors and inefficient queries.
    • A frequent mistake is neglecting to save changes or overwriting important data without backup, losing progress.
    • Choosing inappropriate data types, such as using a text field where a number or date field would allow validation and sorting.
    • Failing to proofread entered data, leading to inconsistencies—for instance, typing 'London' and 'london' which affects sorting and query results.
    • Confusing queries with reports: learners may try to print a query datasheet instead of using the report generator to format headings and layout.
    • Entering inconsistent or incomplete data, such as missing required fields or entering text in numeric fields.
    • Confusing the purpose of sorting (temporary arrangement) with the permanent structure of the database.
    • Failing to save queries before attempting to generate reports, leading to missing or incorrect data in the output.
    • Misconception: 'Level 3 ITQ is just about knowing how to use Microsoft Office.' Correction: While Office applications are central, the qualification also covers internet safety, legal and ethical use of IT, and advanced features that require critical thinking and problem-solving, not just basic operation.
    • Misconception: 'I can pass by memorising steps without understanding why.' Correction: The assessment requires you to apply skills to unfamiliar scenarios. You must understand the purpose behind each action, such as why a particular formula is used or how a database query retrieves specific data.
    • Misconception: 'Data security is just about having a strong password.' Correction: Data security encompasses encryption, access controls, regular backups, and understanding phishing threats. The qualification expects you to implement a range of security measures appropriate to different situations.

    Frequently Asked Questions

    Common questions students ask about this topic

    Before You Start

    Prior knowledge that will help with this topic

    • Basic IT literacy: Familiarity with using a computer, operating system (e.g., Windows), and common software applications like word processors and spreadsheets at a foundational level.
    • Understanding of file management: Ability to create, save, organise, and retrieve files and folders, as well as knowledge of different file formats (e.g., .docx, .xlsx, .pdf).
    • Numeracy and literacy skills: Competence in basic maths (e.g., percentages, averages) and English (e.g., spelling, grammar) to effectively use software features and produce professional documents.

    Key Terminology

    Essential terms to know

    • Plan, create and modify relational database tables to meet requirements, Enter, edit and organise structured information in a database, Use database software tools to create, edit and run data queries and produce reports
    • Plan, create and modify relational database tables to meet requirements, Enter, edit and organise structured information in a database, Use database software tools to create, edit and run data queries and produce reports
    • Create and modify non-relational database tables, Enter, edit and organise structured information in a database, Use database software tools to run queries and produce reports
    • Enter, edit and organise structured information in a database, Use database software tools to extract information and produce reports
    • Enter, edit and organise structured information in a database, Use database software tools to extract information and produce reports
    • Create and modify non-relational database tables, Enter, edit and organise structured information in a database, Use database software tools to run queries and produce reports
    • Plan, create and modify relational database tables to meet requirements, Enter, edit and organise structured information in a database, Use database software tools to create, edit and run data queries and produce reports
    • Relational table design
    • Data entry and organisation
    • Query building and execution
    • Report production
    • Data integrity and validation
    • DBE:1 Enter, edit and organise structured information in a database, DBE:2 Use database software tools to produce reports
    • DBE:1 Enter, edit and organise structured information in a database, DBE:2 Use database software tools to produce reports
    • DBE:1 Enter, edit and organise structured information in a database, DBE:2 Use database software tools to produce reports
    • Create and modify non-relational database tables, Enter, edit and organise structured information in a database, Use database software tools to run queries and produce reports
    • Create and modify non-relational database tables, Enter, edit and organise structured information in a database, Use database software tools to run queries and produce reports
    • Enter, edit and organise structured information in a database, Use database software tools to extract information and produce reports

    Ready to learn?

    AI-powered learning tailored to this unit