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

Join the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. 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
Anonymous
Not applicable

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
Anonymous
Not applicable

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
FabCon and SQLCon Highlights Carousel

FabCon &SQLCon Highlights

Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.

New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

March Fabric Update Carousel

Fabric Monthly Update - March 2026

Check out the March 2026 Fabric update to learn about new features.