Create destination table automatically when using the SQL SERVER 2008 R2 Import and Export Data (64-bit) program

Hi all.

I want to be able to create destination table automatically when using the SQL SERVER 2008 R2 Import and Export Data (64-bit) program. When I go through the wizard and get to the "Select Source Tables and Views" window it I select the "Source" table and it automatically populates the "Destination" table with the same name. This is good, because I haven't created the destination table yet. But when I click the Next button it gives me an error:

"Column information for the source and the destination data could not be retrieved, or the data types of source columns were not mapped correctly to those available on the destination provider."

In SQL Server 2000 I used to be able to create the table in the same wizard when copying. How can I do this now?

Thank you in advance.
printmediaAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vitor MontalvãoMSSQL Senior EngineerCommented:
After choosing the source and destination table click on Edit Mappings... button an verify if all source columns has a correct destination column.
0
printmediaAuthor Commented:
Thank you for your reply.

When I click the "Edit Mappings..." button I get the error:

Column information for the source and destination data could not be retrieved.
"myTable" -> [dbo.].[myTable]:
- Index was outside the bounds of the array.

Additional Information: Index was outside the bounds of the array. (Microsoft.DataTransformationServices.Controls)

FYI: The source is a DSN "data source: .Net Framework Data Provider for Odbc." to our ERP software.
0
printmediaAuthor Commented:
I figured out the problem, it is with our ERP software ODBC driver. It does not return the fully qualified column name (i.e. [dbo].[TableName]). I have to write a SQL query to import the data instead.

Thank you anyways.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
printmediaAuthor Commented:
Figured it out on my own.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.