Database Journal
MS SQL Oracle DB2 Access MySQL PostgreSQL Sybase PHP SQL Etc SQL Scripts & Samples Tips Database Forum Rss Feed

» Database Journal Home
» Database Articles
» Database Tutorials
MS Access
SQL Scripts & Samples
» Database Forum
» Slideshows
Free Newsletters:

News Via RSS Feed

Rss Feed

Database Journal |DBA Support |SQLCourse |SQLCourse2

Featured Database Articles


Posted May 8, 2001

Configuration of StarSQL 3.0

By Brian Knight

The first step that one must do to create a link to or export data from DB2 is to establish to proper connectivity. This supplimental artical will show you how to configure StarSQL 3.0 by StarQuest. It is a good idea if you are the DB2 admin when installing the product to run a custom installation and install StarAdmin also. StarAdmin will give you the access to easily bind the packages to DB2. If you are using StarSQL to connect to DB2 for the purposes of DTS or linked servers, make sure that you install it on the server and configure it exactly as you did on your workstation. StarSQL will not work with the Windows 95 or 98 operating system.

I choose StarSQL 3.0 for the following reasons:

  • Ease of configuration.
  • Supportibilty by Microsoft of DTS and Replication
  • Fits seamlessly into DTS and Linked Server.

Another consideration you must have is the datatypes. You will need to check the datatypes on DB2 and SQL Server to make sure that they will support each other. The chart below covers covers the supportibilty of the datatypes (see books online for more information).

Click here for comparison table.

  • Install StarSQL ver 3.x. Download at StarQuest.

  • Register the software with either a temporary evaluation code or a purchased one. If you do not register the software, you will receive an "INVALID NODE ID" error. This error will not occur until you try to see the actual data in SQL Server. You will be able to see the schemas however.

  • Go to the control panel, then ODBC Data Sources.

  • Select the system DSN tab. When prompted to select a type of ODBC, select StarSQL.

  • Give your data source a name and make a note of it. (see figure 1)

    Give your data source a name
    FIGURE 1 (click for full size)

  • Enter the server name of your DB2 server and leave the default package collection name as STARSQL (see figure 2).

    Enter the server name
    FIGURE 2 (click for full size)

  • Select the method of connection you wish to use to link the SQL Server to DB2 for the Network Option (see figure 3). If using TCP/IP, select the IP Address for the host name and port (see your DB2 Admin for port information).

    Select connection method
    FIGURE 3 (click for full size)

  • Enter your DB2 or RACF user id and password

    Enter User ID and password
    FIGURE 4 (click for full size)

  • Click on advanced (which replaced next). If you'd like to filter which DB2 database schemas will be visible to the user, check the databases you'd like to see in the Catalog Filters section. Hint : If you see schemas listed here, you know your conectivity is good to the DB2 server. Click summary after you've completed this option.

  • Verify the settings on the summary screen and click OK.

    Verify summary information
    FIGURE 5 (click for full size)

You are now ready to configure SQL Server 7.0 to link to DB2 and import data via DTS. If you need any help, I've found Starquest's technical support to always answer on the first ring and be very helpful. As always, feel free to contact me by email if any problems occur.

MS SQL Archives

Latest Forum Threads
MS SQL Forum
Topic By Replies Updated
SQL 2005: SSIS: Error using SQL Server credentials poverty 3 August 17th, 07:43 AM
Need help changing table contents nkawtg 1 August 17th, 03:02 AM
SQL Server Memory confifuration bhosalenarayan 2 August 14th, 05:33 AM
SQL Server Primary Key and a Unique Key katty.jonh 2 July 25th, 10:36 AM