Select * from openquery ( PI, ‘select * from pipoint.pipoint where tag=”sinusoid”’ ) Next check that you can run queries against the pipoint table as follows: Select * from openquery ( PI, ‘select * from pisystem.piproductversion’ ) Now check that you can run queries against the linked server using something like the following in an SSMS query window (where “PI” is the name of the linked server just created): If it works, that’s great – you should also be able to open up a view on a number of Catalogs defined under the linked server, each of which contains a number of tables and associated views. You should be able to test the connection to the linked server. Enable Promotion of Distributed Transactions for RPC = True.Just select the option “Be made using the login’s current security context.”.In the linked server properties dialog set up as follows… After this it should be possible to set up the linked server definitions in SQL Server Management Studio. Make sure to install the PI System pre-requisites beforehand.
To set up linked servers on the PI OLEDB Provider, the PI SDK and OLEDB Provider packages from OSI must be installed on the database server. One route to query-based access is through OSI’s PI SQL Commander tool, which gives a front end to prepare queries on PI OLEDB Provider (for PI Servers) and also PI OLEDB Enterprise (for PI AF Servers).Īlternatively, linked servers can be defined on a SQL Server instance so that queries to the PI Server can be mixed with other databases (perhaps involving joins against other tables) in SQL Server Management Studio (SSMS), stored procedures based on SQL Server, used by applications, etc. It is possible to set up PI OLEDB Provider to get SQL access to the contents of your PI Server using the “PI OLEDB Provider” package from OSIsoft.
0 kommentar(er)
