Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • So you are saying you have chosen wrong collation setting for the SQL Server ? Commented Nov 17, 2016 at 13:47
  • No, the wrong language. A German SQL Version was installed. This causes problems with SQL Statements coming in. Please read: dba.stackexchange.com/questions/154978/… Commented Nov 17, 2016 at 13:49
  • Have you tried just setting the regional settings in Windows to English? (Date / Time / Keyboard) But I would recommend having an English Windows Server and an English SQL Server installation any time. Stuck with German / German at the moment. You might be able to backup the master/msdb databases and reinstall SQL Server and then resetore the master and msdb database over the new installation. You would then have an English SQL Server running on a German Windows Server. Never tried it myself. Commented Nov 17, 2016 at 14:20
  • BTW Installations of different language versions of SQL Server instances on the same computer are not supported. Commented Nov 17, 2016 at 14:31
  • Had same thoughts and made some spikes - but with backup/restore of master I ran into new trouble. The solution below is very straight forward and working in my case so I will go for that and hold on until - hopefully not - new problems may happen... Commented Nov 17, 2016 at 14:33