Activity overview
Latest activity by timetrak_aw
Didn't think to put this in the original post... SSMS is 13.0.16106.4. SQL Prompt version is 7.5.1.1000. Error comes up in a 2016 SQL Server (13.0.4001.0) or 2014 SQL Server (12.0.2000.8). If there's anything else that might be helpful, let me know. / comments
Didn't think to put this in the original post... SSMS is 13.0.16106.4. SQL Prompt version is 7.5.1.1000. Error comes up in a 2016 SQL Server (13.0.4001.0) or 2014 SQL Server (12.0.2000.8). If there...
Error Dialog When Using SSMS - Invalid name character in Workstation Id
I am getting an error dialog on an extremely frequent basis whenever I do any of the following in SSMS:
Saving Scripts
Executing Scripts
Change Tabs
Scrolling Object Explorer
I have no idea where...
This was a very surprising change, especially since there was no specific mention in any of the release notes. I understand the need to remove obsolete functionality, but you've inadvertently removed something that was a very useful feature of the source control product.
We have been using the extended property in order to determine what version an installed database is at, so our product bootstrap installer can upgrade the user to the right revision level. For example, if a customer is two releases behind, we can see they are at revision "A", and we know that "C" is current, so we run A_B and B_C upgrade packages to get them up to date.
Since we don't know what revision number changes are going to be until after they are committed, it would be very helpful if we could specify an extended property name somewhere and have the commit process update that extended property, similar to what was happening with the migration script system.
I think it would also help if the current revision level was displayed at all times somewhere in the UI, rather than just after the check-in. A good location could be following the database name on the Commit and Get Latest tabs. / comments
This was a very surprising change, especially since there was no specific mention in any of the release notes. I understand the need to remove obsolete functionality, but you've inadvertently remov...