Content Database Collation

Question

Are there any known issues for keeping SharePoint cotent database on a database instance which has a different default code page (different from the code page 1252, which SharePoint uses)?

Someone told me we will run into issues because the temp database on this instance will have a different code page (it will be in the instance's default code page).  According to him, when the temp database is used we will get mismatching collation error, unless all the charcter fields are in unicode.

I find it hard to believe.  If what he's saying is true, this is not really a problem for SharePoint content database, but any database that uses a different code page from the default code page of the databaase instance that it is in.  If that's the case, why would SQL server even allow users to create a database with a different code pages at all?

Has anyone actually had this issue - SharePoint not working properly keeping its content database on a database instance with code page other than 1252, personally?  Or, are there any people who have a setting like this, but have been able to run SharePoint for a long time without any issues?

Thank you for your input in advance.