Wizard returns all rows during setup

  • Hi all,

    I have, once again, been sorely disappointed by MS's so-called Managed Newsgroups. This last marking the 30th consecutive post I have put up there that has gone completely unanswered.

    I am hoping that someone can shed some light on this issue for me.

    I am moving data from MySQL (v5.x) to SQL Server 2K5. This needs to run on a nightly basis, and I have several SSIS packages setup to do the work.

    The problem occurs when I am setting up the packages. I am using the Import/Export Wizard from within the Business Intelligence studio, using the MyODBC connector to attach to the MySQL databases, and providing a very simple query to pull the data (usually SELECT * FROM ). When I click next from the query, the wizard goes to the Select Source and Destination screen, at which time it executes the query, essentially pulling all rows across the wire, assumedly so you can click the Preview button to look at the data. This is not a big deal on small tables, but when you have a table with 35M rows in it, it takes almost an hour to execute. To make matters worse, after you wait, when you click the Edit Mappings... button the query is RE-EXECUTED, and I have to wait for another hour... Then I have to wait an hour yet again to actually execute the package!

    Is it just me or is there something not-so-good going on here?

    My questions are:

    #1 Why in the world do I need to pull all rows just to look at some sample data?

    #2 What if I don't even want to look at the sample data, why can't I just pull the table definition so I can do the column mapping on the next screen?

    #3 In all seriousness, is there any way to set a flag, or navigate around this behavior? Is there another approach I can use?

    Thanks for any info!

    Frustrated,

    Chris

  • Not to defend MS, but it could be an issue with the ODBC connector to MySQL. I have used the Import/Export wizard to pull data from other systems and have not seen this behavior. I'd be curious if anyone else is experiencing similiar problems as well.

    We do have a process that pulls data from a MySQL database, but it queries specific tables on a nightly basis for our HR system using a linked server.

    😎

  • Hi there,

    Thanks for the response. Someone else had mentioned linking the MySQL server and doing it that way... I think I will look into this more.

    Thanks!!!

    Chris

  • Hi Lynn,

    So I wound up linking the MySQL server, and am able to query the data and manipulate it, but it turns out to be noticeably slower than using SSIS.

    I still have the same problem, and even experience it when creating an SSIS package from within BI studio.

    Can anyone shed any light on this issue?

    Thanks!

    Chris

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

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