Hi

I have PK defined to all tables via DDT and deployed to customer already. I found that I missed out index fillfactor. I tried to change the fillfactor and rebuild package to deploy to customer again. However, I hit error PK constaint must be drop first before able to change fillfactor.



What should I do for this? Should I remove the PK, and create it again via DDT as workaround?



Thank you

Still having to deal with this.

I am frustrated because the DDT resets the index values back to zero everytime you modify the table structure.  I don't know why and it is a real pain to either reset all the indexes back to whatever I want them to be after every time I open a table structure and then hit save.  So usually I just ignore them and skip past the errors on the deployment log, which is also a pain since you can't copy and paste or otherwise save the DDT deployment log.

Requested solutions:

1. Do not modify the fillfactor percentage when doing table structure saves (In the DDT editor).
2. Set a default fillfactor index as a database property and have it automatically apply to all indexes (In the DDT editor).
3. Allow copy/paste of deployment log, or not make the form modal so I can view it and still make changes to the DDT, without having to find the text deployment log and then find where I was at.
4. Just not modify the fillfactor on deployment for exisiting indexes.  I don't know if this is possible or if fillfactor is a required paramater, unless you are creating a new index just leave it alone for existing indexes.

Jason Seidell

Programmer/Analyst

Infinedi

Jason, the developers are looking into this. I'll get back to you (or they will) once we've had a look at it.

Jason,



I am trying to reproduce this and can't. What are the steps to reproduce? What version of StrataFrame do you have installed?