DSXchange

Hi,

I am using an sql server stage to run sql against a table.
To data both the code and the db have been on the same machine and so all i need to specify was the DB name, user name and password.

Unfortunately, i now need to move to an environment where the db and ds are no different servers.

can you tell me how to connect the sql stage to the new db on the new server please?

Thanks, as always

John Fitz

DS works thru database connectivities defined via setup activities. There's no requirement that DS reside on the same server as the database. SQL-Server on Windows is accessed via an ODBC connection defined on the DS Server. One of the fields in that setup is the server DSN/IP address. Just update that.

UNLESS...

the DataStage server resides on Unix, at which point you will not be able to use the SQL Server stage. I have this issue and find the best solution to be the Dynamic RDBMS stage.

Toodles,

One presumes both your database and you Datastage server are windows servers. On the datastage server go into Administrative tools as admin then Data Sources and point to the Database on the other server with "Add" a data source. Then you should be able to reference the remote database through odbc stage.

In the unlikely you are Unix for Datastage but if you are tell me and I'll show you some examples of how to point at an ms sql instance using odbc on Unix.

If Ray or Craig are looking at this, you can't use SQL Server stage on a Unix box, right?

... Flash Gordon

thanks to all

have that sorted now, as usual it's simple when you know how!

Regards
John Fitz

Correct, you cannot use the SQL Server stage on Unix. You can use the ODBC stages as you have pointed out. I have this setup right now and it works fine (though not with the faster speeds of native stages).

John,

I was looking at this today. On Unix you can use DRS stage and select MS SQL Server as the database. Probably just doing odbc anyway, right? I haven't used Datastage for windows for a long time so I was curious.

... Tom

Hi Flash!

That is correct. My understanding is that it is an optimized ODBC connector. If I remember correctly, using the Dynamic RDBMS allows better logging capabilities than the standard ODBC connector (don't quote that as gospel). I find it much easier to work with than the standard connector. It also allows me to change database engines very easily should I need to.

Toodles!