SQL Database Design - best practice
Posted on 2013-11-21
We have a MS SQL database that we are planning to re-develop. We have 2 databases with stored procedure that communicate with each other via our in-house application we have developed.
We have several products tied into 2 databases. Our aim is to re-develop the database and compile the database into one database and have each of our products in a separate database.
We want to know from you experts, what is the best practice on how we can improve our database, or is there an example of a database structure we can follow.