Skip to main content

SQL Server Indexes fragementation

  • October 29, 2021
  • 2 replies
  • 0 views
M
Hello,
I am SQL Server DBA.
I have an index fragmentation problem with an application using Uniface 9.7.
Indexes fractionated to more than 90% in less than 24 hours. The developer tells me that the problem is related to Uniface.
I can't find anything about it.
Has anyone come across this problem before ?
Thank you,

------------------------------
Marc Leroi
Rocket Forum Shared Account
------------------------------

    2 replies

    Gianni Sandigliano
    Forum|alt.badge.img
    Hello,
    I am SQL Server DBA.
    I have an index fragmentation problem with an application using Uniface 9.7.
    Indexes fractionated to more than 90% in less than 24 hours. The developer tells me that the problem is related to Uniface.
    I can't find anything about it.
    Has anyone come across this problem before ?
    Thank you,

    ------------------------------
    Marc Leroi
    Rocket Forum Shared Account
    ------------------------------

    Hi Marc,

    NO, I've never seen in my 30+ yrs with Uniface a situation like the one described...not with SQL Server, nor with another (R)DBMS!

    My initial gotfeel is: Uniface could hardly be the real origin of the issue you've focus on...probably some design decisions were taken before Uniface being used to implement the application.

    It would be interesting to dig a little bit more on context details:
    - Which kind of index is it? PrimaryKey, CandidateKey, ExternalKey, JustForTuningKey?
    - Which is underlying table usage rate: inserting rate, update rate, delete rate, each one per day?
    - Table total number of records? Table total size on disk?
    - Is the underlying table used as a temporary work area?
    - Is that index often updated because are updated one or more underlying fields due to implemented business rules?

    This last question is important if the index type is PrimaryKey...

    Hope those questions could help you!

    Regards,
    Gianni



    ------------------------------
    Gianni Sandigliano
    Italy
    ------------------------------
    PillarOfWisdom1: Inject yourself with some fantasy to NOT die of realityPillarOfWisdom2: The secret for a long healthy life is: eat half, walk double, laugh three times and love without measure! (Chinese saying)PillarOfWisdom3: Barcollo ma non mollo!
    M
    • Marc Leroi
    • Author
    • New Participant
    • November 9, 2021

    Hi Marc,

    NO, I've never seen in my 30+ yrs with Uniface a situation like the one described...not with SQL Server, nor with another (R)DBMS!

    My initial gotfeel is: Uniface could hardly be the real origin of the issue you've focus on...probably some design decisions were taken before Uniface being used to implement the application.

    It would be interesting to dig a little bit more on context details:
    - Which kind of index is it? PrimaryKey, CandidateKey, ExternalKey, JustForTuningKey?
    - Which is underlying table usage rate: inserting rate, update rate, delete rate, each one per day?
    - Table total number of records? Table total size on disk?
    - Is the underlying table used as a temporary work area?
    - Is that index often updated because are updated one or more underlying fields due to implemented business rules?

    This last question is important if the index type is PrimaryKey...

    Hope those questions could help you!

    Regards,
    Gianni



    ------------------------------
    Gianni Sandigliano
    Italy
    ------------------------------
    Gianni,

    Thank you very much for this reply.
    I expected that.
    I can go back to the developer to fix this.

    Yours,

    ------------------------------
    Marc Leroi
    Rocket Forum Shared Account
    ------------------------------

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement