June 16, 2006 at 8:08 pm
June 19, 2006 at 8:00 am
This was removed by the editor as SPAM
June 19, 2006 at 10:10 am
Have you tried to use perfmon on the NIC interfaces ? My guess is that if you used perfmon (locally) whilst you performed the network SQL trace and the local SQL trace you'd see why things are slowing down. A separate session on both interfaces, the public (where the network SQL trace data goes) and the private (crossover) where your local passove node trace is probably going.
If this is the case it's because the cluster was built with defaults networking, communication and binding (and they are not correct), who would have thought that MS defaults were wrong ?!?!?
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
June 20, 2006 at 12:23 am
it's not because your queries slow down, that your network slows it down !
For sqlserver it depends wich trace-flags are activated for the trace.
e.g. do you only capture sqltext or also have selected the execution plans, all locking acitivity, .....
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
June 20, 2006 at 11:39 am
There was something wrong with our network, I believe. When running trace, I noticed that overall connection to network where SQL Server located was slow. For example, even RPD sessions became significantly slower.
When running trace on second (passive) node, connectivity is Ok.
Igor
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply