I am pretty well versed with SQL Server, MySQL, Oracle etc but putting these Database products aside, is there a resource that will help me design relational databases well? Is there something like patterns or best practices for database design?
I have seen a few times that database is often not scalable; people have personal preferences with keeping columns like isChecked column which is boolean in nature but stored as Char(1) with values like 'Y' and 'N' instead of 0 and 1 which to me sounds better. Ways not to commit common mistakes while doing database design?
Links to books or articles will be highly appreciated.
Thanks in advance.
The information requirements are the most important part.
Once you are done using the database, you must close it. You use the DB->close() method to do this. Closing a database causes it to become unusable until it is opened again.
Logical design. Physical design. Implementation. Monitoring, modification, and maintenance.
A few points:
There are numerous database design patterns. They aren't often nicely formalized, so you may have to simply look at lots of database design.
See, for example, Fowler's books on design patterns. Also Nock's Book.
There are blogs, like database programmer.
There's an IEEE book, On Pattern-Based Database Design and Implementation.
The Google Search (link) turned up 24M hits.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With