|
In Control Panel, using ODBC Administrator, create a System Data Source selecting the iSeries Access driver and setting the name,system, library and other parameters as you wish.
Using MS SQL EM, Expand the Security branch and then right click on "Linked Servers" and select "New Linked Server". In the dialog box, give the Server any name you want and then select the "Microsoft OLE DB Provider for ODBC Drivers" from the drop down list of provider names. In the Data Source field, type the name of the data source you defined in the ODBC Administrator. That's all you need to do. You can also specify a library (collection/schema) in the Catalog field.
I also clicked on the Security tab and defined a permanent User ID and password for the context but I think the ODBC driver will prompt you.
That was all I needed to do and it connected just fine. Pete Helgren Pete Helgren wrote:
Jim, I had forgotten about the Linked Server option.... I'll give it a try and post what I come up with. Pete Pete Helgren wrote:The File/User/System DSN issue really only affects how the DSN is locally stored and how it is accessible. The actual implementation is the same in all cases.I have used ODBC quite a bit in SQL EM to import data using DTS. Beyond that particular application I am not sure how else SQL EM would use iSeries data (e.g. there is no "connector" and it can't, to my knowledge, manage iSeries tables).DTS works well though. A heckofalot better than the DB2 tools. Pete Helgren
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
