Geek Answers Handbook

Error connecting to a remote SQL Server database Visual Studio 2017

I have an instance of SQL Server 2016 running on a Windows 2016 server. I'm trying to connect to a database from a remote PC in the Visual Studio 2017 community using Server Explorer. The connection was successful, and I can see the databases available on the server and logging in is just fine, but when I try to expand the tables folder, I get this error:

Failed to get data for this request.
Failed to connect to server (local)
User xxxxx login failed

The thing is, I can connect in exactly the same way using Visual Studio 2015 Enterprise, so I can see the tables and modify them.

I made sure that the user had all the permissions granted on the server, and for me this does not seem to be a permission issue, since the connection works fine in VS 2015.

+8
sql-server visual-studio
source share
5 answers

This will help. Make sure you select the "Save my password" checkbox when adding a new database connection to view the image .

+25
source share

For those who performed the first migration of the code and received this problem, simply right-click on the connection name in the server explorer and select "Change this connection ...", then click the "Save Password" button. Click OK and confirm again that everything is working again.

+4
source share

Did you try to save the solution / project and try again? I struggled with this on the new VS 2017 Community installation and what just worked for me. The .rds file was not updated until I saved everything. After that, I can again use the "add table" button.

0
source share

I have the same problem. When trying to expand the table folder, registration failed. all other folders really work, "Views", "Stored Procedures", but not "Tables".

0
source share

The problem is that Visual Studio 2017 makes more calls to load tables (to collect row counts) until 2015. This can be seen in SQL Profiler. The problem is worse with SQL Server 2016 due to analytics of "optimized memory".

The default timeout for the designer is 30 seconds. Assuming an SLA of up to 20 ms before AWS or Azure, an object scheme of size 6,000 will ALWAYS fail in 2017 by default.

Unfortunately, increasing the timeout will not speed up the work.

0
source share

More articles:


All Articles