Strange connecting behaviour, why?

  • I have this DTSpackage, several Data Transformation tasks from a SybaseDB to a SQL2K. On the one site a have an OLE DB connection for Sybase from Sybase ASE OLE DB provider, on the other site our trusted Microsoft OLE DB Provider for SQL Server, pointing to DB1. Now I have changed something in my Data Transformationtasks, created a duplicate targetDB, DB2, and run the package. Succesfully ended, it says. I look in DB2 and see no records... I try again, and again: no records appear in DB2. I check connection parameters: yes, the targetdatabase is definitely DB2. I run it again, succesfully, and no records in DB2...

    I wake up and check DB1. A lot of records... Suspicious now I run the package again, no records in DB2, and lo! New records added in DB1!

    I check again: yes, the target IS DB2!

    I detach DB2 and run the package again, message: Error in Ole DB for SQL Server, unspecified error...

    What is going on here? I point to DB2, but DB1 is still the target, although the properties of the Connectionsource tells me otherwise.

    I am running SQL2K sp3 on W2003 server.

    Greetz,
    Hans Brouwer

  • This was removed by the editor as SPAM

  • Hi Hans

    Do you completely remove the Connection for DB1 - and then add a brandy new connection for DB2?  Are you using the vanilla SQL Server Connection in the DTS Designer - or are you using a Data Link File?  I've many times gotten confused by using the  Data Link file - either the wrong file name or the wrong path being used.  Are you executing the package within the DTS designer (then it looks for files/paths on your client)?  Or are you running the package as job (then it looks on the server).  Those are my thoughts.

     


    Mike at the Mill

  • Hi Mike,

    Yes, I have created a new connection for DB2 and used the old 1 with a new targetserver. I do use the SQLServerConnection in DTS. I run the package on the server, so I execute it directly, no job involved, I have not tried it with a job.

    I have meanwhile created a brand new package with a connection to DB2, no DB1 is mentioned anywhere. It works fine and do not wish to spend time hunting ghosts...;-)

    Tnx for your response.

    Greetz,
    Hans Brouwer

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply