SQL Server Express 2014 Extremely Slow on Network
-
Tiny network, Windows 10 on two machines. SQL Server Express 2014 on one machine. If I connect from SSMS on the "client" machine to the "server" machine, I get a connection, but opening a table is ridiculously slow. To the point that apps seem to be timing out. Not sure where to dig in, something is causing it to be dog slow. Can't be disk, RAM or CPU because it's fine locally. Something about network or authentication seems to be the culprit.
-
Try a cross over cable to remove the switch.
-
or swap patch cables if you can.
-
This post is deleted! -
Is the issue from one specific "client" machine, or multiple?
-
@scottalanmiller said in SQL Server Express 2014 Extremely Slow on Network:
s 10 on two machines. SQL Server Express 2014 on one machine. If I connect from SSMS on the "client" machine to the "server" machine, I get a connection, but opening a table is ridiculously slow. To the point that apps seem to be timing out. Not sure where to dig in, something is causing it to be dog slow. Can't be disk, RAM or CPU because it's fine locally. Something about network or authentication seems to be the culprit.
Any more details? What is the connectivity between the devices? What about Antivirus?
-
@Jimmy9008 said in SQL Server Express 2014 Extremely Slow on Network:
Is the issue from one specific "client" machine, or multiple?
There only is a single machine, so very hard to tell.
-
@dbeato said in SQL Server Express 2014 Extremely Slow on Network:
@scottalanmiller said in SQL Server Express 2014 Extremely Slow on Network:
s 10 on two machines. SQL Server Express 2014 on one machine. If I connect from SSMS on the "client" machine to the "server" machine, I get a connection, but opening a table is ridiculously slow. To the point that apps seem to be timing out. Not sure where to dig in, something is causing it to be dog slow. Can't be disk, RAM or CPU because it's fine locally. Something about network or authentication seems to be the culprit.
Any more details? What is the connectivity between the devices? What about Antivirus?
Windows Defender. Just connected to the same switch, tiny environment.
-
@scottalanmiller said in SQL Server Express 2014 Extremely Slow on Network:
Tiny network, Windows 10 on two machines. SQL Server Express 2014 on one machine. If I connect from SSMS on the "client" machine to the "server" machine, I get a connection, but opening a table is ridiculously slow. To the point that apps seem to be timing out. Not sure where to dig in, something is causing it to be dog slow. Can't be disk, RAM or CPU because it's fine locally. Something about network or authentication seems to be the culprit.
I've run into strange problems when default gateway or network mask isn't right.
Or if a program is doing a hostname lookup but the DNS on the network isn't running.You could probably run wireshark and find it pretty quickly.
I doubt that it's a "physical" problem.
-
@scottalanmiller said in SQL Server Express 2014 Extremely Slow on Network:
Tiny network, Windows 10 on two machines. SQL Server Express 2014 on one machine. If I connect from SSMS on the "client" machine to the "server" machine, I get a connection, but opening a table is ridiculously slow. To the point that apps seem to be timing out. Not sure where to dig in, something is causing it to be dog slow. Can't be disk, RAM or CPU because it's fine locally. Something about network or authentication seems to be the culprit.
Not an answer but a vaguely described possible point in direction...
On ML, someone here posted (Sometime in the last year I believe) about having to allow a process through the Windows Firewall for SQL and that sped everything up. I believe it was "Transaction Coordinator" or something like that.
-
@pmoncho said in SQL Server Express 2014 Extremely Slow on Network:
Not an answer but a vaguely described possible point in direction...
On ML, someone here posted (Sometime in the last year I believe) about having to allow a process through the Windows Firewall for SQL and that sped everything up. I believe it was "Transaction Coordinator" or something like that.netsh advfirewall firewall set rule name="Distributed Transaction Coordinator (TCP-Out)" new enable=yes profile="domain" -
Did you ever solve this problem? Just wondering what you solution was if you did.
