Using OPENQUERY() to execute query in linked server. The examples above make all data processing on SQL Server. It can be very unoptimal if there's a lot of data in linked server's tables. We may want - or usually want - to process some data in linked server before SQL Server starts local processing. For this we have OPENQUERY(). Here will be entered configuration to connect to MySQL server: In the Linked server text box of the General tab, enter the name of how the linked server will be called (e.g. MYSQL_SERVER). Choose the Other data source radio button and from the Provider list, choose the Microsoft OLE DB Provider for ODBC Drivers item: However, in practice, lack of understanding leads consumers to use a combination of keywords both corresponding to the generic OLE DB properties and to provider specific keywords making sense only in the context of the provider string. For example the site listing lots of examples of connection strings has the following for SQL Server Native In the Server Objects node, right-click Linked Servers and click New Linked Server. The New Linked Server dialog is displayed. In the General section, click the Other Data Source option and enter the following information after naming the linked server: Provider: Select the SQL Server Native Client Provider that corresponds to your version of Connect to specified DB Instance that you are going to use the Shared Server (Linked Server) in it. Go to [Server Objects] and on the [Linked Servers] perform a [Right-Click] and select [New Linked Server]. [ Linked server] : XXX.XXX.XXX.XXXDDSS (The NetworkName of Shared Server that will be used for addressing the Shared server). After installing the MSOLEDB x64 driver for 64-bit SQL Servers, you can use the Management Studio Interface or T-SQL to create a new linked server to another instance of SQL Server. Linked Server MSOLEDB Driver. Or using T-SQL: USE [master] GO. EXEC master.dbo.sp_addlinkedserver @server = N'', @srvproduct=N", @provider=N Linked Servers are a method by which a SQL Server can talk to another ODBC compliant database, such as another SQL Server instance or an Oracle database, with a direct T-SQL query. There are several important settings to know when setting up a Linked Server. This tip will cover creating a Linked Server to another SQL Server instance using the Once you created a linked server, you don't need a connection string. Just make a connection to your primary server and do some query, e,g.--List the tables in the linked server. EXEC sp_tables_ex txtsrv GO--Query one of the tables: file1#txt--using a four-part name. SELECT * FROM txtsrv[file1#txt] where txtsrv is a your linked server name. 'IBMDADB2.DB2COPY1' for @provider. Next, specify the DBALIAS of your cataloged database for @datasrc. In this example assume we have cataloged the Sample database with a DBALIAS of SAMPLE. Optionally you can specify a default schema or catalog with @provstr=N'Initial_Catalog=mySchema' For more information about sp_addlinkedserver view: This one is a bit tricky. First you need to set the connection object's Prompt property to adPromptAlways. Then use the connection string to connect to the database. oConn.Properties ("Prompt") = adPromptAlways. oConn.Open "Provider=SQLNCLI11;Server=myServerAddress;DataBase=myDataBase;" We can use these scripts to change the linked server alias, data source, and a wide range of other o