In a vehicle service management system, the service history of a vehicle refers to the complete record of all maintenance and repair activities performed on that vehicle. Displaying this history in chronological order is an important database operation because it enables the owner, service centre, or administrator to understand how the vehicle has been maintained over time. In a DBMS and C++ Lab context, this task can be implemented by storing vehicle and service details in database tables and retrieving the records of a specified vehicle using an SQL query with an `ORDER BY` clause. A suitable database design may contain a `Vehicle` table and a `ServiceHistory` table. The `Vehicle` table can store information such as vehicle registration number, vehicle model, owner name, vehicle type, and purchase date. The `ServiceHistory` table can contain fields such as service ID, vehicle registration number, service date, service type, description of work performed, service cost, and service centre. The registration number can be used as a common field between the two tables. The service history table should have a primary key such as `service_id`, while `vehicle_no` can act as a foreign key referring to the vehicle table. For example, the structure of the service history table may be represented as: ```sql CREATE TABLE ServiceHistory ( service_id INT PRIMARY KEY, vehicle_no VARCHAR(20), service_date DATE, service_type VARCHAR(50), description VARCHAR(200), cost DECIMAL(10,2) ); ``` Some sample records may be inserted into the table as follows: ```sql INSERT INTO ServiceHistory VALUES (101, 'DL01AB1234', '2022-04-15', 'General Service', 'Engine oil and filter changed', 2500); INSERT INTO ServiceHistory VALUES (102, 'DL01AB1234', '2022-10-20', 'Repair', 'Brake pad replaced', 3500); INSERT INTO ServiceHistory VALUES (103, 'DL01AB1234', '2023-06-12', 'General Service', 'Engine inspection and oil change', 2800); INSERT INTO ServiceHistory VALUES (104, 'DL01AB1234', '2024-01-18',