January 5, 2015 at 2:17 pm
We have an application that uses sql server and we had some people complaining about performance.
We found that the same reports are running fine for some people but having serious performance issues for others
I have created a setup with a server and a few workstations to test this and eliminated as many variables as possible
Now I am down to a sql server database on a server and have multiple workstations connected. interestingly a surface pro tablet is one that doesn't experience the problem
I was able to track it all the way down to simply using the ODBC datasource admin. When testing the data source attempting the connection to the server takes about 1.5 seconds on the workstations that have the performance issue were the oones that don't connect without any delay.
looks like they are all using native client 11
Looking for any help to try and track down what is causing this issue
any help would be greatly appreciated
thanks
Mike
January 5, 2015 at 3:59 pm
Local firewall software on the client taking a while to "allow" the connection? (try disabling any firewalls for a test)
Nameserver lookups taking a while? (still slow with ip address and port specified?)
Pings ok from these clients?
SQL authentication or Domain? same problem for both?
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);
January 5, 2015 at 4:12 pm
Check maximum number of concurrent connections?
January 5, 2015 at 4:35 pm
I would also check that these are on the same network segment. Maybe the router in front of these boxes is overloaded, or has something else slowing down the conn.
It could be as simple as the client has only a 100Mb conn while the others have 1Gb. There are a lot of factors here and you just have to start eliminating things. But don't overlook physical issues.
Watch my free SQL Server Tutorials at:
http://MidnightDBA.com
Blog Author of:
DBA Rant – http://www.MidnightDBA.com/DBARant
January 5, 2015 at 5:10 pm
have disabled all firewalls, anti virus and anything else I could think of.
I may have found an issue. have to do some more testing but it seems to possibly have to do with reverse DNS issues. At least in one instance I was able to fix the problem by adding the sql server to the hosts file on the machine and the problem went away immediately
January 5, 2015 at 6:08 pm
Another thing to check are the ANSI settings for the connections. Maybe one set of machines is different than the others. That can lead to differences in execution plans and therefore differences in performance.
See if there is more than one execution plan for the same query within the plan cache on the server.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply