November 2, 2006 at 10:28 am
I work in a corporate environment and we have jsut recently moved our SQL Server from our onsite location to a corporate location. Since our move we have been experiencing timeout issues while running scripts on a web server. Moving the SQL Server to corporate actually moved the servers physically closer together.
It was suggested by a corporate network person that the port that SQL Server is listening on is not given as high a priority as some of the other ports and that we should change the port that SQL listens on.
Does this sound reasonble and if so is there anything else changing this port can effect.
And if anyone has any othe ideas they would be greatly appreciated.
Thanks in advance
November 2, 2006 at 2:51 pm
It is possible. Probably, the network person set it. One way to set it is:
Open the Task Manager;
Click the Process tab;
Right-click an executable file, then choose Set Priority;
...
November 3, 2006 at 10:09 am
I dunno ... the servers are now closer together. Is your SQL Server's NIC card set to 100 MB/Full Duplex ? Is the switch port that your SQL Server is plugged into set at 100 Mb/Full Duplex ? (With CISCO network equipment and Intel NIC cards there are issues associated with 'auto'). Are they on the same physical network seghment ? Are you using VLANs ? If so, are they on the same VLAN ? Are they using custom routing tables internally on the network ? Have they monitored the switch port that the SQL Server is using for errors and dropped packets ?
I would not change anything on the SQL Server until you can get the above questions answered. If your network guy cannot then go to the next person up the chain.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply