|
|
|
date: Tue, 22 Apr 2008 13:03:01 -0700,
group: microsoft.public.sqlserver.connect
back
RE: VS2008 Server Explorer takes 45 seconds to connect to SQL2005 Data
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@microsoft.com.
===========================================================
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.
=========================================================
date: Wed, 23 Apr 2008 03:59:29 GMT
author: (Charles Wang [MSFT])
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@microsoft.com.
> ===========================================================
> 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.
> =========================================================
>
>
date: Wed, 23 Apr 2008 03:44:01 -0700
author: Paul Hale am
RE: VS2008 Server Explorer takes 45 seconds to connect to SQL2005
QUESTION
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?
RESPONSE
PC 1 â DELL Precision 670 64Bit - Vista Ultimate SP1 + VS2008
PC 2 â Dell Inspiron 9400 Laptop X86 - Vista Ultimate SP1 + VS2008
PC 3 â Dell Dimension 3000 X86 running XP Pro (note no sp2) + VS2008
Problem: On all machines if I try and connect to SQL2005 SP2 running on a
Windows 2008 Server via VS2008 server explorer they experience a timeout. If
I set the Timeout to 120 (as opposed to default 15) AND manually enter the
database I want to connect to in the âSelect or enter a database nameâ
dropdown box I can connect after a 45 second wait. Note that even after I set
the timeout to 120 the âSelect or enter a database nameâ does not auto
populate with available databases.
QUESTION
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.
RESPONSE
Ping test.
PC 1: bytes-32 time<1ms TTL128 (Using IP address)
PC 1: bytes-32 time<1ms TTL128 (Using Server Name)
(0% loss)
PC 2: As above.
PC 3: As above.
QUESTION
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"
RESPONSE
Ran both examples. Login timeout errors received...
âSqlcmd: Error: Microsoft SQL Native Client : Login timeout expiredâ
QUESTION
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.
RESPONSE
SQL Server Browser is running (sorry forgot to mention this on original post)
QUESTION
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.
RESPONSE
Emailed to you as requested.
If you need anything else from me please dont hesitate to ask.
Paul.
"Paul Hale" wrote:
> 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@microsoft.com.
> > ===========================================================
> > 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.
> > =========================================================
> >
> >
date: Wed, 23 Apr 2008 05:48:04 -0700
author: Paul Hale am
RE: VS2008 Server Explorer takes 45 seconds to connect to SQL2005
Hi Paul,
Thank you for your detailed response.
I have checked the error log and did not show any error information
regarding your SQL Server instance startup. Also I established a test
environment with Windows Server 2008 and performed a test at my side,
however I could not reproduce your issue. Every connection to my SQL Server
instance was quickly succeeded, so I think that your issue should be caused
by some misconfigurations on your server.
I recommend that you check the following conditions and let me know the
results:
1. Firewall exceptions
Run firewall.cpl from command line, check if your SQL Server process
(%ProgramFiles%\Microsoft SQL Server\MSSQL.(x)\MSSQL\Binn\sqlservr.exe) is
added into the Exception list; if not, please add the two processes to the
exception list.
2. SQL Server Services service account
Run services.msc from command line, right click SQL Server Services,
click Properties, switch to the Log On tab, check if the service account is
a domain user account; if not, please manually specify a domain user
account and restart your SQL Server to see if it helps.
3. Local connection
Run "sqlcmd -S<servername>\<instancename> -E" from command line locally
to see if you can quickly connect to your SQL Server instance.
Please feel free to let me know if you have any other questions or
concerns. Have a nice day!
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@microsoft.com.
=========================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
date: Thu, 24 Apr 2008 08:13:08 GMT
author: (Charles Wang [MSFT])
RE: VS2008 Server Explorer takes 45 seconds to connect to SQL2005
Charles,
Thank you sir!
The problem was I had not added Sqlserv.exe as a Firewall exception.
I can now see all available databases in the "Select or enter a database
name" drop down and the time it takes to connect to a database is pretty
mutch instant.
This also solved a multitude of problems I have been having when coding
using various databound controls.
Thank you very much for your time on this. You have made my week!
Paul.
""Charles Wang [MSFT]"" wrote:
> Hi Paul,
> Thank you for your detailed response.
>
> I have checked the error log and did not show any error information
> regarding your SQL Server instance startup. Also I established a test
> environment with Windows Server 2008 and performed a test at my side,
> however I could not reproduce your issue. Every connection to my SQL Server
> instance was quickly succeeded, so I think that your issue should be caused
> by some misconfigurations on your server.
>
> I recommend that you check the following conditions and let me know the
> results:
> 1. Firewall exceptions
> Run firewall.cpl from command line, check if your SQL Server process
> (%ProgramFiles%\Microsoft SQL Server\MSSQL.(x)\MSSQL\Binn\sqlservr.exe) is
> added into the Exception list; if not, please add the two processes to the
> exception list.
>
> 2. SQL Server Services service account
> Run services.msc from command line, right click SQL Server Services,
> click Properties, switch to the Log On tab, check if the service account is
> a domain user account; if not, please manually specify a domain user
> account and restart your SQL Server to see if it helps.
>
> 3. Local connection
> Run "sqlcmd -S<servername>\<instancename> -E" from command line locally
> to see if you can quickly connect to your SQL Server instance.
>
> Please feel free to let me know if you have any other questions or
> concerns. Have a nice day!
>
> 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@microsoft.com.
> =========================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
> =========================================================
>
>
>
>
>
>
>
>
date: Thu, 24 Apr 2008 05:49:01 -0700
author: Paul Hale am
|
|
