# COLLATION error during call storage procedures in mysql

**URL:** <https://forums.percona.com/t/collation-error-during-call-storage-procedures-in-mysql/6509>\
**Category:** Other MySQL® Questions\
**Created:** [August 14, 2018, 2:16pm UTC](https://forums.percona.com/t/collation-error-during-call-storage-procedures-in-mysql/6509 "2018-08-14T14:16:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amna](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@Amna](https://forums.percona.com/u/Amna)\
**Post date:** [August 14, 2018, 2:16pm UTC](https://forums.percona.com/t/collation-error-during-call-storage-procedures-in-mysql/6509/1 "2018-08-14T14:16:08Z")

</div>

Hello,  
when i tried to call specific storage procedure in mysql, i faced the below error  
mysql\> call DBname.StorageProcedureName();  
ERROR 1253 (42000): COLLATION ‘utf8\_general\_ci’ is not valid for CHARACTER SET ‘latin1’

i have done a lot of search and all recommended to change character set and collation to UTF8, like below  
character-set-server = utf8  
collation-server = utf8\_general\_ci  
Actually i worried about this solution as it may be affect data consistency specially if DB contain foreign\_key ( [url][sql - Dangers of Changing encoding in mysql - Stack Overflow](https://stackoverflow.com/questions/36702672/dangers-of-changing-encoding-in-mysql%5B/url%5D) ) My questions now: 1. there is any solution rather than changing character set and collation to UTF8 2. if not, what’s the risk if i change from to utf8. 3. what’s the best character set and collation, utf8 or latin