Skip to main content
Solved

Problem with SQL Server and special characters

  • June 8, 2022
  • 4 replies
  • 609 views
larsk
Contributor
Forum|alt.badge.img
  • larskContributor
  • Contributor
  • 3 replies

I am having problem writing attributes with swedish characters (åäö) to a mssql table.

The characters get replaced by other strange characters instead. I am using FME Desktop 2022.0.0.2 build 22343.

The database is set up with collation Finnish_Swedish_CI_AS as it should be.

Other programs such as QGis is writing åäö to the table correctly.

Is there some kind of setting that I need to do in FME or is this a bug?

Best answer by debbiatsafe

Hi @larsk​ ,

Thanks for letting us know! This behaviour is due to a bug that was fixed in FME 2022.0.1 build 22346. Installers can be found at https://www.safe.com/support/downloads/

 

If any users running into this issue are unable to upgrade to the build above or newer, please try one of the following workarounds:

  1. Disabling Bulk Inserts on the SQL Server writer
  2. Updating Microsoft OLE DB Driver for SQL Server to at least version 18.4 and ensure Use Unicode UTF-8 for worldwide language support is enabled on the Windows System Locale setting
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

david_r
Celebrity
  • david_rCelebrity
  • 8391 replies
  • June 8, 2022

My first recommendation would be to install the SQL Server ODBC driver, which FME should use automatically, when present. I believe it's much more recent than the 2012 Native Client installed with FME (unless something's changed in 2022).

https://docs.microsoft.com/en-us/sql/connect/odbc/download-odbc-driver-for-sql-server?view=sql-server-ver16

You'll need to restart FME after the installation.

larsk
Contributor
Forum|alt.badge.img
  • larskContributor
  • Author
  • Contributor
  • 3 replies
  • June 8, 2022

That didn't help. But I tried the latest beta version and it works there so I guess it's a bug that is fixed in the latest beta.

Thanks anyway!

debbiatsafe
Safer
Forum|alt.badge.img+21
  • debbiatsafeSafer
  • Safer
  • 648 replies
  • Best Answer
  • June 8, 2022

Hi @larsk​ ,

Thanks for letting us know! This behaviour is due to a bug that was fixed in FME 2022.0.1 build 22346. Installers can be found at https://www.safe.com/support/downloads/

 

If any users running into this issue are unable to upgrade to the build above or newer, please try one of the following workarounds:

  1. Disabling Bulk Inserts on the SQL Server writer
  2. Updating Microsoft OLE DB Driver for SQL Server to at least version 18.4 and ensure Use Unicode UTF-8 for worldwide language support is enabled on the Windows System Locale setting
larsk
Contributor
Forum|alt.badge.img
  • larskContributor
  • Author
  • Contributor
  • 3 replies
  • June 9, 2022

Thanks! Upgrading to the new version solved the problem.

Community Stats

32,065
Posts
121,730
Replies
39,691
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.