Partinitioning Of Table of database

  • Basically, we are working on a table. There was a problem of LOCKS that persists because there are multiple users working on different entities on a particular column.(e.g different brokers)

    In order to rectify this problem we horizontally partition the table on the basis of entity and prepared a view on this basis using UNION ALL. Indexes are created on the table not on a View.

    The problem of Locks is resolved but now the Performance Issue is critical.

    Please suggest your views in order to resolve this issue.

    I am open to your suggestions and guidance.

    Thanks,

    with warm regards,

    Kavita .

     

     

     

     

     

     

     

  • What do you mean performance issue?

    Are you seeing a decrease in query times?

    One thing you MUST do is create check constraints on each table the check constraint is what your logic is on partitioning the data. This way the query optimizer will see the constraint and know what table to go through.

    Another question I have is do you have queries that join partitioned views to the same, or other partitioned views?

    I worked on a system, and when I did this query performance was very poor. So I had to write additional views doing the various join combinations.

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

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