Post reply

Table Partitioning as it relates to table escalation

  • April 25, 2014 at 5:38 pm

    #396662

    In SQL 2005, can I partition a table to help with more row and page locks versus immediately jumping to table locks?

    I have one table that seems to always table lock on every transaction. Will partitioning that table help with partition locks, or do I need the application team to alter the code on app side to understand the table is partitioned? My bosses are talking about turning on trace flags (1211 or 1224) and doing other things that I would rather not try until I have ruled out all other options.

  • April 26, 2014 at 7:54 am

    #1708958

    Before you start looking at partitioning you may want to look at the code that is forcing the table locks and the current indexing (clustered/nonclustered) on the table.

  • April 26, 2014 at 7:56 am

    #1708959

    Start by tuning the queries. Partitioning is not a silver bullet.

    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 3 posts - 1 through 2 (of 2 total)

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