Hi @galletto,
Is there any update on this case?

Hi galletto,

Open the file >> C:\Users\userName\AppData\Roaming\Microsoft\SQL Server Management Studio\18.0\UserSettings.xml
Search with the keyword Password, whether you can find entries related to the login name.

Make sure that SSMS is not started, then try to cut this 18.0 folder under C:\Users\userName\AppData\Roaming\Microsoft\SQL Server Management Studio to Desktop, then start SSMS, log in and remember the password. Note that after starting SSMS, an new18.0 folder will be created again. If there are any problems, move back the 18.0 folder that was previously removed.

I cannot reproduce your problem. Do you have other machines with SSMS 18.6 also having this problem? If possible, re-install SSMS.

Hi,

This improvement changes the way that concurrency is managed with PFS updates so that they can be updated under a shared latch, rather than an exclusive latch.

You may need to learn more about SQL Server latch.
If you need more detailed instructions, I haven't found some more helpful information for the time being.

Hi,

I'm not sure if the different versions of powershell caused this problem. This problem has not occurred in my environment.

Please try to repair SQL Server and SSMS.

What's new in 18.0
General SSMS Switched to "Windows Credential Manager" for connection dialog MRU passwords. This addresses a long outstanding issue where persistence of passwords wasn't always reliable.

The Windows Credentials are visible at: Control Panel\User Accounts \Credential Manager. Or search box on the taskbar and type "credential".
Check the SSMS credential records(Microsoft:SSMS:18:...)

Hi,

Will this problem disappear after turning off the "forced encryption" on the server side? It seems that this error occurred during the connection establishment phase, and "forced encryption" is just to ensure encryption during the data transmission phase.

The client that trying to connect is a Cluster Virtual interface.

This also makes me wonder whether it is from some connections between the cluster and SQL Server, such as checking the health status of the availability group.

I will also check SQL Server and the TLS/SSL protocols supported by the servers in cluster.

Hi,
I’m glad to hear that your problem has been resolved. Thank you for sharing.

Hi，

It looks like you have installed the latest SSMS 18.9.2 but still facing the same problem. Please try to use the Azure Data Studio to connect to SQL Server, which is automatically installed with SSMS 18.9.2.

Hi,

Welcome to Microsoft Q&A!
I can't find any useful information about SQL Server and query rewrite rules. Do you mean MySQL?

Hi,

You can specify the filegroup when creating the table.

If you need to move the existing tables to a different filegroup.
https://www.mssqltips.com/sqlservertip/5832/move-sql-server-tables-to-different-filegroups/

Hi @raki-3122,

But question is, if i can access the database using same odbc connection from visual studio on the server itself why not from IIS when residing there.

This problem seems to be related to IIS. I suggest you go to the IIS forum (dotnet-aspnet-iisnet) for proper help.
https://docs.microsoft.com/en-us/answers/topics/dotnet-aspnet-iisnet.html

Hi,

I also think that the high frequency of physical connection and close operations may cause LSASS to consume a lot of CPU.

I am not familiar with IIS application. Does the application use connection pooling?

Hi,
You are welcome. I'm sorry that I don't currently have a SQL Server 2016 environment, otherwise I can test and draw a definite conclusion.

Hi,

m

y assessment at this point is that if you install on any drive outside of C, you probably can't also have spaces in the 'working directory' path

I will take a test on this valuable assessment.

Oh, this time I created a new directory with spaces on the E drive on the original computer and installed a new SQL Server instance. Everything is the default configuration, but there is no problem with executing sp_execute_external_script.