From: esquel@sommarskog.se   
      
   m (miroslavsi@gmail.com) writes:   
   > Databases are on different servers, and they have different server   
   > collation.   
   >   
   > "Doesn't work properly" means that given example function   
   > cannot be compiled in B database (has error, see posts before) while in   
   > database A compiles correctly (there are no errors)   
   >   
   > So we determined that is becouse different server collation.   
   >   
   > Question is what to do to avoid compilation errors in db B, but without   
   > changing sql function code, becouse code is encrypted.   
      
   I'm afraid that you're stuck. That is, you either need to change the   
   code, or change the server collation. Or give up the restore entirely.   
      
   The recommendation I can give is to use a case-sensitive collation in   
   development, and also stick to lowercase identifiers consistently to   
   avoid problems like these.   
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Books Online for SQL Server 2005 at   
   http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx   
   Books Online for SQL Server 2000 at   
   http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)