Comments
Sort by recent activity
Hi Joe. Within the YAML editor in Azure DevOps there should be a "Show assistant" button on the top right. This tool allows you to configure the task with the UI and then insert the YAML straight into the pipeline. I hope this helps. / comments
Hi Joe. Within the YAML editor in Azure DevOps there should be a "Show assistant" button on the top right. This tool allows you to configure the task with the UI and then insert the YAML straight i...
Hi, You should be able to use SQL Change Automation 3 Core Edition in Visual Studio 2017 Enterprise. If this isn't working for you please open a support ticket here and we will investigate this. Thanks. / comments
Hi,You should be able to use SQL Change Automation 3 Core Edition in Visual Studio 2017 Enterprise. If this isn't working for you please open a support ticket here and we will investigate this.Thanks.
Monday said:
This is the hype! I will check this out later but I am hoping that little input box next to the database name can be used to filter the tables. That was one of my biggest gripes using the VS extension.
Yes, you are able to filter tables! / comments
Monday said:
This is the hype! I will check this out later but I am hoping that little input box next to the database name can be used to filter the tables. That was one of my biggest gripes ...
Thank you for reporting this Cindy. We recently became aware of this issue and are working on a fix. This fix will be included in a future update of the SSMS extension. / comments
Thank you for reporting this Cindy.We recently became aware of this issue and are working on a fix. This fix will be included in a future update of the SSMS extension.
TheSQLGuru said:
Would it be useful for people who DON'T use this product to take the survey?
We would like to know how we can improve our product further, so feedback from anyone that has tried the product is useful, even if they are not currently using it. Thanks. / comments
TheSQLGuru said:
Would it be useful for people who DON'T use this product to take the survey?
We would like to know how we can improve our product further, so feedback from anyone that has t...
WoehrMi said:
Another problem I experienced after update to 4.0.19270.10947: I cannot open old migration scripts from the Visual Studio Solution explorer or from the VS error list. A double click on the item raises now an error msg dialog from Visual Studio: "Failed to create an editor. Value cannot be null. Parameter name: password".
Please could you try opening the database connection window in Visual Studio and testing the database connection. I hope this will fix this issue. We will look further into the issue you are facing with very large package files. If you are able to open a support ticket here we can look into your specific case. Thanks. / comments
WoehrMi said:
Another problem I experienced after update to 4.0.19270.10947: I cannot open old migration scripts from the Visual Studio Solution explorer or from the VS error list. A double c...
WoehrMi said:
Another problem I experienced after update to 4.0.19270.10947: I cannot open old migration scripts from the Visual Studio Solution explorer or from the VS error list. A double click on the item raises now an error msg dialog from Visual Studio: "Failed to create an editor. Value cannot be null. Parameter name: password".
Please could you try opening the database connection window in Visual Studio and testing the database connection. I hope this will fix this issue. We will look further into the issue you are facing with very large package files. If you are able to open a support ticket here we can look into your specific case. Thanks. / comments
WoehrMi said:
Another problem I experienced after update to 4.0.19270.10947: I cannot open old migration scripts from the Visual Studio Solution explorer or from the VS error list. A double c...
WoehrMi said:
Another problem I experienced after update to 4.0.19270.10947: I cannot open old migration scripts from the Visual Studio Solution explorer or from the VS error list. A double click on the item raises now an error msg dialog from Visual Studio: "Failed to create an editor. Value cannot be null. Parameter name: password".
Please could you try opening the database connection window in Visual Studio and testing the database connection. I hope this will fix this issue. We will look further into the issue you are facing with very large package files. If you are able to open a support ticket here we can look into your specific case. Thanks. / comments
WoehrMi said:
Another problem I experienced after update to 4.0.19270.10947: I cannot open old migration scripts from the Visual Studio Solution explorer or from the VS error list. A double c...
Hi Greg, Thank you for reporting this. I have managed to reproduce this issue, which appears to be caused by SSMS 18 no longer accepting authentication arguments. We are working on a fix for this which should be included in the next release of SQL Change Automation. Thanks, Ben / comments
Hi Greg,Thank you for reporting this. I have managed to reproduce this issue, which appears to be caused by SSMS 18 no longer accepting authentication arguments.We are working on a fix for this whi...