Tag Archives: database design

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

Concurrency Challenges Around Schema Changes

I saw a great question on Twitter from Frank Pachot, a developer advocate of Yugabyte. He wrote: Without thinking how your preferred database deals with it, what do you expect if: session 1 starts to reads table T session 2 … Continue reading

Posted in Editorial | Tagged , | 2 Comments