Creating an inventory database in sql server 2008
-
Hi I need to create an inventory database using sql server 2008 and want to know on how i will proceed, what are the steps,etc ? can someone please provide me with some advice? Thanks
- Download SQL Server 2008 R2 Express[^] 1) Install it 2) Read up on relational database management systems 3) Read up on database normalisation 4) Perform an inventory of what you have and decide how you want to represent it in your database 5) Ask more specific questions in online fora Really, it depends on what you have and how you picture it in your head. The more tables the better! :-D
-
Hi I need to create an inventory database using sql server 2008 and want to know on how i will proceed, what are the steps,etc ? can someone please provide me with some advice? Thanks
-
- Download SQL Server 2008 R2 Express[^] 1) Install it 2) Read up on relational database management systems 3) Read up on database normalisation 4) Perform an inventory of what you have and decide how you want to represent it in your database 5) Ask more specific questions in online fora Really, it depends on what you have and how you picture it in your head. The more tables the better! :-D
PIEBALDconsult wrote:
The more tables the better
Ehm, only if you really need them...
"When did ignorance become a point of view" - Dilbert
-
PIEBALDconsult wrote:
The more tables the better
Ehm, only if you really need them...
"When did ignorance become a point of view" - Dilbert
I once inherited a database in whcih the original programmer had created seperate tables for each and every field - eg instead of: Table "clients": ID Name Address PostCode etc They had: Table "clients" ID Name Table "addresses" ClientID Address Table "PostCodes" ClientID PostCode etc et-bloody-cetera.... dozens of tables. X| You can just imagine the SQL statements....
-
I once inherited a database in whcih the original programmer had created seperate tables for each and every field - eg instead of: Table "clients": ID Name Address PostCode etc They had: Table "clients" ID Name Table "addresses" ClientID Address Table "PostCodes" ClientID PostCode etc et-bloody-cetera.... dozens of tables. X| You can just imagine the SQL statements....
If you have a table with very many columns and you often select just a subset of them, then I can understand if you split the table for performance reasons. But what you inherited is just ridiculous. And it doesn't have anything to do with normalization.
"When did ignorance become a point of view" - Dilbert
-
Look here: Data Models[^] for database design options.
I don't speak Idiot - please talk slowly and clearly 'This space for rent' Driven to the arms of Heineken by the wife