We currently have a new SQL server running on 2008 Enterprise. After a few days drive mapping takes an age as does accessing shares via both the hostname and IP, a reboot fixes the issue. It only effects this one server.
Ping is fine as is traceroot.
IPv6 is disabled and the server is well within spec.
There are no errors in the logs
Has anyone got any idea what this could be?
□ΞVΞ□
It's a DNS problem.
Oh, so you think it's definitely not a DNS issue, because DNS is working great? Ah, ok.
It's a DNS problem.
if its a DNS issues why dos it do the same when the IP is used?
□ΞVΞ□
My first thought is how do you have memory utilisation configured in SQL, from memory on one of the tabs on the properties of the server (in SQL Management Console), you get a memory tab with a slider, by default SQL is coonfigured to use all available memory if needed, and I've sometimes seen it over time grab too much 'just in case'. What can happen over time is SQL memory utilisation goes up so high that parts of the OS get paged out to the page file (the so-called paged pool). Try setting the maximum memory utilisation in SQL to phyiscal RAM -512MB to give the OS some reserved space and see if that makes any difference.
You can monitor both memory utilisation of SQL and utilisation of the paged pool in perfmon.
Peter Sellers, 1977, The Muppet Show...There is no me. I do not exist. There used to be a me but I had it surgically removed.
Jay (30-09-2009)
I have restricted SQL to "only" use 14GB of RAM, lets see how that goes.
Thanks for that, simple things like that are so easily overlooked!
□ΞVΞ□
After many hours of my time this seems to be an issue with SMB2
□ΞVΞ□
There are currently 1 users browsing this thread. (0 members and 1 guests)
SCAN.care@HEXUS
SCAN.care@HEXUS
SCAN.care@HEXUS
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote