![]() ![]() ![]() You can check this in the SQL Server Configuration Manager tool (in the "Configuration Tools" folder in the start menu). O The SQL Server process is likely set to run under something other than the "Local System" account. Assistance with this should be directed to Microsoft service and support. Note that this is all Microsoft code-related and is as-is at best. There are two things that can affect this. If the user is getting "Msg 7399, Level 16, State 1, Line 1" type errors when attempting to run the sample select statement, this is a problem with the SQL Server service and the rights the user it is running under has. Note: Some additional configuration steps are often needed to get this working with SQL Server 2005, particularly if this is the first OLEDB provider the SQL Server user has ever tried configuring. In SQL Server 2005, you can test your linked server by running a simple query: 1. ![]() With Express versions but seems to work with Developer or Enterprise editions. This function seems dependent on what version of SQL Server 2005 is being used. Note: For SQL Server 2005, this test may not show a list of tables. You should see the list of tables in the right pane. In SQL Server 2000, test the connection by expanding the linked server and double-clicking on Tables. Under server Objects -> Linked Servers -> Providers right click on the provider being used (IBMDASQL, IBMDA400, or IBMDARLA) and select properties. The OLE DB provider must be configured to allow inprocess this only has to be done once per provider but if it is not done, you will get an error 7399 from SQL Server when you attempt to use the linked server. You should now see the linked server in the list. Select the Be made using this security context radio button.Ĭlick OK. In the above example, 'DB2 for i' is used. It seems that almost any value works, aside from special characters. Note: For SQL Server 2005, the Product Name must have a value. If you are accessing the libraries in an iASP you will need to insert the iASP RDB name in this field otherwise, the *SYSBASE database name will be retrieved. Typically you won't need to specify any value in this field. In Microsoft's terminology, Catalog is the relational database name. If you wanted to browse the objects in QIWS, MYLIB, and YOURLIB, you could set the provider string to:ĭefault Collection=QIWS Library List=MYLIB,YOURLIB Ĭatalog. If nothing is specified, the library of the user profile being used to connect will be used. This is the default library that you connect to. In the example below the 'Default Collection' property is used. Valid connection properties for the IBM i OLE DB provider can be found in the Programmer's Toolkit and in technote iSeries Access for Windows Custom Connection Properties for OLE DB. Connection properties are separated by a semi-colon. The Provider string can contain any valid connection properties the provider supports. This is the name of your IBM System i server. In the following example, I am using the IBMDASQL provider: The IBMDASQL OLE DB provider is the provider that should be used with Microsoft SQL Server linked servers. Microsoft's OLEDB-ODBC bridge, which uses our ODBC driver Offers the best performance when using the. Note: IBMDA400 does not support forward-only cursors or block fetches with RLA. RLA-only support, forward-only cursors and block fetches with RLA. SQL-only support, SQL commitment control, and MTS. Note: IBMDA400 does not support SQL commitment control or MTS it supports only SELECT statements. To decide which one of our providers would be best to use, you can refer to the following table from the IBM iSeries Access Programmer's Toolkit:Įxisting applications, applications that want the most flexible OLE DB support, including support for SQL, RLA, Data Queues, and Commands. Give your new Linked Server a title in the Linked server: text box.įor the Server type, select Other data source and select the desired IBM OLE DB data provider. Right-click on Linked Servers and select New Linked Server. Under the Console Root, expand Microsoft SQL Servers > SQL Server Group > Local > Security > Linked Servers for SQL Server 2000.įor SQL Server 2005 expand Server Objects > Linked Servers. Open the SQL Server Enterprise Manager(SQL Server 2000) or SQL Server Management Studio(SQL Server 2005). To configure a linked server using the IBM OLE DB data providers on an SQL server, you should do the following: 1, This document shows the basic steps to configure a linked server using the IBM OLE DB data providers on an SQL server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |