I work for a large state department. Consequently, the department I work for is, I believe, over 100 years old. Obviously, no one was writing databases back in 1923. 🙂
But that does mean that what we have a mixed bag. I'm not sure anyone who works here have any idea what the data modeling standards were when our hundreds of databases were created. And some people have been here for 30+ years.
Several databases started their lives as a single office app written in MS Access, that were upgraded to SQL Server, leaving all the databases, tables, and column names alone. Table and column names are all over the map.
Some apps we have are third party applications, so whatever the vendor thinks of naming their databases and tables, is what it is.
And for the rest of them, each development team creates their own database. We use Entity Framework, but surprisingly we do not use EF Migrations. Instead, some people use TOAD by Quest. Others, well they just wing it. What puzzles me a lot is why doesn't anyone use the DBAs to help with this task.
Kindest Regards, Rod Connect with me on LinkedIn.