Understanding PI Vision Patch Upgrades: Why Your SQL Database dbo.Version Remains Unchanged

Upgrading critical infrastructure like PI Vision is a careful process, and it’s common for engineers and administrators to double-check that all components are updated as expected. A recent community discussion highlighted a frequent point of confusion: upgrading from PI Vision 2020 to 2020 Patch 1 and noticing that the SQL database, specifically the dbo.Version table, does not reflect any change.

Let’s look at why this is not cause for concern, and how you can verify your PI Vision system is up-to-date.

The Scenario: Patch Installation Without Schema Changes

One user, Ashwin, shared a typical case: after performing the PI Vision 2020 Patch 1 upgrade, he saw no errors in the PI Vision administration configuration page, but observed that the dbo.Version table in the PI Vision SQL database did not reflect an upgrade. This prompted worries that the upgrade hadn’t been fully applied, especially since SQL database upgrades and schema changes often accompany new software releases or patches in enterprise systems.

Community Insights: Schema Changes vs. Code Changes

Community responses and product documentation clarified a crucial point: not every patch or minor upgrade requires a database schema update. In the specific case of the upgrade from PI Vision 2020 to 2020 Patch 1, the product team confirmed that there were no SQL schema changes implemented. This means:

• No database migrations are triggered during the upgrade process.
• The dbo.Version table remains unchanged, as there’s no new database version to record.
• The upgrade consists primarily of application code changes, like bug fixes or minor feature improvements, that do not alter the underlying SQL structure.

Best Practices: How to Confirm Your Patch is Applied

1. Review Release Notes: Always consult the patch or release notes to check for database changes, migration steps, or special instructions. For PI Vision 2020 Patch 1, the release notes do not list any schema or database updates.
2. Monitor the Installer Output: The PI Vision installer will typically note whether any database upgrades are being applied. Absence of such messages during a patch aligns with no schema changes.
3. Check In-App Diagnostics: If the PI Vision Admin page shows no errors and your application is functioning as expected, it’s a good indicator that the patch has been successfully installed.
4. dB Version Table Clarification: Only major upgrades or patches that actually perform schema changes will update the dbo.Version table. If you don’t see a new version, it means the schema is unchanged – not that the patch failed.

Key Takeaway

It’s perfectly normal for the dbo.Version table to remain unchanged when upgrading from PI Vision 2020 to 2020 Patch 1. The official documentation and community feedback confirm that this patch did not require a SQL schema change.

When in doubt, consult the release notes and refer to OSIsoft’s official resources. If errors aren’t reported in the administration interface and functionality is as expected, your upgrade is complete—even if the dbo.Version table looks unchanged.

Further Reading

• Upgrading your PI Vision Database
• PI Vision Documentation - OSIsoft Live Library

Have you encountered similar upgrade questions or have insights to share? Let us know in the comments below!