OPC with Microsoft SQL Server
It is a common requirement in automation to store or retrieve data to or from SQL databases. QuickOPC will make it easy for you to create OPC SQL solutions, i.e. integrate OPC client functionality into your database solution with Microsoft SQL Server. Reading a value from OPC Data Access server, or writing a data value can be achieved in just several lines of code. QuickOPC component interfaces hide the complexities of OPC and allow you to focus on your main task.
Dedicated solutions that integrate OPC and SQL databases exist from various vendors. For example, you can purchase packages that log the OPC data into the database, or packages that download recipes from the database to the technology. If you have more specialized needs, then a development work is needed to make the OPC SQL integration happen, and that's where QuickOPC components can help. Using programming language of your choice, you can express custom application logic that dedicated solutions cannot provide.
You are writing an application that connects to the SQL server using traditional means, such as ADO.NET, OLEDB, or ODBC. You have great flexibility in selecting technologies and application types - there are almost no limitations: Your code can be written C/C++, C#, VB6, VB.NET, or just about anything else.
You will use QuickOPC.NET components if the technology is based on Microsoft .NET, or you will use QuickOPC-COM if it is a language or tool that is capable of working with OLE automation objects. Either of these QuickOPC variations will give you client access to OPC servers located on your network.
How to log OPC Data Access item changes into an SQL database
How to log OPC Unified Architecture data changes into an SQL database
The SQL server can stay free of any custom, OPC-related code.