Question regd. the database design..

  •  

    Hi Dudes,

    I have a query regd the design of the database.

    Let me explain my requirement. I have some set of xml files(contains large chunk of data). I want to store them in the database and need to query against that. I have a .NET application, when I run it, it takes the data from around (1000 to 10000)xml files and store it in the DB. So each time I run the application I will store all these data in a Table. For each run max 10million rows will be inserted into the table. I need to run this application weekly once. So If I maintain only one table for this, then over a period huge data wil be stored, and when I query against it, it's taking lot of time to fetch the rows. So I have a thought of going to create dynamically a table for each application run, so that can improve the performance. But I need to use all Dynamic queries for retrieving the data.

    So please suggest me which way is the best out of these options.

    Either going for a single table and maintaing the whle data into it

    or creating a table dynamically for each run.

     

    Thanx.

  • Hello Mahesh,

    Do you require the earlier processed data? If so, you can go ahead with renaming the table created by adding the date to it before creating the actual table for today i.e., let us think that you have processed all 10 million rows y'day and today you need to process another 10 million rows. It would be better if you can rename the y'day data table by suffixing with y'day date and then go ahead with the creation of a new table.

    Hope this helps you.

    Thanks

     


    Lucky

  • I'd look into table partitioning. One partition per week.

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

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

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