Comments
Sort by recent activity
Hi Jacky,
What's the version number of your SSMS? Have you tried uninstalling and reinstalling SQL Prompt?
Can you please check if you have "SSMS Integration Pack Framework 1" installed on the Programs and Features menu, that is what actually controls the visibility of the tools within SSMS.
Thanks. / comments
Hi Jacky,
What's the version number of your SSMS? Have you tried uninstalling and reinstalling SQL Prompt?
Can you please check if you have "SSMS Integration Pack Framework 1" installed on the Prog...
This error occurs when our Git library attempts to read the repository's metadata files but cannot finish for whatever reason -
The best way to resolve this is to either:
1- Create a new repository for the database files (so that the metadata files are clean)
2- Unlink and use the Custom option with the Git config file to link to your local repository. Note you will have to use your Git tool (GitBash, TortoiseGit, SourceTree etc.) to Push and Pull instead of SQL Source Control.
If it doesn't help, can you show us the errors in your log file? / comments
This error occurs when our Git library attempts to read the repository's metadata files but cannot finish for whatever reason -
The best way to resolve this is to either:
1- Create a new repository...
Hi @Shaun5Stu Sorry I should have been more clearer. You won't be prompted Access Token request until you try to Push or Pull from remote. For example: [image] After click Continue, you'll need to use Access token to complete the Push. [image] / comments
Hi @Shaun5Stu Sorry I should have been more clearer. You won't be prompted Access Token request until you try to Push or Pull from remote.For example:After click Continue, you'll need to use Access...
Hi @HWinkler
Can you please try:
1- create a Personal access token https://docs.microsoft.com/en-us/vsts/accounts/use-personal-access-tokens-to-authenticate
2- clone the repository to your PC (manual clone or via VS) [image]
2- Click the database, go to Set up in SQL Source Control --Link to my source control system -- Git, paste the path of the local repository that you've cloned. [image]
3- Click 'Link', and choose access token and put in your Personal access token.
SQL Source Control will remember the token so you don't need to re-enter it in the case of relinking.
I hope this helps. Please let me know if you need more information.
Thanks. / comments
Hi @HWinkler
Can you please try:
1- create a Personal access token https://docs.microsoft.com/en-us/vsts/accounts/use-personal-access-tokens-to-authenticate
2- clone the repository to your PC (manu...
Hi @Kamil ,
It seems to work fine for me. I've tested in version 13.0.5.5219 and 13.1.2.5327. We have created a ticket for you so that we can look into the issue for you in detail. / comments
Hi @Kamil ,
It seems to work fine for me. I've tested in version 13.0.5.5219 and 13.1.2.5327. We have created a ticket for you so that we can look into the issue for you in detail.
We've now removed version numbers from the product names in the drop down list when you want to submit a new post. / comments
We've now removed version numbers from the product names in the drop down list when you want to submit a new post.
Hi Mike,
Unfortunately SQL Prompt V6.2 doesn't support VS 2015. Please upgrade your SQL Prompt.
Thanks. / comments
Hi Mike,
Unfortunately SQL Prompt V6.2 doesn't support VS 2015. Please upgrade your SQL Prompt.
Thanks.
Hi Rick,
Thanks for posting!
I'm afraid it isn't possible to do this in SQL Prompt at the moment. Could I suggest you vote on uservoice. We use these requests to help prioritize upcoming work.
Kind regards, / comments
Hi Rick,
Thanks for posting!
I'm afraid it isn't possible to do this in SQL Prompt at the moment. Could I suggest you vote on uservoice. We use these requests to help prioritize upcoming work.
Kind...
Hi @seanhoward,
As we discussed in the email, if you have an error like:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) ---> System.ComponentModel.Win32Exception (0x80004005): The certificate chain was issued by an authority that is not trusted
before you connect to the SQL Server, please go to the Connection Properties and enable the "Trust Server Certificate" option. [image]
Thanks! / comments
Hi @seanhoward,
As we discussed in the email, if you have an error like:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: S...
Hi everyone,
I'm sharing @Sal 's finding for this issue. Can you please check your log file to see if you have similar error like this:
System.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted)
In this case, please make sure to enable the "Trust Server Certificate" under Connection Properties when you connect to SQL server?
I hope this helps! [image] / comments
Hi everyone,
I'm sharing @Sal 's finding for this issue. Can you please check your log file to see if you have similar error like this:
System.Data.SqlClient.SqlException (0x80131904): A connection...