Tag Archives: database design

A Domain for Data

A domain is a set of possible values (among other definitions). I use this word a lot in my work, often with a problem domain (the thing you’re trying to solve) or the domain of possible values (like the US … Continue reading

Posted in Editorial | Tagged | Comments Off on A Domain for Data

Your Biggest Data Model Complaints

I’ve been working with databases for a long time and there are no shortage of things I’ve seen other people do that I don’t like. Sometimes I shake my head a little. Sometimes I might groan inwardly (hopefully not aloud), … Continue reading

Posted in Editorial | Tagged | 6 Comments

Poor Database Design Realities

One of the interesting things that I see at Redgate Software is how idealistic our developers and engineers can be. They often build our database DevOps products with the idea that customers will use well-designed databases. The systems will have … Continue reading

Posted in Editorial | Tagged , | Comments Off on Poor Database Design Realities

Having Data Modeling Standards

While working with a customer recently, they mentioned that they have certain standards for their objects. They require a PK, and it’s the name of the table with _PK added. They also have some standards, like CustomerName vs. CustomerNames for … Continue reading

Posted in Editorial | Tagged , | 2 Comments