Post reply

Mapping Sybase tables for use in lookup function and end table

  • March 23, 2010 at 8:32 am

    #138891

    We are int he process of implementing a new procedure whereby we take client flat files, perform transformations on the data using both derived functions as well as reference tables. The reference tables and end table are all Sybase tables. When we attempt to map the reference tables or the end table to the process it gives us an error which out IT team has said occurs because SSIS is adding an additional "dbo." to the front of the table4 names.

    Has anyone had any success linking Sybase tables as reference tables in lookups and also as the repository for the end data? If so, please help!!!!!

  • March 23, 2010 at 9:36 am

    #1138326

    mikelordi2 (3/23/2010)

    We are int he process of implementing a new procedure whereby we take client flat files, perform transformations on the data using both derived functions as well as reference tables. The reference tables and end table are all Sybase tables. When we attempt to map the reference tables or the end table to the process it gives us an error which out IT team has said occurs because SSIS is adding an additional "dbo." to the front of the table4 names.

    Has anyone had any success linking Sybase tables as reference tables in lookups and also as the repository for the end data? If so, please help!!!!!

    the issue's unclear; first you said you are taking flat files and transforming them, which i would infer that you are putting the tables into SQL Server because you specifically said you are using SSIS ; then you said "The reference tables and end table are all Sybase tables. When we attempt to map the reference tables or the end table "

    if the tables are in Sybase, are you using a linked server? a linked server would have to have the full 4 part naming convention, ie select * from mySybaseServer...SomeTableName

    show us the exact query that fails, we can help you better.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • March 23, 2010 at 9:47 am

    #1138342

    Thanks Lowell....let me try to be more clear.

    Our project consists of using SSIS as an ETL tool (yes I know it's not really, but our company has a license for this and is forcing us to use this). We have numerous flat files which we setup as the "Flat File Source". I then setup Dervied column functions and lookup tables, with the end result being the OLEDB destination being a Sybase table.

    The lookup tables and the destination all use tables in the Sybase environment, but when I attempt to connect to them, I receive a failure. From what I can tell, SSIS is adding an additional "dbo." to the view or table name, so in the query it attempts to reference "dbo.dbo.PlanCode" as opposed to "dbo.plancode". There is supposedly a way to correct this, but being new to SSIS and Sybase we are a little behind and would like some guidance.

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

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