OSI PI Data Historian vs SQL Server

Choosing the right database is a critical choice when building any software application. All databases have different strengths and weaknesses when it comes to performance, so deciding which database has the most benefits and the most minor downsides for your specific use case and data model is an important decision. Below you will find an overview of the key concepts, architecture, features, use cases, and pricing models of OSI PI Data Historian and SQL Server so you can quickly see how they compare against each other.

The primary purpose of this article is to compare how OSI PI Data Historian and SQL Server perform for workloads involving time series data, not for all possible use cases. Time series data typically presents a unique challenge in terms of database performance. This is due to the high volume of data being written and the query patterns to access that data. This article doesn’t intend to make the case for which database is better; it simply provides an overview of each database so you can make an informed decision.

OSI PI Data Historian Overview

OSI PI, also known as OSIsoft PI System, is an enterprise-level data management and analytics platform specifically designed for handling time series data from industrial processes, sensors, and other sources. Developed by OSIsoft (acquired by AVEVA in 2021), the PI System has been widely used in various industries such as energy, manufacturing, utilities, and pharmaceuticals since its introduction in the 1980s. It provides the ability to collect, store, analyze, and visualize large volumes of time series data in real-time, allowing organizations to gain insights, optimize processes, and improve decision-making.

SQL Server Overview

Microsoft SQL Server is a powerful and widely used relational database management system developed by Microsoft. Initially released in 1989, it has evolved over the years to become one of the most popular database systems for businesses of all sizes. SQL Server is known for its robust performance, security, and ease of use. It supports a variety of platforms, including Windows, Linux, and containers, providing flexibility for different deployment scenarios.

OSI PI Data Historian for Time Series Data

OSI PI was created for storing time series data, making it an ideal choice for organizations that need to manage large volumes of sensor and process data. Its architecture and components are optimized for collecting, storing, and analyzing time series data with high efficiency and minimal latency. The PI System’s scalability and performance make it a suitable solution for organizations dealing with vast amounts of data generated by industrial processes, IoT devices, or other sources.

SQL Server for Time Series Data

While Microsoft SQL Server is primarily a relational database, it does offer support for time series data through various features and optimizations. Temporal tables allow for tracking changes in data over time, providing an efficient way to store and query historical data. Indexing and partitioning can be leveraged to optimize time series data storage and retrieval. However, SQL Server may not be the best choice for applications requiring high write or query throughput specifically for time series data, as specialized time series databases offer more optimized solutions as well as a variety of developer productivity features that speed up development time for applications that heavily use time series data.

OSI PI Data Historian Key Concepts

• PI Server: The core component of the PI System, responsible for data collection, storage, and management.
• PI Interfaces and PI Connectors: Software components that collect data from various sources and send it to the PI Server.
• PI Asset Framework: A modeling framework that allows users to create a hierarchical structure of assets and their associated metadata, making it easier to understand and analyze data.
• PI DataLink: An add-in for Microsoft Excel that enables users to access and analyze PI System data directly from Excel.
• PI ProcessBook: A visualization tool for creating interactive, graphical displays of PI System data.

SQL Server Key Concepts

• T-SQL: Transact-SQL, an extension of SQL that adds procedural programming elements, such as loops, conditional statements, and error handling, to the standard SQL language.
• SSMS: SQL Server Management Studio, an integrated environment for managing SQL Server instances, databases, and objects.
• Always On: A suite of high availability and disaster recovery features in SQL Server, including Always On Availability Groups and Always On Failover Cluster Instances.

OSI PI Data Historian Architecture

OSI PI is a data management platform built around the PI Server, which is responsible for data collection, storage, and management. The PI System uses a highly efficient, proprietary time series database to store data. PI Interfaces and PI Connectors collect data from various sources and send it to the PI Server. The PI Asset Framework (AF) allows users to model their assets and their associated data in a hierarchical structure, making it easier to understand and analyze the data. Various client tools, such as PI DataLink and PI ProcessBook, enable users to access and visualize data stored in the PI System.

SQL Server Architecture

Microsoft SQL Server is a relational database that uses SQL for querying and manipulating data. It follows a client-server architecture, with the database server hosting the data and processing requests from clients. SQL Server supports both on-premises and cloud-based deployment through Azure SQL Database, a managed service offering in the Microsoft Azure cloud. SQL Server’s architecture includes components such as the Database Engine, which processes data storage and retrieval, and various services for reporting, integration, and analysis.