Accessing SQL Database in Rockwell Historian SE 4.00.01: Expert Insights on Table Structures and Relationships

Question:

Subject: Inquiry About SQL Database Access for Rockwell Historian SE 4.00.01 Hello, I have a quick question regarding Rockwell Historian SE 4.00.01, which utilizes MS SQL Server Express. In my previous experience with Wonderware InSQL Historian, I was able to directly access the underlying SQL database using various database management tools, such as Toad, to explore tables like AnalogHistory and DiscreteHistory. Is it possible to do the same with Rockwell's Historian? Additionally, can anyone provide details about the database structure, including the tables and their relationships? I want to gather some foundational information before Rockwell Historian arrives on-site in a couple of months. Thank you, Martin

Top Replies

The underlying data in FactoryTalk Historian is not stored in SQL; instead, it is maintained in flat files. If you’re looking to retrieve historical data using OLEDB or ODBC connectivity, it’s advisable to consider purchasing and implementing the Advanced Server option. While SQL holds the Asset Framework configuration and other related information, I can certainly provide a schema dump if you're interested in exploring it further.

Subject: Inquiry About Wonderware InSQL and Rockwell Historian Database Hi Dravik, Thank you for your prompt response! If I recall correctly, Wonderware InSQL utilized flat files; however, by employing a standard query tool like Toad for SQL Server, it was possible to access historical data, albeit not in real-time. It’s been over a decade since I last engaged with that technology, so I may be mistaken. I’m very interested in your offer regarding the database schema, as my curiosity about this topic is piqued. Additionally, I’d love to know what tables you can find when you log in to the SQL Server database associated with your Rockwell historian. Looking forward to your insights! Best, Martin

Databases associated with FactoryTalk products, including FTHSE, utilize MS SQL and are exclusively accessible through the related Rockwell application installation. These databases cannot be accessed externally since no SQL management tools are available for browsing SQL files. Additionally, it's important to note that the SQL framework installed by FTHSE does not store 'historical' data; instead, the FTHSE databases function as PI (Time-Series) containers, distinguishing them from traditional SQL relational databases. For database connectivity, both FTVantagePoint and FTView SE serve as the Historian front-end, leveraging the FTHSE SQL for efficient data retrieval in Historian SE.

I understand this discussion has been inactive for some time, but I have additional questions and observations to share. We installed FT Historian SE in August 2017, and it has been successfully collecting data from various PLCs and SCADA systems on our site since then. However, yesterday marked our first attempt to analyze the data, and I found the experience somewhat disappointing. I aimed to review historical data for ten specific items over a three-hour timeframe on a designated day, and create a graph from those results. I utilized the PI DataLink Excel add-in to query the historian data. Although the wizard appeared to support multiple item selection, it only allowed the selection of one item at a time, necessitating manual graph creation. Next, I experimented with the PI System Management tool to export the data to CSV format (which I then imported into Excel to create the graph manually). Unfortunately, despite the interface indicating that several items were selected, all data points were grouped together, making it impossible to isolate them. Is it true that, to effectively visualize the collected data, I must create a trend within a SCADA display using FTView or utilize FTVantage-Point? Perhaps I’m overlooking some functionality?

User dmargineau pointed out that the MS SQL databases associated with FactoryTalk products, including FactoryTalk Historian SE (FTHSE), are locked and accessible only through the specific Rockwell application they are linked to. Users cannot perform a 'lookup' of SQL files since there are no tools available resembling 'SQL Manager.' Moreover, the SQL databases installed by FTHSE do not store any historical data; the databases created with FTHSE function as PI (time-series) containers, rather than traditional SQL relational databases. The FTVantagePoint and FTView SE applications, which act as the front-end for the Historian, utilize the FTHSE SQL for connecting to the Historian SE database. However, I believe there’s some misunderstanding. I may not have grasped your point correctly, in which case I apologize. In my experience, I utilize the standard Datalog from FTView SE to log data into a Microsoft SQL Express database. I then employ DreamReport for extracting information from the SQL database for various applications, including generating reports and visualizing trends. For better clarity, here's a higher resolution screenshot: [link](https://ibb.co/er4qMH).

Hi Martin, great question! You can indeed access the Rockwell Historian SE database using tools like SQL Server Management Studio (SSMS), but keep in mind that direct modifications to the database tables aren't recommended, as it could affect the integrity of the data or the application itself. For the structure, Rockwell provides some documentation that outlines the key tables, including the AnalogHistory and DiscreteHistory tables, as well as their relationships, but it’s always a good idea to check their official resources or user community for the latest insights. It sounds like you're gearing up well for the installation—good luck!

Hi Martin, great question! Yes, you can access the underlying SQL database of Rockwell Historian SE 4.00.01 using tools like SQL Server Management Studio. However, keep in mind that the database schema is quite different from what you're used to with Wonderware. The structure can be a bit complex, but typically you'll find tables like Points, AnalogData, and DiscreteData. It's also essential to understand the relationships between them to make sense of the data, as they often link through keys. I recommend checking the documentation Rockwell provides; it usually includes helpful diagrams and explanations about how the data is organized. It’ll definitely help you hit the ground running when the system arrives!

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

✅   Work Order Management

✅   Asset Tracking

✅   Preventive Maintenance

✅   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

You must be a registered user to add a comment. If you've already registered,
sign in. Otherwise, register and sign in.

Frequently Asked Questions (FAQ)

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  â†’