How can we help you today? How can we help you today?
Guenter
Hi Jon, thanks for the hint. That toggle gives me the format I wanted to see! I do remember though, htat there was another issue that took me to set the flag otherwise, but unless I find that again, I'm happy with your solution. / comments
Hi Jon,thanks for the hint. That toggle gives me the format I wanted to see!I do remember though, htat there was another issue that took me to set the flag otherwise, but unless I find that again, ...
0 votes
After looking at it, the difference seems to come from the option "Collapse statements shorter than 40 characters". When I toggle this setting, the formatting gets right - so maybe it's just a glitch in the shortening formatter? / comments
After looking at it, the difference seems to come from the option "Collapse statements shorter than 40 characters". When I toggle this setting, the formatting gets right - so maybe it's just a glit...
0 votes
Hi Peter, there is no "error" in the product, it's just a missing feature.  Imagine the following: a table "Customers" in database A with a CustomerID from an autoincrement column that contains the customers of interest in your working database a table "ImportCustomers" in database B that contains a superset of customer data imported from some 3rd party a procedure prepareCustomers in database B that retrieves the CustomerID from table "Customers" in database A and joins it with the "ImportCustomers" in database B on some condition to find existing customers and writes new attributes to a table "ETL.Customers" in database B a procedure updateCustomers in database A that calls prepareCustomers in database B and then merges the content of ETL.Customers from database B into Customers in database A Now some day the third party offers an additional column "Preferred Database Tool Vendor". To import that, I have to  add a column to Customers in database A add a column to ImportCustomers in database B add a column to ETL.Customers in database B modify the prepareCustomers function in database B so it can use the newly created column in database A as a join criteria modify the updateCustimers function in database A to use the newly created column in ETL.Customers With the current version of SQL Compare, I can only generate one script per database. But I cannot run the script for database A before the script for database B because the column in ETL.Customers in database B is missing. And I cannot run the script for database A after the script for database B because the column in Customers in database A is missing. I would like to have ONE script for both databases that  creates/modifies all tables in A creates/modifies all tables in B creates/modifies all Views in A and B, honoring dependencies between views in both databases creates/modifies all stored procedures in A and B, honoring dependencies between procedures in both databases In the above case, the correct order would be modify Customer in A modify ImportCustomer in B modify ETL.Customer in B modify prepareCustomer in B modify updateCustomer in A Hope this clarifies my issue. / comments
Hi Peter,there is no "error" in the product, it's just a missing feature. Imagine the following: a table "Customers" in database A with a CustomerID from an autoincrement column that contains the c...
0 votes