Errro message The operation could not be completed. The connectionString property has not been initialized (System.Data) ·

Question

Errro message The operation could not be completed. The connectionString property has not been initialized (System.Data) ·

Richard Argento 26

This question has been asked before by user member of this forum called cris123456 who also displays a large Nazi swastika as part of his profile logo,

Does that violate this forum's rules?

What he asked, and what I ask is this: I'm trying to upload data from .csv to a table by the SQL Server Import and Export Wizard However, I received this error: The operation could not be completed. The connectionString property has not been initialized (System.Data) ·

The answer he receive was Hi Cris,

If you’re using SQL Server Import and Export Wizard to load CSV file into database, you could choose “flat file source” in DataSource dropdown list and then refer to following link to set it., etc.

However, when I use the choose “flat file source” selection then I cannot format the resulting .dbo table's columns and the result is that column headings are not recognized and columns' data are formatted incorrectly.

To avoid that, I used the "Import Data" choice on the SQL Server Import and Export Wizard, which THEN allows me to select the type of file I am trying to import and I THEN specified "flat file" and the specific .csv file I wanted, and the Import and Export Wizard allowed me to check a box specifying the column headings for the table:

I did so, and I pressed the "Next" button and received the error message :

The operation could not be completed. The connectionString property has not been initialized (System.Data) ·

Howe do I get past this, given that the answer last time this question arose would not work for me, given my need to format the columns of the table, including column headings?

Accepted answer

3 additional answers

Your answer

Answer 1

Erland Sommarskog 121.9K MVP Volunteer Moderator

You have selected the .NET provider for ODBC. I don't think that is a good option to import flat files. And if you want to use it, you need to specify an ODBC driver on the second page.

Richard Argento 26 Reputation points

2021-10-10T19:13:23.587+00:00
Which provider, if not the .NET provider for ODBC, would be a good option to import flat files?

And, how do I specify an ODBC driver on the second page, if I do use the .NET provider for ODBC?
Erland Sommarskog 121.9K Reputation points MVP Volunteer Moderator

2021-10-10T21:26:34.43+00:00

As you quote in your original posting "Flat file source" like a possible bet. I don't really know for sure, as I would typically import a CSV file with BCP. I'm just pointing out the obvious error. You would use the ODBC provider if you were to import data from another relational data source, for instance Postgres.

It seems that you specify the driver on the first page. But that point is moot, because to my knowing ODBC is only for databases, not things like flat files.

Answer 2

Hi @Richard Argento ,

Sorry for reply late. I rested on weekend.

> I am using Microsoft SQL Server MS Version 18, maybe that is why your suggested solution does not work on my particular installaton:

My screenshot also from SSMS 18.x. I think that I should give you detail steps about this, it may make you better understood my suggestion.

You got the error message as the screenshot that you offered in previous post when you choose a destination source. This error means that you did not choose the correct provider for the destination source.

I assume you choose SQL Server database as the target data source, this means that you want to import data from CVS file to SQL server database. so I suggested you choose the correct the provider for SQL server as my first post mentioned. If I misunderstood your target data source, please let me know. You need to choose a correct provider for your target data source. If not you will got the error message that you got in the screenshot.

Please check the detail steps for my suggestion.

Choose CVS file location.
Choose the correct provider for destination source SQL server. Please scroll down the list of providers and then select SQL server Native client 11.0 for SQL server database source on Destination box.

3... Type the correct SQL server instance name, choose the correct authentication for SQL server, choose the correct database that you want to store the data from CVS file.

Then Next and Next.

If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar thread.

Richard Argento 26 Reputation points

2021-10-08T18:39:12.337+00:00

Hi Cathy,

Thanks for answering; I am using Microsoft SQL Server MS Version 18, maybe that is why your suggested solution does not work on my particular installaton:

I successfully get to this step:

I press the NEXT button on the Import and Export Wizard to indicate the Destination and I get the following result;

I AGAIN press the NEXT button on the Import and Export Wizard and I get the error message which I indicated at the beginning and in the title of my question.

How do I fix this?

Answer 3

CathyJi-MSFT 22,396 Microsoft External Staff

Hi @Richard Argento ,

Welcome to Q&A forum.

>I received this error: The operation could not be completed. The connectionString property has not been initialized (System.Data) ·

Please make sure that you have choose the correct provider for destination source SQL server as below screenshot.

Refer to this similar thread.

If your issue did not occur on this step, please share us a screenshot of your issue that you got the error message to make us better understand your issue. It will help us to give you a better help.

By the way, suggest you reading the blog Import csv into SQL server (with query OR without query using SSMS), it will show you the detailed steps about importing CVS to SQL table.

If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar thread.

Ajiboye, Remilekun Olamide 0 Reputation points

2023-05-06T13:27:41.31+00:00

I'm faced with a similar challenge, and my version of SQL did not come with the SQL Server Native Client 11.0 option. How do I get past this, please?
Erland Sommarskog 121.9K Reputation points MVP Volunteer Moderator

2023-05-06T13:50:01.83+00:00

House rules: don't piggyback on old threads, but ask a new question, describe your problem from start to end.

Answer 4

zaz 0

I solved it watching this video I found on YouTube

https://youtu.be/brGq2by7DvA?si=1Cf701DvRWdR6FXq

Share via

Errro message The operation could not be completed. The connectionString property has not been initialized (System.Data) ·

3 additional answers

Your answer