Creating a linked server in SQL Server 2008 is a great way to execute SQL queries against a completely different remote Historian server.

Transcription

1 Tech Note 874 Accessing Remote Historian Data Using Linked Server Functionality All Tech Notes, Tech Alerts and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information. Topic#: Created: September 2012 Introduction Creating a linked server in SQL Server 2008 is a great way to execute SQL queries against a completely different remote Historian server. You can configure a linked server to enable the SQL Server Database Engine to execute commands against OLE DB data sources outside of the instance of SQL Server. Therefore, linked servers can be configured to enable the Database Engine to execute a Transact-SQL statement that includes Historian Runtime database s tables in another instance of SQL Server. This Tech Note provides step-by-step procedure showing you how to use the Microsoft SQL Server Management Studio 2008 to create a linked server relationship with your Historian node. Note: Linked Server functionality is not supported by Wonderware Tech Support. For Linked Server issues, contact Microsoft Support. Application Versions Wonderware Historian v10.0 SP1 SQL Server 2008 Setting Up the Linked Server 1. Open the MS SQL Server Management Studio. 2. Go to Server Objects of the database server where the linked server will be added and right-click Linked Servers. 3. Click Add New Linked Server. 4. In the General tab, type a name for the new linked server in the Linked Server field. MY_LINKED_SERVER is used for this example (Figure 1 below). 5. Select Other data source. 6. For Provider select Microsoft OLE DB for SQL Server. 7. For Product Name type SQLOLEDB.

2 8. In the Data Source field, type the IP address or the network name of the target server. In this example, we use briann5. It is running the Historian from which we'll get the data. 9. Catalog is the name of the target database on the linked server. Runtime is the Historian database on that server. Figure 1: Linked Server Setup 10. Click the Security page item and select Be made using this security context (Figure 2 below). When connecting from a different domain, type in the remote login and credentials. In this example, we are connecting as the same domain user with local administrative privileges on the Historian Server.

3 Figure 2: Security Options: Log In Using the Same Security ConteXt 11. Click the Server Options page to view the options.

4 Figure 3: Server Options Running Queries Here is the syntax to query against this server. The following example was run against the SysTimeSec tag: SELECT * FROM [MY_LINKED_SERVER].[database_name].[dbo].[table_name] And here is the query against the Historian Server's History table: SELECT DateTime, TagName, Value, QualityDetail FROM [my_linked_server].runtime.dbo.history WHERE tagname = 'SysTimeSec' AND DateTime >= DATEADD(second, -10, GetDate())

5

6 Figure 4: Query Return from Linked Server B. Nguyen Tech Notes are published occasionally by Wonderware Technical Support. Publisher: Invensys Systems, Inc., Rancho Parkway South, Lake Forest, CA There is also technical information on our software products at Wonderware Technical Support. Back to top 2012 Invensys Systems, Inc. All rights reserved. No part of the material protected by this copyright may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording, broadcasting, or by anyinformation storage and retrieval system, without permission in writing from Invensys Systems, Inc. Terms of Use.