Comments
Sort by recent activity
I ran this and I got back: version "1.3" of extension "log_fdw" is already installed / comments
I ran this and I got back:version "1.3" of extension "log_fdw" is already installed
@Bill_E - Yes, has to be in both tasks - Build and Release. That's how I got my pipelines working again. I left off the last set of digits... I only used this in the required version: 4.3.20259 / comments
@Bill_E - Yes, has to be in both tasks - Build and Release. That's how I got my pipelines working again.I left off the last set of digits... I only used this in the required version: 4.3.20259
Also consequently, the Release Task is also broke for same reason. [image] Had to set specific version there too. / comments
Also consequently, the Release Task is also broke for same reason. Had to set specific version there too.
More info: SCA version 4.3.20259.22134 works fine. So the latest version breaks the connection string connecting using Azure DevOps. / comments
More info:SCA version 4.3.20259.22134 works fine.So the latest version breaks the connection string connecting using Azure DevOps.
NerdGirlSteph - I had to uninstall SQL Prompt then install the file linked above. I did not lose my tabs, history, snippets, or settings. To save your settings, go into Options -> Export save your snippets by going into Snippet Manager, and seeing the path, and moving them somewhere else. That's the safest way, I didn't do any of that. [image] / comments
NerdGirlSteph - I had to uninstall SQL Prompt then install the file linked above. I did not lose my tabs, history, snippets, or settings.To save your settings, go into Options -> Exportsave your sn...
Same here. I get the error: The Target Principal Name is incorrect. Cannot generate SSPI context. Nothing changed other than updating SQL Prompt on SSMS 18.6 SQL Server version I'm running is SQL 2017. / comments
Same here.I get the error: The Target Principal Name is incorrect. Cannot generate SSPI context.Nothing changed other than updating SQL Prompt on SSMS 18.6SQL Server version I'm running is SQL 2017.