Spanish characters

Question

Spanish characters

johnnycash

Ten Centuries

Points: 1172
More actions
February 1, 2018 at 10:13 am

#333192

Hello to all gurus!
I've inherited a software application using a SQL 2008 DB. We migrated to 2014 and we are seeing the special characters in spanish being transformed (á, é, í, ó, ú, ñ and their uppercase counterparts) into unreadable characters when the application retrieves data for its UI and subsequently, when a row is saved, these transformated characters are being stored in the table (or tables). I'd like to know if this is something I can correct on the server side or should I raise hell with the software vendor to get it fixed (if it is an application issue)? Mind you, the application runs on an RDS farm in Windows 2012 R2 (English) with the US locale. Users access the application via Remote Desktop from spanish-speaking locations using their locale.
As I said, just wanted to hear that this is not a SQL issue rather a Windows/Remote Desktop or software issue.
Your kind replies are appreciated in advance!
Regards,
JC

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Luis Cazares SSC Guru Points: 183706 More actions · Answer 1

johnnycash - Thursday, February 1, 2018 10:13 AM
Hello to all gurus!
I've inherited a software application using a SQL 2008 DB. We migrated to 2014 and we are seeing the special characters in spanish being transformed (Ã¡, Ã©, Ã, Ã³, Ãº, Ã± and their uppercase counterparts) into unreadable characters when the application retrieves data for its UI and subsequently, when a row is saved, these transformated characters are being stored in the table (or tables). I'd like to know if this is something I can correct on the server side or should I raise hell with the software vendor to get it fixed (if it is an application issue)? Mind you, the application runs on an RDS farm in Windows 2012 R2 (English) with the US locale. Users access the application via Remote Desktop from spanish-speaking locations using their locale.
As I said, just wanted to hear that this is not a SQL issue rather a Windows/Remote Desktop or software issue.
Your kind replies are appreciated in advance!
Regards,
JC

Accentuated vowels and Ã‘'s shouldn't be a problem. I've worked on several databases in Mexico with default settings (meant for USA) without problems. This is something to do with the client side and how they handle strings.

Luis C.
General Disclaimer:
Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

How to post data/code on a forum to get the best help: Option 1 / Option 2

johnnycash Ten Centuries Points: 1172 More actions · Answer 2

Thank you Luis!

The weird part is that when it was running on SQL Server 2008, we did not see this happening. Now, while the server is running SQL Server 2014, the database compatibility mode was left at 2008 (as per the vendor's strong recommendation) so it throws me off that it is happening now hence my question, is it a SQL setting or a Windows setting?

Luis Cazares SSC Guru Points: 183706 More actions · Answer 3

johnnycash - Thursday, February 1, 2018 10:44 AM
Thank you Luis!
The weird part is that when it was running on SQL Server 2008, we did not see this happening. Now, while the server is running SQL Server 2014, the database compatibility mode was left at 2008 (as per the vendor's strong recommendation) so it throws me off that it is happening now hence my question, is it a SQL setting or a Windows setting?

I would say that it's neither and both. It's a mismatch between the code pages of SQL and the application that connects to it. It's similar to what happens when you convert from unicode to ansi strings.

Luis C.
General Disclaimer:
Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

How to post data/code on a forum to get the best help: Option 1 / Option 2

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 4

Can you compare the server settings or did you do an in place upgrade from SQL Server 2008 to SQL Server 2014?

johnnycash Ten Centuries Points: 1172 More actions · Answer 5

We compared the settings of both SQL servers and they are identical. However, in deeper research, I've found what was causing the issue and had nothing to do with the application or the server. We have a web service that pulls information from a third party and that was the culprit. it did not have the right code set in its code. We updated that and ran some test in our lab and all is fine now.

Thank you all and have a blessed day!

Regards,

subramaniam.chandrasekar SSCarpal Tunnel Points: 4223 More actions · Answer 6

johnnycash - Thursday, February 1, 2018 11:17 AM
We compared the settings of both SQL servers and they are identical. However, in deeper research, I've found what was causing the issue and had nothing to do with the application or the server. We have a web service that pulls information from a third party and that was the culprit. it did not have the right code set in its code. We updated that and ran some test in our lab and all is fine now.
Thank you all and have a blessed day!
Regards,

Okay, so web service was the culprit !!!