Partitioning Split

  • I have tables partitioned by year, they are large tables. The filegroup they're on is large, but not inordinately so, around 60 gig. I'm trying to create a new year's partition with ALTER TABLE FUNCTION partitionfunctionname SPLIT RANGE (200700) and it has been running for an hour and a half already. Is this typical for large-ish databases or has something gone wrong here?

    --------------------------------------
    When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
    --------------------------------------
    It’s unpleasantly like being drunk.
    What’s so unpleasant about being drunk?
    You ask a glass of water. -- Douglas Adams

  • Stefan Krzywicki (9/1/2010)


    I have tables partitioned by year, they are large tables. The filegroup they're on is large, but not inordinately so, around 60 gig. I'm trying to create a new year's partition with ALTER TABLE FUNCTION partitionfunctionname SPLIT RANGE (200700) and it has been running for an hour and a half already. Is this typical for large-ish databases or has something gone wrong here?

    If SQL Server finds data that belongs to new splitted partition then SQL Server has to move that data. This process may be perceived as to be either fast or slow depending on how much data has to be moved around.

    _____________________________________
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at Amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
  • PaulB-TheOneAndOnly (9/1/2010)


    Stefan Krzywicki (9/1/2010)


    I have tables partitioned by year, they are large tables. The filegroup they're on is large, but not inordinately so, around 60 gig. I'm trying to create a new year's partition with ALTER TABLE FUNCTION partitionfunctionname SPLIT RANGE (200700) and it has been running for an hour and a half already. Is this typical for large-ish databases or has something gone wrong here?

    If SQL Server finds data that belongs to new splitted partition then SQL Server has to move that data. This process may be perceived as to be either fast or slow depending on how much data has to be moved around.

    There's no data in the affected tables that'd need to be moved.

    --------------------------------------
    When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
    --------------------------------------
    It’s unpleasantly like being drunk.
    What’s so unpleasant about being drunk?
    You ask a glass of water. -- Douglas Adams

  • Stefan Krzywicki (9/1/2010)


    PaulB-TheOneAndOnly (9/1/2010)


    Stefan Krzywicki (9/1/2010)


    I have tables partitioned by year, they are large tables. The filegroup they're on is large, but not inordinately so, around 60 gig. I'm trying to create a new year's partition with ALTER TABLE FUNCTION partitionfunctionname SPLIT RANGE (200700) and it has been running for an hour and a half already. Is this typical for large-ish databases or has something gone wrong here?

    If SQL Server finds data that belongs to new splitted partition then SQL Server has to move that data. This process may be perceived as to be either fast or slow depending on how much data has to be moved around.

    There's no data in the affected tables that'd need to be moved.

    If this is the case something is wrong.

    Can you see any locking in the system?

    Can you trace the session and see what is really going on?

    _____________________________________
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at Amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

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

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