This exception is happening because the SQL decimal type will map to the C# decimal type, and the default Parse behavior for decimal doesn't allow scientific notation. I'm reluctant to change that ...

I'm trying to implement DMS for our data replication purposes between two SQL Server instances with Change Tracking enabled. The problem I stumbled upon is specifically connected with decimal(19,0) ...