Tried different settings and was never able to eliminate these. I get a LOT of ALTER Table statements to ALTER COLUMN to the datatype and null/not null value that is already present. My issues is going to be when I fill in the property in the model, it is going to try to run an "add" when it really needs to do an "update" and the property value will never get set.
When reading extended properties from SQL 2016, modeler doesn't pick up any of the ones with a NULL value and generates an "addproperty" for all of them which comes back and says "property already exists" when ran. I have many extended properties that are set null until we figure out all the values to be populated. I don't understand why this tool is not the same.įirst of all, would like a way for the function to take into account the "generate" flag on each item and only generate scripts for those.Ĭomparing model to SQL 2016. I've used in the past other data modelling tools, power designer data architect and the e/r studio and their dialogs are snappy and fast. It is disruptive to my workflow because I want to make changes quickly. I don't understand why the dialogs aren't snappier. Let's say I want to modify a check constraint. It takes 3 seconds until the Attribute Properties dialog shows up. Now, I go to attributes and double-click on an attribute. It takes 3 seconds until the Entity Properties dialog shows up. Let's say I want to edit the attributes of an entity. It takes a few good seconds until a dialog shows up after clicking on an entity or attribute. I bring it up again because it annoys me greatly and perhaps you can do something about it. This is a complaint I've had for a very long time, since the days TDM was owned by the Czech company (the product had another name).
0 kommentar(er)
