Database Software
This subtopic introduces learners to fundamental database software skills, focusing on accurately entering, editing, and organising structured data. It covers the use of basic database tools to extract targeted information through queries and to produce formatted reports for effective data presentation and decision-making. Practical application includes managing simple contact lists or inventory records in a vocational context.
Assessment criteria
Quick Revision Summary (Key Takeaway)
The TLM Level 2 Certificate in IT User Skills in Open Systems and Enterprise (ITQ) covers practical digital skills for the modern workplace, including word processing, spreadsheets, databases, presentations, and safe internet use. This qualification focuses on applying IT tools to real-world tasks, with assessment through portfolio evidence and online tests, preparing learners for employment or further study.
Topic Overview
The TLM Level 2 Certificate in IT User Skills in Open Systems and Enterprise (ITQ) is a vocational qualification that equips learners with essential digital competencies for the workplace. It covers a range of software applications, including word processing, spreadsheets, databases, presentations, and email, as well as safe and responsible use of IT. The qualification is assessed through a portfolio of evidence and online multiple-choice tests, making it practical and relevant to real-world tasks.
This qualification is important because it demonstrates to employers that you can use IT effectively to solve problems, communicate, and manage data. It is recognised across the UK and provides a solid foundation for further study in IT or for entering the workforce. The skills you learn, such as creating professional documents, analysing data with spreadsheets, and designing engaging presentations, are directly applicable to many job roles.
The course is structured around units that reflect common IT tasks, such as 'Word Processing Software', 'Spreadsheet Software', and 'Using Email'. Each unit requires you to complete tasks that are assessed against national standards. By the end of the course, you will have a portfolio of work that shows your ability to use IT in a business context, which is a valuable asset for job applications and career progression.
Key Concepts
Core ideas you must understand for this topic
- →File management: organising, saving, and retrieving files in different formats (e.g., .docx, .xlsx, .pdf).
- →Word processing: formatting text, using styles, inserting tables and images, and mail merge.
- →Spreadsheets: using formulas and functions (SUM, AVERAGE, IF), creating charts, and data sorting/filtering.
- →Databases: designing tables, queries, forms, and reports to manage information.
- →Presentations: creating slides with multimedia, transitions, and effective design principles.
Learning Objectives
What you need to know and understand
- Enter data accurately into a database table.
- Edit existing records to update or correct information.
- Organise records by sorting and filtering data based on given criteria.
- Extract specific information from a database using simple query tools.
- Produce a formatted report from query results.
- Apply basic data validation to ensure accuracy of entries.
- Enter, edit and organise structured information in a database, Use database software tools to extract information 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 non-relational database tables by defining appropriate field types and properties
- Enter and edit data accurately in database tables, ensuring consistency and completeness
- Organise structured information by sorting, filtering, and grouping data for analysis
- Run simple and complex queries to retrieve specific data subsets
- Produce formatted reports that summarise and present database information clearly
- Apply data validation techniques to minimise errors during data input
- 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
- Enter, edit and organise structured information in a database, Use database software tools to extract information and produce reports
- DBE:1 Enter, edit and organise structured information in a database, DBE:2 Use database software tools to 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 a non-relational database table with appropriate field names and data types
- Modify an existing table structure by adding or deleting fields as required
- Enter data accurately into a database table, ensuring consistency and completeness
- Edit and update records to correct errors and maintain data quality
- Organize data using sorting and filtering features to meet specified criteria
- Construct simple queries to retrieve specific information from a database
- Generate formatted reports from query results that display selected fields and summary information
- 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
- Identify different types of database objects (tables, queries, forms, reports).
- Enter data into a database table accurately and efficiently.
- Edit existing records to maintain up-to-date information.
- Organise data by sorting and filtering records based on specified criteria.
- Use database software tools to create and run simple queries.
- Produce formatted reports from extracted data.
- Explain the importance of data integrity and validation.
Assessment Criteria
Key criteria assessors look for in your portfolio
- Award credit for entering data without typographical errors and in the correct fields.
- Credit should be given for using appropriate data types (e.g., text, number, date) when editing fields.
- Award marks for successfully sorting records alphabetically or numerically as required.
- Evidence of applying filter criteria to display a subset of records correctly.
- Credit for generating a report that includes specified fields and has a clear title and consistent formatting.
- Marks for demonstrating checks, such as reviewing data for obvious inaccuracies.
- Award credit for demonstrating accurate data entry into appropriate fields, maintaining consistency and data integrity.
- Credit should be given for successfully locating and editing existing records, such as updating details or correcting errors without corrupting other data.
- Look for evidence of using basic sorting or filtering functions to organize data in a logical manner, such as alphabetical or numerical order.
- Assess the ability to use simple query or search tools to extract specific records based on a single criterion.
- Check that the learner can produce a basic report (e.g., a table listing or summary) that includes relevant fields and is formatted legibly for printing or sharing.
- Award credit for demonstrating a clear database plan that identifies required tables, fields, data types, and primary/foreign keys aligned to the given requirements.
- Expect evidence of creating and modifying table structures, including adding, editing, and deleting fields, and setting validation rules to maintain data integrity.
- Look for accurate and consistent data entry, with records organised appropriately (e.g., sorted, filtered) and evidence of editing to correct errors or update information.
- Assess the ability to construct effective queries using multiple criteria, joins, and calculated fields, and to produce well-formatted reports that summarise or present data as specified.
- Award credit for creating tables with correctly defined data types (text, number, date, etc.)
- Evidence of entering at least a specified number of records accurately
- Use of editing functions to modify existing data fields without introducing inconsistencies
- Successful construction of a query with correct criteria to filter data
- Generation of a report that includes appropriate headers, sorting, and grouping
- Demonstration of understanding of non-relational structure (e.g., flat file) through selection of appropriate fields
- Award credit for demonstrating a clear database design plan that includes entities, attributes, and relationships, showing understanding of primary and foreign keys.
- Award credit for accurately creating database tables with appropriate data types and field properties, reflecting the planned design.
- Award credit for entering and editing records consistently, demonstrating data validation techniques where required.
- Award credit for constructing queries using multiple criteria, joins, and calculated fields to extract specified information.
- Award credit for producing well-formatted reports that summarise query results, including grouping, sorting, and appropriate headers/footers.
- Award credit for demonstrating the consistent and accurate entry of data into predefined fields, with zero typographical errors in critical identifiers.
- Look for evidence of data organisation using appropriate data types, primary keys, and table relationships to maintain referential integrity.
- Credit should be given for designing and executing queries with correctly applied criteria, sorting, and joins to retrieve specific data subsets.
- Assess reports against criteria: inclusion of headers, grouping, sorting, calculated fields where necessary, and professional formatting for intended purpose.
- Award credit for accurately entering a new record into a table, with all mandatory fields completed and data types correctly applied.
- Award credit for demonstrating effective editing, including modifying an existing record and using undo/redo features appropriately.
- Award credit for successfully sorting or filtering data in a table or query to organise information according to a given brief.
- Award credit for demonstrating the creation of tables with appropriate data types and field properties (e.g., primary keys, validation rules) that align with documented requirements.
- Award credit for accurately establishing relationships between tables (e.g., one-to-many) and enforcing referential integrity.
- Award credit for producing queries that correctly filter, sort, and combine data from multiple tables to meet specified criteria.
- Award credit for generating reports that present queried data in a clear, formatted layout suitable for the intended audience.
- Evidence of creating a table with at least three fields and appropriate data types (e.g., text, number, date)
- Demonstration of adding, deleting, and editing records with correct use of navigation and save functions
- Application of sorting and filtering tools to organize data logically, with screenshots or annotations
- Correct execution of a query with at least one criterion, showing the output
- Production of a report that includes only relevant fields, a clear title, and professional formatting
- Consistent and accurate data entry, with minimal typographical errors and adherence to specified formats
- Award credit for demonstrating accurate data entry with consistent formatting and use of appropriate data types.
- Award credit for correctly editing existing records and organising data using features like sorting and filtering.
- Award credit for producing a well-structured report that extracts relevant data, with clear headings and formatting.
- Award credit for showing understanding of data integrity principles, such as avoiding duplicate entries and verifying accuracy.
- Award credit for demonstrating the ability to create a new non-relational database table with appropriate field names and data types (e.g., text, number, date) that align with a given purpose.
- Evidence should show accurate data entry, including using import tools or manual entry, with no typographical errors that compromise data integrity.
- When modifying a table, credit for correctly adding/deleting fields, changing data types, or adjusting field properties without corrupting existing data.
- For queries, award credit for constructing and executing at least one simple query (e.g., filter, sort) that extracts specified records, and saving it appropriately.
- Reports must be generated from queries or tables, with evidence of selecting layout, sorting, and applying basic formatting to present data clearly.
- Award credit for correctly creating a table with appropriate field names and data types.
- Award credit for accurately entering at least 10 records without errors.
- Award credit for demonstrating the ability to edit a specific record as per instructions.
- Award credit for successfully applying a filter to display only records meeting given criteria.
- Award credit for creating a query that extracts relevant data from multiple fields.
- Award credit for generating a report that includes a title, column headings, and sorted data.
Assessment Guidance
Guidance for achieving higher grades
- 💡Always double-check each entry against the source data before moving to the next record.
- 💡Practice building simple queries step-by-step, testing them with small datasets first.
- 💡When producing a report, use the print preview to ensure all required fields are visible and neatly aligned.
- 💡Save the database file frequently and back it up before performing bulk edits or deletions.
- 💡Use a systematic approach: enter data first, verify, then organise, query, and finally report.
- 💡In portfolio-based assessments, include annotated screenshots that clearly show the process of entering, editing, and organizing data, not just the final outcomes.
- 💡When extracting information, use simple, single-criterion queries—practise building them step by step to avoid syntax errors.
- 💡Always use the preview function before printing or saving a report to check that all necessary fields are visible and correctly aligned.
- 💡Demonstrate a clear understanding of database structure by naming fields logically and keeping related data together in one table.
- 💡Save work frequently and maintain backup copies; evidence of version control can strengthen your portfolio and show safe working practices.
- 💡For report production, select only the fields that are relevant to the task, and use the software’s default formatting tools rather than manual layout adjustments to ensure consistency.
- 💡Always start by reading the scenario thoroughly to identify the required outputs before designing your database structure.
- 💡During the planning phase, sketch out an entity relationship diagram (ERD) to visualise table relationships and validate with the assessor if possible.
- 💡When creating queries, build them step-by-step, testing each part before adding complexity, and save working versions as backups.
- 💡For reports, use the software’s built-in grouping and sorting features to automatically organise data, and preview before finalising to ensure the layout meets the brief.
- 💡For the assessment, ensure you practice creating tables with various field types and test data entry for consistency.
- 💡Use clear, consistent naming conventions for fields and tables to make queries easier to construct.
- 💡Always preview your reports before finalising; check that sorting and grouping are logical and enhance readability.
- 💡When running queries, double-check your criteria; test with known data to verify they return expected results.
- 💡Manage your file saves and backups: keep a clean master copy in case you need to revert after editing.
- 💡Always begin with a clear requirements analysis and sketch an entity-relationship diagram before building tables.
- 💡Use consistent naming conventions for tables and fields to enhance clarity and maintainability.
- 💡Test queries with sample data to verify results before finalising your submission.
- 💡Ensure reports directly address the business need by including only relevant fields and summarisations.
- 💡Document any assumptions and design decisions, as assessors may credit reasoning even if minor errors exist.
- 💡Always begin by planning the database structure on paper, identifying entities, fields, and relationships before creating anything digitally.
- 💡When extracting data for reports, verify query results against a manual sample count to ensure criteria are correctly filtering records.
- 💡Use the report wizard initially, then modify the design view to precisely meet the specifications of the task—this saves time and reduces errors.
- 💡Save queries with descriptive names and test them thoroughly; if a report is based on a query, ensure the query runs as expected first.
- 💡Before producing a report, always preview the report layout to check that all fields appear correctly and any grouping or sorting matches the task requirements.
- 💡Use simple query wizards to extract only the needed data for a report, rather than building a report from an entire table, saving time and reducing errors.
- 💡Always review the scenario and define all required fields and relationships before starting to build the database; annotate your plan to show normalisation steps.
- 💡When constructing queries, test each clause incrementally (e.g., first the SELECT, then the WHERE, then the ORDER BY) to isolate errors.
- 💡Save and name all database objects (tables, queries, reports) clearly and consistently, as assessors will check for a logical naming convention.
- 💡Practice hands-on with the exact database software version you will be assessed on to build familiarity
- 💡Double-check all data entry for accuracy and consistency before submitting evidence as screenshots or files
- 💡Read query requirements carefully—note whether they ask for an exact match, a range, or a pattern (e.g., 'starts with')
- 💡Use clear, descriptive field names and avoid spaces or special characters to prevent software issues
- 💡For your portfolio, save evidence of each stage: table design, data entry, query results, and final report
- 💡When generating reports, ensure you select only the fields needed and apply sorting if specified in the task
- 💡Always double-check data entry against source documents to minimise errors before submission.
- 💡Plan your report layout by identifying the key fields required, then use the software's reporting tools to generate and refine the output.
- 💡Practice using 'query by example' or filtering to extract only necessary data, demonstrating efficient use of the software.
- 💡Show an understanding of data protection by anonymising personal data in evidence unless specifically permitted by the assessment.
- 💡When creating tables, always plan the structure on paper first: define field names, data types, and any validation rules to meet the scenario requirements.
- 💡For queries, test them against known data to ensure they return correct results; document your query criteria to demonstrate understanding.
- 💡In reports, use descriptive headers and footers, and ensure the report title reflects the data source and purpose; this shows professional presentation skills.
- 💡Check your work for consistency: e.g., all dates in same format, no blank required fields, to maximize marks for data quality.
- 💡Familiarise yourself with the software interface before the assessment to reduce anxiety.
- 💡Practice creating queries using the query wizard and design view.
- 💡Check all data entries for spelling and consistency before final submission.
- 💡Read the assignment brief carefully to ensure the report format matches the requested layout.
- 💡Use print preview to verify the report appearance before printing or submitting.
- 💡Always save your work regularly and in the correct format. In the exam, you may be asked to submit files in a specific format, so check the instructions carefully.
- 💡When answering questions about software features, use the correct terminology (e.g., 'cell reference', 'primary key', 'slide transition') to show your knowledge.
- 💡For portfolio evidence, include screenshots with annotations to explain what you did and why. This helps the assessor see your thought process.
Common Mistakes
Common errors to avoid in your coursework
- Forgetting to save changes after editing records, leading to lost data.
- Entering data in the wrong field (e.g., putting a name in an address field).
- Misunderstanding data types and entering letters in numeric-only fields, causing errors.
- Using query criteria incorrectly, resulting in empty or inaccurate result sets.
- Producing reports that lack clear titles or include irrelevant data.
- Confusing the 'sort' and 'filter' functions and applying the wrong method to organise data.
- Entering data into incorrect fields, causing mismatches and data inconsistencies across records.
- Forgetting to save changes after editing records, resulting in lost updates and incomplete evidence.
- Confusing sorting with filtering, which leads to unintended data arrangements or hidden records.
- Producing reports that omit key fields or include all records when only a subset is required, showing misunderstanding of extraction criteria.
- Attempting to use complex querying or reporting features beyond the Entry 3 scope, leading to errors and frustration.
- Not verifying the accuracy of extracted information before presenting it, resulting in reports that contain mistakes.
- Failing to normalise data, leading to redundant fields and inconsistent information across tables.
- Not setting appropriate data types or field sizes, causing data entry errors or wasted storage.
- Confusing primary keys with foreign keys when establishing relationships, resulting in incorrect table links.
- Overlooking the need to test queries with different datasets, leading to inaccurate or incomplete results.
- Neglecting to include headers, grouping, or summary options in reports, making them unsuitable for their intended purpose.
- Misunderstanding the difference between data types, leading to inappropriate field selections (e.g., using text for numeric values that need calculations)
- Inconsistent data entry, such as spelling errors or variable formats (e.g., dates typed differently)
- Confusing queries with tables; attempting to edit data directly in a query output rather than the table
- Generating reports that include unnecessary fields or lack proper grouping, making them hard to interpret
- Overlooking data validation features that can prevent errors before data entry
- Saving multiple versions of the same database file and working on the wrong one
- Confusing flat file and relational database concepts, leading to data redundancy and update anomalies.
- Neglecting to normalise tables beyond first normal form, causing inefficiencies.
- Using inappropriate data types (e.g., text for numeric fields), which hinders accurate querying and calculations.
- Misapplying join types when building queries, resulting in incorrect record sets.
- Focusing on aesthetics over clarity in reports, such as omitting descriptive titles or using cluttered layouts.
- Entering data directly into spreadsheets instead of using forms, leading to inconsistent formatting and accidental overwrites.
- Using text fields for numeric or date data, preventing proper sorting, filtering, and calculations in queries and reports.
- Forgetting to set primary keys or relationships, resulting in data redundancy and inability to link tables effectively.
- Designing queries with incorrect logical operators (e.g., AND instead of OR), thus returning inaccurate or empty result sets.
- Learners often confuse data types when entering information, such as inputting text where a number or date is required, leading to validation errors.
- When editing, learners may select entire cells instead of placing the cursor correctly, inadvertently overwriting or deleting data without realising.
- Failing to normalise tables, leading to redundant data storage and update anomalies.
- Confusing data types (e.g., storing numeric data as text) which prevents correct sorting and calculations.
- Forgetting to set a primary key or unique identifier, making it impossible to enforce relationships.
- Writing queries that return incomplete results due to incorrect join types or missing criteria.
- Forgetting to save changes before closing the database, leading to lost work
- Data entry errors such as typos, inconsistent date formats, or missing required fields
- Selecting incorrect data types for fields (e.g., using 'Text' for numbers that will be calculated)
- Confusing queries with filters—expecting a filter to produce a separate output or a query to be temporary
- Generating a report that includes all fields and records without applying query criteria or layout design
- Not understanding the difference between a non-relational flat table and a relational database with multiple linked tables
- Entering data in inconsistent formats (e.g., dates as text) which hinders sorting and reporting.
- Failing to use appropriate data types (e.g., numeric fields for amounts) leading to calculation errors.
- Overlooking simple filtering and sorting options, resulting in manual scanning of records instead of efficient data analysis.
- Producing reports with excessive or irrelevant fields, making the output unclear and unprofessional.
- Confusing non-relational (flat-file) with relational databases, attempting to link tables without understanding relationships, leading to data integrity issues.
- Neglecting to set appropriate primary keys or unique identifiers, resulting in difficulty managing and retrieving specific records.
- Assuming that reports automatically update when underlying data changes; not realising that many non-relational tools require re-running queries or reports.
- Typing errors in data entry, especially inconsistent date formats or numeric values with wrong decimal separators, which cause query failures or inaccurate reports.
- Misunderstanding the difference between a field and a record.
- Entering data inconsistently (e.g., mixing date formats).
- Forgetting to save the database file after making changes.
- Applying incorrect filter criteria, resulting in no data displayed.
- Confusing the query design view with the datasheet view.
- Producing reports that do not include all requested fields.
- Misconception: 'ITQ is just about using Microsoft Office.' Correction: While Office is common, the qualification covers open-source alternatives like LibreOffice and focuses on transferable skills, not specific software.
- Misconception: 'Copying and pasting from the internet is fine as long as you change a few words.' Correction: Plagiarism is not acceptable; you must create original work and reference sources properly.
- Misconception: 'Spreadsheet formulas are only for maths experts.' Correction: Basic formulas are simple and logical; you just need to understand cell references and functions.
Revision Plan
How to revise this topic in 1–2 weeks
- 1Week 1: Focus on word processing and file management. Practice creating documents with formatting, tables, and images. Save files in different formats and organise them in folders.
- 2Week 2: Move to spreadsheets. Learn basic formulas (SUM, AVERAGE), cell referencing, and chart creation. Practice using absolute references and conditional formatting.
- 3Week 3: Study databases and presentations. Create a simple database with tables and queries, and design a presentation with slides, transitions, and embedded media.
- 4Week 4: Review all topics, complete practice tests, and compile your portfolio. Identify weak areas and revisit them.
Exam Question Types
How this topic typically appears in the exam
- 📋Multiple-choice questions: These test your knowledge of software features and terminology. Read each question carefully and eliminate obviously wrong answers.
- 📋Scenario-based tasks: You are given a scenario (e.g., 'You need to create a newsletter for a club') and asked to describe the steps you would take. Use a logical order and mention specific tools.
- 📋Practical portfolio tasks: You must produce evidence of completing tasks, such as a spreadsheet with formulas or a presentation. Ensure your work is neat and annotated.
- 📋Short-answer questions: These ask for definitions or explanations, e.g., 'What is a primary key in a database?' Give a clear, concise answer with an example.
Command Word Expectations (THE LEARNING MACHINE)
What examiners look for when using specific command words in this specification
Give a detailed account of the features or steps involved. For example, 'Describe how to insert a chart in a spreadsheet' requires you to list the steps in order, mentioning the Insert tab, chart types, and data selection.
Give reasons or causes. For example, 'Explain why absolute cell references are useful' requires you to state that they prevent changes when copying formulas, and give an example.
Weigh up the pros and cons. For example, 'Evaluate the use of cloud storage for a small business' requires you to discuss advantages (accessibility, collaboration) and disadvantages (internet dependency, security), and give a conclusion.
How Students Lose Marks (Examiner Pitfalls)
Common mark loss traps and how to write 100% full-mark answers
Step-by-Step Worked Solutions
Detailed solution breakdown for typical exam problems
Question: You have a spreadsheet with sales data for each month in column A (months) and column B (sales). In cell C1, you have a target of £5000. Write a formula to calculate the difference between each month's sales and the target, and explain how you would format the result to show positive differences in green and negative differences in red.
- 1.Step 1: Identify the cell references: sales are in B2:B13, target is in C1.
- 2.Step 2: Use a formula that subtracts the target from each sales figure: =B2-$C$1 (use absolute reference for C1).
- 3.Step 3: Copy the formula down for all months.
- 4.Step 4: Apply conditional formatting to the result column: select the range, choose 'Highlight Cells Rules' > 'Greater Than' for 0 (green) and 'Less Than' for 0 (red).
Question: You need to create a presentation for a school project. Describe how you would insert a chart from a spreadsheet into a slide and ensure it updates automatically if the spreadsheet data changes.
- 1.Step 1: Create the chart in the spreadsheet (e.g., a bar chart of exam results).
- 2.Step 2: In PowerPoint, go to the slide where you want the chart, click 'Insert' > 'Object' > 'Create from file', and select the spreadsheet file.
- 3.Step 3: Tick the 'Link' checkbox to create a link to the source data.
- 4.Step 4: If the spreadsheet data changes, right-click the linked object in PowerPoint and choose 'Update Link' to refresh the chart.
Active Recall Memory Test
Test your memory before revealing the key facts
Frequently Asked Questions
Common questions students ask about this topic
Pass / Merit / Distinction Evidence Checklist
How your portfolio evidence is graded for THE LEARNING MACHINE Database Software
Every vocational unit is marked against named criteria rather than an exam percentage. Your tutor's brief lists the exact codes for this unit — here is what each band is asking you to do.
Demonstrate baseline knowledge, accurate terminology, and core practical application.
Provide detailed analysis, structured explanations, and clear workplace reasoning.
Deliver thorough evaluation, original problem solving, and fully justified recommendations.
Before You Start
Prior knowledge that will help with this topic
- •Basic computer literacy: knowing how to use a mouse, keyboard, and navigate the operating system.
- •Understanding of file types and how to save/open files.
- •Some familiarity with common software like word processors or spreadsheets (though not essential).
Coursework AI Review
Paste your assignment brief and check your draft against its P/M/D criteria
Key Terminology
Essential terms to know
- Data Input and Editing
- Record Organisation and Sorting
- Information Retrieval and Queries
- Report Generation and Formatting
- Data Accuracy and Validation
- Enter, edit and organise structured information in a database, Use database software tools to extract information 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
- Non-relational table design
- Data entry and editing techniques
- Query construction and filtering
- Report generation and formatting
- Data organisation best practices
- 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
- Enter, edit and organise structured information in a database, Use database software tools to extract information and produce reports
- DBE:1 Enter, edit and organise structured information in a database, DBE:2 Use database software tools to 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
- Table creation and modification
- Data entry and editing
- Query design and execution
- Report generation
- Data organization and sorting
- Software navigation and tools
- 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
- Data entry accuracy
- Database structure and organisation
- Querying and filtering techniques
- Report production and formatting
- Data maintenance and editing
- Understanding of database terminology
Ready to learn?
AI-powered learning tailored to this unit