Hello,
I am developing an application that uses a database.
As I have designing the database, I am thinking about the future framework for the system and wanted to engineer the database with the best practices.
I have 3 main functions.
- Employee Management
- Equipment Management
- Configuration Control
I would like to know the pros and cons of creating 3 separate MSSQL databases on the same server and linked them with views versus 1 MSSQL database with different schema(s) for each function. Or is there a third recommended method.
Thanks
jlimited
I am developing an application that uses a database.
As I have designing the database, I am thinking about the future framework for the system and wanted to engineer the database with the best practices.
I have 3 main functions.
- Employee Management
- Equipment Management
- Configuration Control
I would like to know the pros and cons of creating 3 separate MSSQL databases on the same server and linked them with views versus 1 MSSQL database with different schema(s) for each function. Or is there a third recommended method.
Thanks
jlimited