DSXchange

It's not about the links, it's about the stages. Two links into two stages = possible locks. Two links into one stage = no locks. With SQL Server 2000 you will have the same issue going into one stage since SQL Server does not support multiple open statements against a single session. The OLEDB API...

Check whether some other person / application is modifying the table. Actually it is most likely his own job that is causing the problem. When you have the stage in the job twice it is opening 2 separate sessions to SQL Server. If this is the case you can usually fix the issue by setting the commit...

naveendronavalli wrote:Thanks a lot!
Ray, ds_user78, ArndW, chulett and Sainath.

Naveen.

I am not to sure if you found the actual command that you want. The correct syntax is:

Rod, With much work we finally convinced the modeler to allow us to add it to the data warehouse model as a column in the destination table. To keep the users from getting confused filter the columns out via the reporting tools metadata. This worked well for us since the relational database persists...

That is what I wanted to do but we have some free time and management has asked us to look at it now.

We are starting to look into using MetaStage again and was wondering if anyone is using it? If so what benefit are you seeing?

This product seriously needs a bcp stage for MSSQL server especially before Microsoft bring out their ETL tool with Yukon !!. There is a BCP stage that is supposed to work with SQL Server, it is just hidden under the Sybase stage collection. I have never used this stage since Microsoft states that ...

I guess I read too much into it. I was never that good with story problems.

Craig,

Works as expected? It seems that it is not working as Amos had expected therefore the question. :D

Amos,

When you set the commit size to zero you are setting the transaction so that all rows must insert without error or all rows are rolled back. If you set the commit size to 1 then each row will be committed individually and only the errored rows will be missing.

I would just load them up into temporary tables on the DBMS and do the cartesian using the database.

Dont forget the command line compiler (dscc.exe) that has been shipping for a couple versions.

Personally I think the counting of 1 dual core cpu as 2 single core cpus by DataStage is kind of a rip off. If you look at optimal performance (read benchmarks) you will see that 1 dual-core (for Sun e.g.) has the performance of about 1.5 single core cpu's. Ogmios Are you talking Dual core or Hyper...

We have seen the same issue here. I reported it to Ascential but I was never able to get a resolution from them. I even had them as Power user and it would not work. I finally gave up on working it out since we did not have the time. Good luck and let me know if you resolve this one since I would li...

I am getting an un specified error when I use the bulk load soure. How can I determine what the actual error is. The best way to track it down is to run the Microsoft SQL Profiler and filter it to trap the actual error. I have put a ticket into Ascential on this and the OLEDB stage not returning th...