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

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
cduden
Regular Visitor

Problem with Data Pipeline, Mysql column type of decimal

Attempting to set up a simple Copy data activity from our MySQL db.   I'm trying to copy one table but when I get to the mapping step it says the column "krivalue" has an unsupported type.   The type is decimal(50,2) in MySQL.  I've looked around on the interwebs but no joy.

cduden_0-1715805209738.png

The schema in MySql:

cduden_1-1715805233538.png

Any ideas re. what is wrong here?

 

Thanks.

1 ACCEPTED SOLUTION

Hi @cduden 

 

Yes, In Microsoft Fabric Pipelines, the behavior is slightly different. While it leverages underlying data storage solutions like Azure Synapse or SQL Server, there isn't a direct equivalent for setting the maximum precision for decimals within the pipeline itself.

These underlying data platforms support a maximum precision of 38 for the decimal data type. This means Fabric Pipelines will work with decimals up to 38 digits when interacting with these data stores.

 

I hope this information helps. Please do let us know if you have any further queries.

 

Thank you.

View solution in original post

6 REPLIES 6
v-cboorla-msft
Community Support
Community Support

Hi @cduden 

 

Thanks for using Microsoft Fabric Community.

 

In MySQL database the maximum total number of decimal digits to be stored. This number includes both the left and the right sides of the decimal point. The precision must be a value from 1 through the maximum precision of 38.

For more details please refer : decimal and numeric (Transact-SQL).

 

Try to reduce the precision value of the decimal and execute the pipeline Copy activity.

 

If the issue still persist, please do let us know. Glad to help.

 

I hope this information helps. 

 

Thank you.

Hi @cduden 

 

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.

 

Thanks.

The link you provided applies to SQL Server (and other MS platforms) not to MySQL.  MySQL allows for more precision:  MySQL :: MySQL 8.0 Reference Manual :: 14.24.2 DECIMAL Data Type Characteristics

 

I assume this means that the Data Pipeline tool only accepts up to 38 points of precisions?

 

Thanks.

Hi @cduden 

 

Yes, In Microsoft Fabric Pipelines, the behavior is slightly different. While it leverages underlying data storage solutions like Azure Synapse or SQL Server, there isn't a direct equivalent for setting the maximum precision for decimals within the pipeline itself.

These underlying data platforms support a maximum precision of 38 for the decimal data type. This means Fabric Pipelines will work with decimals up to 38 digits when interacting with these data stores.

 

I hope this information helps. Please do let us know if you have any further queries.

 

Thank you.

Reducing the precision of the source column in MySQL did fix the problem.   Thanks for your help.

Hi @cduden 


We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.

 

Thanks.

Helpful resources

Announcements
FabricCarousel_June2024

Fabric Monthly Update - June 2024

Check out the June 2024 Fabric update to learn about new features.

PBI_Carousel_NL_June

Fabric Community Update - June 2024

Get the latest Fabric updates from Build 2024, key Skills Challenge voucher deadlines, top blogs, forum posts, and product ideas.