1. We have moved from vBulletin to XenForo and you are viewing the site in the middle of the move. Though the functional aspect of everything is working fine, we are still working on other changes including the new design on Xenforo.
    Dismiss Notice

Need Database Design idea

Discussion in 'Database' started by PRamanan, Nov 28, 2007.

  1. PRamanan

    PRamanan New Member

    Hi shabir,

    I am indulged in developing Online Issue Tracking sytem.For that I have met with a problem in Database creation.

    The Sceneario is "The Database should be specific for each and every group of customers,For example initially A is a company with 10 users accessing the product after two days B is a company with 50 user accessing the same product".In this case the datase base should be provided to the two companies separately to maintain their transaction. How to handle this.

    Any sort of ideas is valuable for me.
    Thanks,
    Ramanan
     
  2. shabbir

    shabbir Administrator Staff Member

    You have the same thread almost 5 times and do not irritate the people who can help you. I have closed all your other threads with a reference to this one.
     
  3. narayan

    narayan New Member

    Sorry for the delayed reply.

    You can design the table with column name "Company name"
    based on the company name... you can filter the datas. Just create the same database schema
    and pass this to all companies. don't go for different schema for each company based on the company name
     
  4. skp819

    skp819 New Member

    The design process

    The design process consists of the following steps:

    • Determine the purpose of your database This helps prepare you for the remaining steps.
    • Find and organize the information required Gather all of the types of information you might want to record in the database, such as product name and order number.
    • Divide the information into tables Divide your information items into major entities or subjects, such as Products or Orders. Each subject then becomes a table.
    • Turn information items into columns Decide what information you want to store in each table. Each item becomes a field, and is displayed as a column in the table. For example, an Employees table might include fields such as Last Name and Hire Date.
    • Specify primary keys Choose each table‚Äôs primary key. The primary key is a column that is used to uniquely identify each row. An example might be Product ID or Order ID.
    • Set up the table relationships Look at each table and decide how the data in one table is related to the data in other tables. Add fields to tables or create new tables to clarify the relationships, as necessary.
    • Refine your design Analyze your design for errors. Create the tables and add a few records of sample data. See if you can get the results you want from your tables. Make adjustments to the design, as needed.
    • Apply the normalization rules Apply the data normalization rules to see if your tables are structured correctly. Make adjustments to the tables, as needed.
     
  5. xpi0t0s

    xpi0t0s Mentor

    Do the companies share the same data (a) just for read access (b) for read/write? Should each be able to see the other's data?

    One solution if they don't need to share data at all is just to give them different schemas to connect to and to duplicate the table structures (but not the data) in each schema.

    If they need to share data then the shared data can go into a schema accessible by both. but they should still both have their own schema for security/tracking purposes.

    Or they could both connect to the same schema, but if they do that then each company will have full control over the other company's data, which may not be desirable.
     

Share This Page