Fluid_Imagery
asked on
SBS2011 running SQL Proprietary Database Slow
We have a server that's running SBS2011 (41GB Exchange Database) and a Propietary custom designed SQL database (~ 1.6GB)
The Server is a T610 Xeon X5670 2.93 with 24GB Memory
In Task Manager it's showing Exchange using around 14GB of memory and SQL using a little under 3. There are about 10 desks at the office accessing the database all day and occassionally complain about database running slow. I'm assuming it has something to do with the memory utilization.
Any recommendations outside of getting a 2nd server to host the SQL database?
The Server is a T610 Xeon X5670 2.93 with 24GB Memory
In Task Manager it's showing Exchange using around 14GB of memory and SQL using a little under 3. There are about 10 desks at the office accessing the database all day and occassionally complain about database running slow. I'm assuming it has something to do with the memory utilization.
Any recommendations outside of getting a 2nd server to host the SQL database?
I'm thinking it may be a disk io issue. Check resource monitor to check for a raising disk queue. Can you put your db on a different internal drive?
Very well could be; hard to tell with so little info up front.
Also look at tempdb set up. Make sure you have more than one data file, and/or that all data files on tempdb are exactly the same size.
As an aside, limit SQL to using only 10G or so, since Exchange is using so much memory ... that is *not* your problem now, but it could easily become a big one in the future if you don't do that.
Also look at tempdb set up. Make sure you have more than one data file, and/or that all data files on tempdb are exactly the same size.
As an aside, limit SQL to using only 10G or so, since Exchange is using so much memory ... that is *not* your problem now, but it could easily become a big one in the future if you don't do that.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
didn't get a answer,