Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
shishirbabel
Starting Member
3 Posts |
 Posted - 2008-09-20 : 19:30:30
|
| I am in the process of developing an ERP which should have the capability of handling bulk data.My database is ready but i am bit confused that whether my database architecture is perfect or not on following grounds :1. I am having lengthy tables of up to 50 columns but all these 50 columns will not contain any redundant values so is it a good idea to keep single table for this or shd we keep it in multiple tables ?2. I am using transactions and stored procedures for saving , updating and deleting so if i will save the data in one table will it affect the performance of the system later on during the stage or not ?3. How i will ensure that database integrity is being maintained along with the fast accessibility.4. How to make sure that database changes are very rare so that development time line doesn't gets affected.Please let me know if you need more details about the database and project for better clarification i will be highly obliged if i can get good suggestions for improvements in the database.Thanks |
|
|
dexter.knudson
Constraint Violating Yak Guru
260 Posts |
Posted - 2008-09-21 : 23:33:54
|
| If this is what you mean by ERP: http://en.wikipedia.org/wiki/Enterprise_resource_planning . It is a big job! Some of the questions you are asking are very broad & would depend on requirements, technology you are using (eg front-end .Net?) & other design choices.How are you planning to maintain the data integrity? Are you planning to use foreign key relationships? In terms of the development time-line impact of changes, you should have a change management process in place. Then you can assess proposed changes to the requirements & advise users on time & cost impact. They can then make a decision on whether they want to proceed with it or not. |
 |
|
|
lepeniotis
Yak Posting Veteran
75 Posts |
Posted - 2008-09-22 : 05:57:51
|
| Well, creating a database for an ERP is not a thing that can be done by one Person. First of all you need a team or different teams to handle with the different parts of the ERP. You need an accountant consultant to explain you how the accounts and the different types of invoices work. After that you have to create the indexes for performance and of course the triggers. At ERPs DB design the most important are the triggers. I assume that for being assigned such a project you don't need suggestion on LogicaL and Physical Database design, so I will not be in such details. But again for the questions 2,3,4 you have to create well designed triggers. A book that might help you is DATABASE SYSTEMS forth edition. It can help you a lot at Desigining tips. But again I suggest you to ask an accountant consultant to consult you about the triggers which is the most important in this kind of applications.MSc Advanced Computing Science MSc Database ProfessionalSheffield Hallam UniversityMCP (70-229, 70-228)Industrial IT Engineer |
|
|
|
|
|
|
Database designing issues -- needs urgent help