vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hey Folks, Experiencing strange problem with SQL 2005 running on Windows Server 2008. When trying to connect via named pipes or tcp, it takes 25-45 seconds for the connection to be established. Looked at some posts about IPv6 possibly causing the problem when in stacked ipv4/ipv6 environment, but not seeing any results after un-binding ipv6 protocol. After running some tests, interaction with the DB Server is slow even after connection. Queries against the same databases take longer on this server versus an existing server. Any ideas out there? Thanks... |
| ||||
| GatorDBA (gatorgrad01@gmail.com) writes: > Experiencing strange problem with SQL 2005 running on Windows Server > 2008. When trying to connect via named pipes or tcp, it takes 25-45 > seconds for the connection to be established. Looked at some posts > about IPv6 possibly causing the problem when in stacked ipv4/ipv6 > environment, but not seeing any results after un-binding ipv6 > protocol. Do you connect with Windows authentication or SQL Server authentication? If the former, could you try the latter and see if it makes any difference? > After running some tests, interaction with the DB Server is slow even > after connection. Queries against the same databases take longer on > this server versus an existing server. > > Any ideas out there? Does this happen also when you run queries locally and you are connected through shared memory? -- Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/pro...ads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinf...ons/books.mspx |
| Thread Tools | |
| Display Modes | |
|
|