× Heads up!

Aqua Data Studio / nhilam

Follow
IDE for Relational Databases
×
coengeurtsen reported 2024-08-06T00:17:40Z  · last modified 2024-08-06T00:17:40Z

SQL Server fillFactor property on keys and indexes


usability
Dev
QA
Priority Low
Complexity Easy
Component Tools - ER Modeler
Version 23.0

Hi i found out that the case of the word fillfactor is different when the property is used for Primary Keys or for indexes

See examples below.

It would be very helpfull if these words would have the same case usage. When using a different case the property is not recognized by the Er modeler when you compare with the database. 

 

<Constraint table="4352" name="PK_InterfaceBatch" type="PrimKey">

        <Option name="noRecomputeStats" class="Boolean" value="false"/>
        <Option name="ignoreDupKeys" class="Boolean" value="false"/>
        <Option name="allowPageLocks" class="Boolean" value="true"/>
        <Option name="padIndex" class="Boolean" value="false"/>
        <Option name="allowRowLocks" class="Boolean" value="true"/>
        <Option name="clustered" class="Boolean" value="true"/>
        <Option name="fillFactor" class="Integer" value="100"/>
        <ConstraintColumn id="4353"/>
    </Constraint>
 
 
<Index table="0" name="IX_AanslagGroep_SoortaanslagId" schema="dbo" database="SOVASQLDEV">
        <Option name="allowPageLocks" class="Boolean" value="true"/>
        <Option name="allowRowLocks" class="Boolean" value="true"/>
        <Option name="fillfactor" class="Integer" value="100"/>
        <IndexColumn id="3" sequence="0" ascending="true"/>
    </Index>
 

 

Issue #15949

New
 
 
Completion
No due date
No fixed build
No time estimate

About AquaClusters Privacy Policy Support Version - 19.0.2-4 AquaFold, Inc Copyright © 2007-2017