SQL Server Practical Manual Industrial SQL Database Practical Manual
Official Philosophy: Open the software, open the Softwell Notebook, and perform the practical.
20 Matching Lab Practicals
Action Flow Manual
No Theory / Only Practical
Softwell Training Template
Softwell Digital Practical Notebook
[check] Open -> Click -> Select -> Download -> Test -> Complete
NO THEORY * ONLY PRACTICAL
P01
Softwell Digital Practical Manual
Practical 01 - Install SQL Server and SSMS
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Install SQL Server and SSMS.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Install SQL Server and SSMS as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Install SQL Server and SSMS.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Install SQL Server and SSMS
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Install SQL Server and SSMS is completed, verified and documented inside the SQL Server Practical Manual workflow.
Talk to Automation Advisor
Get expert guidance for course selection, corporate training, project support and practical learning path.
Course GuidanceSelect the correct PLC SCADA, corporate, online or Industry 4.0 path.
Batch SupportGet schedule, duration, mode and prerequisite guidance.
Project AdviceDiscuss plant, automation, reporting or training requirement.
P02
Softwell Digital Practical Manual
Practical 02 - Create Training Database
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Create Training Database.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Create Training Database as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Create Training Database.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Create Training Database
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Create Training Database is completed, verified and documented inside the SQL Server Practical Manual workflow.
Skills & Tools You Will Learn
Important automation skills are arranged for job-level, project-level and Industry 4.0 learning.
PLC ProgrammingLadder, SCL/ST, hardware, I/O mapping and troubleshooting.
SCADA / HMITags, screens, alarms, trends, scripts and reporting.
Industry 4.0 ToolsOPC UA, SQL Server, Python, dashboards and Excel/PDF reports.
P03
Softwell Digital Practical Manual
Practical 03 - Create Production Table
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Create Production Table.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Create Production Table as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Create Production Table.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Create Production Table
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Create Production Table is completed, verified and documented inside the SQL Server Practical Manual workflow.
P04
Softwell Digital Practical Manual
Practical 04 - Create Alarm History Table
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Create Alarm History Table.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Create Alarm History Table as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Create Alarm History Table.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Create Alarm History Table
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Create Alarm History Table is completed, verified and documented inside the SQL Server Practical Manual workflow.
Why Choose Softwell Automation
Learn automation with practical examples, industrial troubleshooting approach and complete IT/OT learning path.
Industry Experienced TrainerReal plant examples and project based training.
Hands-on LearningPLC logic, SCADA, VFD, communication and reporting practice.
Flexible ModesOnline, classroom, corporate and in-plant options.
P05
Softwell Digital Practical Manual
Practical 05 - Insert Manual Test Records
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Insert Manual Test Records.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Insert Manual Test Records as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Insert Manual Test Records.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Insert Manual Test Records
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Insert Manual Test Records is completed, verified and documented inside the SQL Server Practical Manual workflow.
Course Contents / Curriculum
The curriculum follows a practical sequence from fundamentals to project integration.
Level 01Basic PLC, wiring, addressing and ladder logic.
Level 02Advanced PLC, networking, SCADA and diagnostics.
Level 03OPC UA, SQL, Python, reports and IT/OT integration.
P06
Softwell Digital Practical Manual
Practical 06 - Import CSV Data
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Import CSV Data.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Import CSV Data as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Import CSV Data.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Import CSV Data
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Import CSV Data is completed, verified and documented inside the SQL Server Practical Manual workflow.
Frequently Asked Questions About SQL Server Practical Manual Industrial SQL Database Practical Manual
Who can join this training?
Students, freshers, working engineers, maintenance teams and corporate plant engineers can join based on their requirement.
Is practical training included?
Yes. The training is focused on PLC, SCADA, HMI, VFD, communication, troubleshooting and project based practice.
Can I request online or corporate training?
Yes. Softwell Automation provides classroom, online, corporate and in-plant training options.
P07
Softwell Digital Practical Manual
Practical 07 - Create Shift Report View
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Create Shift Report View.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Create Shift Report View as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Create Shift Report View.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Create Shift Report View
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Create Shift Report View is completed, verified and documented inside the SQL Server Practical Manual workflow.
P08
Softwell Digital Practical Manual
Practical 08 - Daily Summary Query
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Daily Summary Query.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Daily Summary Query as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Daily Summary Query.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Daily Summary Query
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Daily Summary Query is completed, verified and documented inside the SQL Server Practical Manual workflow.
P09
Softwell Digital Practical Manual
Practical 09 - Alarm History Query
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Alarm History Query.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Alarm History Query as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Alarm History Query.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Alarm History Query
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Alarm History Query is completed, verified and documented inside the SQL Server Practical Manual workflow.
P10
Softwell Digital Practical Manual
Practical 10 - Energy Report Table
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Energy Report Table.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Energy Report Table as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Energy Report Table.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Energy Report Table
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Energy Report Table is completed, verified and documented inside the SQL Server Practical Manual workflow.
P11
Softwell Digital Practical Manual
Practical 11 - Stored Procedure Report
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Stored Procedure Report.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Stored Procedure Report as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Stored Procedure Report.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Stored Procedure Report
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Stored Procedure Report is completed, verified and documented inside the SQL Server Practical Manual workflow.
P12
Softwell Digital Practical Manual
Practical 12 - Batch Report Query
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Batch Report Query.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Batch Report Query as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Batch Report Query.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Batch Report Query
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Batch Report Query is completed, verified and documented inside the SQL Server Practical Manual workflow.
P13
Softwell Digital Practical Manual
Practical 13 - Export Report to CSV
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Export Report to CSV.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Export Report to CSV as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Export Report to CSV.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Export Report to CSV
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Export Report to CSV is completed, verified and documented inside the SQL Server Practical Manual workflow.
P14
Softwell Digital Practical Manual
Practical 14 - Excel SQL Connection
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Excel SQL Connection.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Excel SQL Connection as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Excel SQL Connection.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Excel SQL Connection
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Excel SQL Connection is completed, verified and documented inside the SQL Server Practical Manual workflow.
P15
Softwell Digital Practical Manual
Practical 15 - PDF Report Preparation
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for PDF Report Preparation.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical PDF Report Preparation as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for PDF Report Preparation.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
PDF Report Preparation
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
PDF Report Preparation is completed, verified and documented inside the SQL Server Practical Manual workflow.
P16
Softwell Digital Practical Manual
Practical 16 - Schedule Auto Report
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Schedule Auto Report.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Schedule Auto Report as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Schedule Auto Report.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Schedule Auto Report
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Schedule Auto Report is completed, verified and documented inside the SQL Server Practical Manual workflow.
P17
Softwell Digital Practical Manual
Practical 17 - Database Backup
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Database Backup.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Database Backup as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Database Backup.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Database Backup
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Database Backup is completed, verified and documented inside the SQL Server Practical Manual workflow.
P18
Softwell Digital Practical Manual
Practical 18 - Database Restore Test
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Database Restore Test.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Database Restore Test as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Database Restore Test.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Database Restore Test
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Database Restore Test is completed, verified and documented inside the SQL Server Practical Manual workflow.
P19
Softwell Digital Practical Manual
Practical 19 - Read Only User Permission
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Read Only User Permission.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Read Only User Permission as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Read Only User Permission.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Read Only User Permission
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Read Only User Permission is completed, verified and documented inside the SQL Server Practical Manual workflow.
P20
Softwell Digital Practical Manual
Practical 20 - Final SQL Server Project
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SQL ServerDatabaseReportsHistorian
Software: SQL Server Express / Standard and SQL Server Management Studio Setup: Engineering laptop, local SQL instance, sample production and alarm dataset
A. Step-by-Step Procedure
01
STEP 01
Open SQL Server Express / Standard and SQL Server Management Studio and load the training project for SQL Server Practical Manual.
v
02
STEP 02
Create or open the practical object for Final SQL Server Project.
v
03
STEP 03
Configure the required tags, parameters, blocks or screen objects for this SQL Server reporting workflow.
v
04
STEP 04
Run compile, simulation, runtime or online monitoring as applicable and verify the practical behavior.
v
05
STEP 05
Save the work, record the result and tick Practical Final SQL Server Project as complete.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Final SQL Server Project.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Final SQL Server Project
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Final SQL Server Project is completed, verified and documented inside the SQL Server Practical Manual workflow.
Authentic Training Evidence
Watch Related SQL Server Industrial Reporting Videos
See Softwell Automation's practical teaching style directly on this page. The selected lesson and complete series help learners and companies verify the technology coverage before making an enquiry.
Featured practical: Introduction to PLC and SCADA SQL Reporting
Use a dedicated lab database and least-privilege login. Never test retention, backup or schema changes first on a production historian.
Create a typed tag-history table
Use appropriate data types and a deterministic primary key.
CREATE SCHEMA automation;
GO
CREATE TABLE automation.TagHistory (
TagHistoryId bigint IDENTITY PRIMARY KEY,
TagName nvarchar(128) NOT NULL,
TagValue float NOT NULL,
QualityCode smallint NOT NULL,
SampleTimeUtc datetime2(3) NOT NULL
);
Verify: Insert a lab row and confirm UTC precision and constraints.
Parameterized insert procedure
Keep values as parameters instead of building SQL text in SCADA scripts.
CREATE OR ALTER PROCEDURE automation.InsertTagSample
@TagName nvarchar(128), @TagValue float, @QualityCode smallint, @SampleTimeUtc datetime2(3)
AS
BEGIN
SET NOCOUNT ON;
INSERT automation.TagHistory(TagName,TagValue,QualityCode,SampleTimeUtc)
VALUES(@TagName,@TagValue,@QualityCode,@SampleTimeUtc);
END;
Verify: Execute with a test tag and confirm one row is added.
Historian query index
Index the common tag-and-time access path.
CREATE INDEX IX_TagHistory_Tag_Time
ON automation.TagHistory(TagName, SampleTimeUtc DESC)
INCLUDE(TagValue, QualityCode);
Verify: Compare the lab query execution plan before and after the index.
Transaction-safe batch insert
Rollback the complete batch if one validation step fails.
BEGIN TRY
BEGIN TRAN;
EXEC automation.InsertTagSample N'Tank.Level', 64.2, 192, SYSUTCDATETIME();
EXEC automation.InsertTagSample N'Tank.Temp', 41.8, 192, SYSUTCDATETIME();
COMMIT;
END TRY
BEGIN CATCH
IF @@TRANCOUNT > 0 ROLLBACK;
THROW;
END CATCH;
Verify: Force a lab error and verify that no partial batch remains.
Controlled retention deletion
Delete in batches during a planned maintenance window.
WHILE 1 = 1
BEGIN
DELETE TOP (5000) FROM automation.TagHistory
WHERE SampleTimeUtc < DATEADD(day,-90,SYSUTCDATETIME());
IF @@ROWCOUNT = 0 BREAK;
END;
Verify: Run only in the lab database and record rows before/after.
Least-privilege writer role
Grant only the procedure needed by the logging account.
CREATE ROLE automation_writer;
GRANT EXECUTE ON automation.InsertTagSample TO automation_writer;
-- Add the dedicated lab login/user to this role after review.
Verify: Confirm the test user can execute the procedure but cannot alter tables.
Practice, Viva and Mini-Project
Practice: Modify one input, predict the result, execute the code and compare the output.
Viva: Explain the data flow, failure behavior, safe-use boundary and recovery method.
Mini-project: Combine at least three examples into one reviewed, versioned solution with an evidence pack.
Acceptance: A second learner can run the saved solution and reproduce the documented result.
Before You Start: Prerequisites, Tested Version, Safety and Evidence
This manual is a practical training workbook, not a substitute for the installed product manual or the site's approved engineering procedure. Record the exact software, firmware, license and hardware before following a step because menus and supported functions can vary by release.
Tested-version planning scope: Confirm SQL Server Version 2019 or later, Management Studio, database compatibility level and service account permissions. Enter the exact lab-tested software, firmware and hardware in the record below before course delivery; never assume cross-version compatibility.
Environment record
Software build, firmware, device catalog, driver, communication interface and license status.
Safe lab boundary
Use an isolated training system. Follow electrical, mechanical, process and cybersecurity controls before energizing or downloading.
Evidence pack
Keep the source project, parameter/code export, screenshot/trend, fault test, correction and final pass result.
Technical review
Last reviewed by Softwell Automation Technical Training Team on 17 July 2026.
Field
Learner record
Verification
Software / firmware
________________
Matches the training device and official compatibility information
Project / backup
________________
Saved before and after the practical
Pass evidence
________________
Runtime value, trend, alarm, diagnostic or report attached
Fault tested
________________
Symptom, cause, check and corrective action documented
Practice, Viva and Extension Challenge
Practice
Change one approved input or parameter, predict the result, execute the test and explain any difference.
Viva
Explain the data flow, safety boundary, first diagnostic check and recovery method without opening the answer.
Extension challenge
Add one useful function while preserving the original pass criteria, alarm behavior and rollback path.
Graded mini-project
Combine at least three practicals, submit a versioned project and evidence pack, and demonstrate repeatable recovery.
Instructional workflow diagram: complete configuration, measurable verification, controlled diagnosis and recovery evidence in sequence.Microsoft SQL — official documentation
Content status: Substantively reviewed and expanded 17 July 2026. Verify release-specific details against the linked official documentation.
Verified learning pathway
Practise This Manual with Guidance
Use the manual with trainer-led practicals, software exercises and troubleshooting support.