Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us at the 2025 Microsoft Fabric Community Conference. March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for $400 discount. Register now

Reply
IntegrateGuru
Advocate I
Advocate I

Support for SQL Geography Type in CopyData Activity

I am just trying to understand why the copy data activity has such a hard time converting the SQL geography data type to a string to store into a Delta Table. 

It's capable of exporting the values as strings to csv files. 

But the sink mapping of geography -> string will cause your pipeline to fail every time, with this error:

he logical type is not supported in Delta format. Reason: Cannot find supported delta type for column name 'myGeographyColumn', logical type ,Source=Microsoft.DataTransfer.ClientLibrary,'

The only workaround, if you want to copy the data into your lakehouse without going first to csv file, is to manually write the SQL in the source like:

SELECT [myGeographyColumn].toString as myGeographyColumn FROM dbo.myTable

I have tried every source/sink data type, and have scoured the web for more info on the translator configurations that are stored in the pipeline JSON for copydata activites, but there is little to no information available.

Does anyone have any methods of ingesting the data from a pipeline with only the source/sink TabularTranslator configuration?

1 ACCEPTED SOLUTION
v-kongfanf-msft
Community Support
Community Support

Hi @IntegrateGuru ,

 

As you say, the best option at the moment is to use below code to make sure that the data is already in string format before it reaches the Delta table, thus avoiding the type mismatch issue.

SELECT [myGeographyColumn].toString as myGeographyColumn FROM dbo.myTable

 

Best Regards,
Adamk Kong

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

1 REPLY 1
v-kongfanf-msft
Community Support
Community Support

Hi @IntegrateGuru ,

 

As you say, the best option at the moment is to use below code to make sure that the data is already in string format before it reaches the Delta table, thus avoiding the type mismatch issue.

SELECT [myGeographyColumn].toString as myGeographyColumn FROM dbo.myTable

 

Best Regards,
Adamk Kong

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

FebFBC_Carousel

Fabric Monthly Update - February 2025

Check out the February 2025 Fabric update to learn about new features.

Feb2025 NL Carousel

Fabric Community Update - February 2025

Find out what's new and trending in the Fabric community.