Database Designing Issues - Need Urgent Help

  • 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

  • Please don't cross post. It just wastes people's time and fragments replies. Many of us read all the forums

    No replies to this thread please, direct replies to:

    http://www.sqlservercentral.com/Forums/Topic573066-361-1.aspx

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply