RE: VS2008 Server Explorer takes 45 seconds to connect to SQL2005

Hi Charles,

Yes you understand my problem perfectly.
I will begin to action your list now and get back to you shortly.
(Thanks for looking into this for me)

""Charles Wang [MSFT]"" wrote:

Hi Paul,
I understand that when you tried to open a database connection from Visual
Studio 2008 Server Explorer on Vista SP1 to your SQL Server 2005 SP2
instance. You encountered the timeout error which was eliminated by setting
the timeout value to 120 second in Advanced settings. However if you did
not manually input the database name, you also could not see the database
listed in the dropdown list.
If I have misunderstood, please let me know.

I just performed a test at my side with Visual Studio 2008 installed on
Vista SP1 to connect a SQL Server 2005 SP2 instance on Windows Server 2003
(currently I have no Windows Server 2008 machine for test). I did not
encounter any timeout issue. If necessary, I will submit a request to our
lab to apply for a test environment with Windows Server 2008. However
before that, to decide if this is a server-side issue or a client-side
issue, I would like to collect the following information from you for
further analysis:

1. Check if this issue happened on only one computers or all of your
computers with VS2008 installed on Vista SP1; and what about other
computers with different OS?

2. Check if your network conditions are healthy. You can run "ping" command
to ping your server. Generally in a healthy LAN, the time value should be
less than 15ms.

3. Check if you still encounter connection lag issue when you run "sqlcmd
-S<servername>\<instancename> -E" from command line. You can test the
connection with different protocol by specifying a prefix such as tcp: or
np:. For example:
//Use TCP protocol to connect to your SQL Server instance
"sqlcmd -Stcp:<servername>\<instancename> -E"
//Use Named Pipe to connect to your SQL Server instance
"sqlcmd -Snp:<servername>\<instancename> -E"

4. Check if SQL Server Browser service is started on your server. You can
check it via running services.msc from command line. If it is not started,
please manually start it.

5. Mail me (changliw_at_microsoft_dot_com) your SQL Server Error logs which
are by default located in the folder %ProgramFiles%\Microsoft SQL
Server\MSSQL(.x)\MSSQL\LOG for further research.


Please feel free to let me know if you have any other questions or
concerns. Look forward to your response.


Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
============================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================


.

Relevant Pages

  • NFS locking
    ... We have a NFS server here with a fairly high load. ... lockd: server xxx.xxx.xxx.xxx not responding, ... # ACPI Support ... # CD-ROM/DVD Filesystems ...
    (Linux-Kernel)
  • RE: ADSI as linked server
    ... This is Mark, a SQL Server Engineer. ... Microsoft Online Community Support ... or a Microsoft Support Engineer within 1 business day is acceptable. ...
    (microsoft.public.sqlserver.connect)
  • NFS problems with through 2.5.x to 2.6.0-test9
    ... When the server is running the ... kernel, as a client the 2.6 series seem to work perfectly, excluding ... Interesting problem arose when I attempted switch the server's kernel to ... with and without nfsv4 support compiled in (was considering testing it at ...
    (Linux-Kernel)
  • RE: xp_cmdshell, Access Denied, Further Investigation Reveals
    ... context in which the SQL Server service is running. ... xp_cmdshell will impersonate the SQL Server ... Agent proxy account, ... Microsoft Online Partner Support ...
    (microsoft.public.sqlserver.security)
  • RE: Sharpoint Error in SBS 2003
    ... > Have you upgraded the Sharepoint WMSDE to SQL server? ... > A supported hotfix is now available from Microsoft, ... > To resolve this problem immediately, contact Microsoft Product Support ...
    (microsoft.public.windows.server.sbs)
Loading