You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing docs@inductiveautomation.com.
LESSON LIST
-
8:15Event Streams
-
3:59Kafka - Source Example
-
3:46Kafka - Handler Example
-
7:58Form Component - Structure and Widgets
-
3:39Form Component - Contingent Actions
-
4:55Form Component - Submission Management
-
4:21Form Component - Submitting Form Data in Offline Mode
-
13:37Form Component - Basic Form
-
2:13Offline Submissions
-
4:19File Association and Deep Links
-
11:38Drawing Component - Overview
-
16:14Drawing Component - Elements
-
5:05Drawing Component - Modification Tools
-
10:43Drawing Component - Layering and Alignment
-
2:14SQL Historian
-
4:55Deployment Modes
-
5:29Siemens Symbolic Driver - Browsing
-
4:46Siemens Symbolic Driver - Migrating
-
4:18Internal Secret Providers - Referenced Secrets
-
1:35Internal Secret Providers - Embedded Secrets
-
7:05Alarm Metrics Filtering and Aggregation
LESSON
SQL Historian
Description
Learn how to utilizize existing database connections as historians by creating SQL Historians.
Video recorded using: Ignition 8.3
Transcript
(open in window)[00:00] In this lesson, we'll learn how to create an SQL historian. This type of historian leverages an SQL database for the storage and retrieval of historical data. This does mean that you need a valid database connection in order to create one. So if you're looking at the database connections page like you see on my screen, then there should be a row under the connection section with a status of valid. You can see I have two Maria database connections and they are both valid. Just having a valid connection, however, does not automatically set these databases as historians. We would still need to create those under the historians page. You can get there by drilling into services, and then historians. Once on the historians page, you would then click on the create historian button. We get this create historian menu, and we'll scroll down to SQL historian and select it and click on Next.
[01:02] The only fields that are required are the name and data source, so I'll just name this "Maria Historian". The data source is essentially which database you want to utilize, so I can select one from any of those valid connections that I had. I'll just choose DB one. There's some additional settings available for how you want to partition or prune data. These are nice to have as additional data management options. I'd recommend checking out the user manual link listed below this video to explore the different configuration options that are available to those sections. If we scroll all the way down, there is this button to show advance options. This reveals settings for stale data detection, which is a way to evaluate tag values that remain static for too long. I'm not going into detail on how this works, but just know this is where you can find these settings. And again, you can visit that user manual page for more information. As long as you have a name and a data source applied, then you have enough to create the historian, and you can do this by clicking on the create historian button.
[02:04] You can see I have a new row on this page for my maria historian, and it's in a running status.