How to Create WinCC Unified SQLite Reports in SSRS

In our previous article, we configured an IIS Reverse Proxy to embed SSRS in WinCC Unified without CORS policy conflicts. Now that the infrastructure is in place, the next step is to build custom reports that read directly from the Unified historical SQLite database.

WinCC Unified stores datalogs (historical tag values) and alarms in SQLite databases. SSRS Report Builder can connect to these sources through ODBC. In this guide, we follow the real workflow, from file discovery to the final validated report in the viewer.

• Configure an ODBC Data Source pointing to SQLite
• Explore database structure and available data
• Design a visual report in Report Builder
• Publish and view the report in SSRS

Start at the real data source. In Windows Explorer, identify the physical path used by WinCC Unified: C:\ProgramData\SCADAProjects\RT\TLGDB\. You will find .db3, .db3-shm, and .db3-wal files, confirming where historical data is stored.

Once the location is confirmed, install and open DB Browser for SQLite to inspect the database. Download it from sqlitebrowser.org/dl, install the appropriate version, and open the .db3 file to verify that data is accessible before moving to SSRS.

Before connecting SSRS, prepare the query logic based on the structure shown in SQL Browser. This step validates the tables and fields required in the report and helps reach a stable final query.

With the data model clear, download and install the SQLite ODBC Driver from ch-werner.de/sqliteodbc. Then validate in ODBC Data Source Administrator that the driver is available and the DSN is properly defined. This avoids connection errors later in SSRS.

Next, configure the DSN with database path and technical parameters. This defines the ODBC connection consumed by SSRS, including the connection test to confirm proper response.

Inside SSRS, verify that both report and data source exist in the portal. This server-side view confirms that objects are published and linked in the expected location.

Open Data Source properties and set the ODBC connection string and credentials. The connection test is the key verification that SSRS can read the SQLite database.

With the source operational, design the report in Report Builder: dataset, fields, Tablix layout, and visual formatting. This defines what the end user will see.

Run the report to validate real data loading, pagination behavior, and output quality. If this step works correctly, the report is ready for operational use.

On the Report Server home page, validate overall SSRS availability and access to published resources. This is the main entry point for daily administration and operation.

With the server running, review the report in Report Viewer to confirm data rendering, formatting, and navigation. This is the checkpoint before final acceptance.

Final result of the full workflow: operational report, visible historical data, page navigation, and output ready for export and production usage.

With these 12 steps, we covered the complete path from ODBC driver configuration at OS level to final report visualization in SSRS. The combination of:

• SQLite as WinCC Unified historical database
• ODBC as connectivity protocol
• SSRS and Report Builder for reporting
• IIS Reverse Proxy for Unified embedding (from the previous article)

...provides a complete and professional solution to build advanced reports from automation project historical data. End users can access these reports directly from WinCC Unified, filter by date ranges, export to multiple formats, and perform deep analysis on datalogs and alarms.