Late comment here, but I really would suggest against translations in the DB. Like Tolakram said, it quickly becomes a maintenance nightmare. Files may seem more archaic, but they are a lot easier to merge at the end of the day. This means less work to maintain up-to-date translations. It means less work to maintain static data period.
There is a reason why they have DBAs and data migration engineers and the like - moving data between systems can be a pain to do and do right
Standardize on a format for static data, and stick with the DB where you have dynamic data and need persistence. This is the point in the conversation where I'd plug to use XML for static data because it gives you a far-more flexible format than INI/CSV/etc and has native support in .NET. Also, XML is a hop, skip and a jump from JSON which means super easy usage in web apps. (hint hint: web app for modifying/updating localized data)
Just food for thought.