Ok, that is helpful. I see I can convert the charset and collation on the database and tables. Do I have to do anything to the data? Part time DB Admin, Charles -------------------------------------------------------------- Charles Lambrecht Computer Operations Manager University of Tennessee College of Veterinary Medicine Email: cgl@utk.edumailto:cgl@utk.edu -------------------------------------------------------------- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Gerald Young Sent: Wednesday, October 16, 2013 5:51 PM To: User questions and discussions about OTRS. Subject: Re: [otrs] OTRS 2.4.7 - Best practice to convert table charset collation before upgrades? There are (more than) two ways to go about this. 1) use phpmyadmin to change coalation per table (tedious) 2) mysqldump, global search/replace the result, (first make another, verified backup!) and then drop the database create the database and load from modified backup. Which to do? Oh, that's the question. and neither are *fast*... one requires a lot of hunt, click click click change, and the other is ... well, as long as you have *all* the tables, probably a bit faster, though it does mean that you'll be doing a search/replace through a potentially fairly large text file (NotePad++ or vim would be recommended). or https://www.google.com/search?q=mass+change+collation+mysql On Wed, Oct 16, 2013 at 5:40 PM, Lambrecht, Charles (Charles) mailto:cgl@utk.edu> wrote: Hello, As I wade through having moved OTRS to a new server, I've run the Support Assessment on my OTRS 2.4.7 system. I get the error: Check if the client uses utf8 for the connection. Your client connection is utf8. OK Check if the database uses utf8 as charset. Your database character setting is utf8. OK Check database utf8 support. Your database version supports utf8. OK Check the utf8 table charset collation. Your charset collation is set to Invalid charset collation for: article[latin1_swedish_ci], article_attachment[latin1_swedish_ci], article_flag[latin1_swedish_ci], article_plain[latin1_swedish_ci], article_search[latin1_swedish_ci], article_sender and on for every table. What is the best practice to convert the table charset collation and the data before moving forward with upgrades? Regards, Charles ----------------------------------- Charles Lambrecht Computer Operations Manager University of Tennessee College of Veterinary Medicine Email: cgl@utk.edumailto:cgl@utk.edu -------------------------------------------------------------- From: otrs-bounces@otrs.orgmailto:otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.orgmailto:otrs-bounces@otrs.org] On Behalf Of LQ Marshall Sent: Wednesday, October 16, 2013 9:50 AM To: 'User questions and discussions about OTRS.' Subject: Re: [otrs] restore.plhttp://restore.pl. doesn't restore all data From: otrs-bounces@otrs.orgmailto:otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Lambrecht, Charles (Charles) Sent: Wednesday, October 16, 2013 8:18 AM To: User questions and discussions about OTRS. Subject: Re: [otrs] restore.plhttp://restore.pl. doesn't restore all data Yes, that was an excellent suggestion. My 1.5 GB file only has 4 tables... :( Well, it's off to see how to restore via the physical files (luckily, I have them!) ________________________________ An unverified back-up process is a potential heart ache. I run through all of my back-ups at least once a year to assure they function as expected. --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs