Conceptual DB Design

[George Chilumbu]

We are a startup company, and we are trying to figure out who's responsibility it is to provide the conceptual design of the MySQL database whether its the DBA or the developers?

My take on this was the Developers understand what their applications need, and the functional requirements of the Application. So they should provide the conceptual design e.g., what tables would be needed for their Application. So once they provide the conceptual ideas, the DBA can then create the the tables and other things like indexes and stuff. 

What do you guys think on this matter?

[matthe...@percona.com]

Hey George,

Yes, developers know the application so they should be able to develop an initial schema. However, it is the DBA's job to know some parts of a schema can be inefficient and to suggest alternatives. For example, if a developer has a query that looks like "SELECT * FROM users WHERE username = 'foo' and email = 'b...@bob.com', the DBA should know that a composite index on (username, email) is better than two individual indexes.

It is ALWAYS important that developers check their queries using "EXPLAIN..."

[George Chilumbu]

Indeed, thats what i though should be the case as well.

Thanks Mathew.

--
You received this message because you are subscribed to a topic in the Google Groups "Percona Discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/percona-discussion/k1sJrLnQEqU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to percona-discussion+unsub...@googlegroups.com.
To post to this group, send email to percona-discussion@googlegroups.com.
Visit this group at https://groups.google.com/group/percona-discussion.
To view this discussion on the web visit https://groups.google.com/d/msgid/percona-discussion/d2deffd4-ff1b-46e3-ba67-6b9686904254%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Purpose is the key to success. You can easily be successful in the wrong things.