SAP = BIG = not a reason to do stuff in english
DBMS = inherently English domain because people don't use their own language, that's self-referential
Using German comments makes perfect sense, SAP being a German company.
It works like this: a company starts out making a product for their local market, they get successful and branch out, and then a large amount of time later their code gets opened up to programmers not familiar with the native language.
Now, if the company were American, nobody would have a problem with dealing with identifiers and comments in what is for them a foreign language, say English.
But I really don't see why an American programmer would have a bigger problem dealing with identifiers and comments in German than vv.
Computer programming is not an exclusively English domain, and if to you code with identifiers and comments in a foreign language is hard to read then you have a bit of a hint how much effort the rest of the world has to make in order to make that step.
The fact that English got there 'first' is already enough of a head start, that shouldn't mean it becomes mandatory.
Something similar happens in the world of scientific publishing, where basically publishing in Spanish, Greek or Dutch is equal to not publishing at all.
An algorithm with Dutch, German or Swahili identifiers and comments is exactly equivalent to one in English.
Probably if you spent enough time you could figure out what the comments meant even if you didn't speak the language. Not that that would be very productive, and that's why most larger companies (and definitely multinationals) standardize on English.
You should be happy that's the case, but it is by no means a requirement or a sign of not being professional. If 90% of the team is German I'm all for them coding in German.
PS: I would like to edit my previous comment on the "nobody can change except me"-thing but seem unable to do so. For clarification: I did mean it that takes initiative from me to change my preference and not to be denying written word by someone else as being able to change my mind (which would be obtuse and absurd since it would preclude learning anything from someone else).
Because you can't and you can 'catch' your mistake with a follow up comment there is absolutely no problem and the whole page makes sense.
What about DBs make it inherently English? If a German person needs to store data in a way that an Englishman might employ a DBMS, what construct does he turn to?
PS: btw: I am not an English native, nor a resident of any English-speaking country.
It doesn't, and I merely said that I think it's good practice to do so. (For various reasons, e.g. a multi-national team, possible maintenance and re-engineering scenarios where it might be helpful to use standardized abbreviations, etc.) I have personally worked on a reengineering project that used German identifiers because of a very specific ERP system--it was ultimately decided not to use English identifiers because the translations would be too cumbersome. (This was a small company, what I am trying to say is a company like SAP [big] code a DBMS [inherently English domain] using German comments makes no sense to me...)