I am surprised this isn't talked about more because it is an issue if you want to keep local and remote sites syncronized. My question is "Is this recommended? If I change this setting now, will it screw up the several SS sites I already have running on my local? "

Quote from http://www.parkroad.co.za/blog/2007/02/07/mysql-case-sensitivity-of-table-names-between-windows-and-linux-systems/

"Because windows is case-insensitive, when you create a MySQL table or export tables for use on a linux system, all table names will be lowercase by default. This will cause problems when the dump imported into MySQL on linux, as any calls to the original mixed case tables will result in errors, as these tables don’t actually exist.

To fix this, you can look for the setting: lower_case_table_names in your my.ini file, found in or around: C:\Program Files\MySQL\MySQL Server 4.1, depending on which version you are running. If you don’t find the setting, you can just add it to the end of the my.ini file, as I did, like so:

lower_case_table_names=0

Remember to restart the MySQL service before you test whether or not it works.

You can also set this value to 2 if you want, and then: “MySQL converts them to lowercase on lookup. Name comparisons are not case sensitive.”"

To me it isn't an issue. There's no real reason to have a local and a remote copy of the same DB since ss supports draft changes that you can preview before publishing them. For testng of course, you need some data to test on, but it doesn't have to be a copy of the live site.