March 25, 2011 at 6:25 am
Dear Sir,
I am working in Sql Server 2005 Enterprises Edition And I am dealing billion of data at present my database size 100 GB. and I have mainteining all index & statistic. I have 2 maintainances plan 1. is working rebuild redexing and 2. is working update statistic. two maintenance plan working every other day. 1. maintenance plan running monday,wednesday and fry day and 2. maintenance plan working tuesday,thursday, saturday. but both maintenance plan running at day end.
still my every process running slow. and database server configuration is red controller, 1000 GB HDD, 8GB RAM, 2.3 Dual Cord Processor.
So there is no way to improve performance. Any Idea please help
Thanking You
Debasis Bag
March 25, 2011 at 7:16 am
You can also add up in the maint plan-- checking database integrity to ensure, everything's fine with your db's.
Also, rebuilding indexes every other day, i think its too long a process to do so frequently.
How mcuh time does it take to perform the 2 jobs?
Regards,
Sushant
Regards
Sushant Kumar
MCTS,MCP
March 25, 2011 at 11:58 am
deba_20032004 (3/25/2011)
So there is no way to improve performance.
Unless I'm misreading your comment, it sounds like you've already made up your mind that we can't help you.
Take a deep breath. Let it out slowly. And try again.
Is it only the maintenance plans that are having performance issues, or is it the whole server?
What are you basing "slow performance" on? Is it just a "I made these plans and they don't seem to be working as fast as I expected" response, or did these plans used to be faster?
Have you run Performance Monitor (for the OS / Hardware stats) and a SQL Server trace (or Profiler) to discover what part of the process is causing this slowness?
March 25, 2011 at 12:11 pm
Rebuilding indexes and stats does not solve all performance problems, only some parts of performance.
I think you need to start at the beginning and figure out your current bottleneck. Look around here and in the blogs for improving performance. Basically, you want to check CPU, memory, network and disk activity to see which of those are at capacity. This means spending time in perfmon.exe or using a third party tool.
Also, the issue may be too few (or too many, or incorrect) indexes. Even if they are rebuilt, if they are not used or not defined properly, then SQL server works harder. Look around here for help using Profiler to trace the SQL statements and see which have a high duration (those are running the longest), or which have the highest CPU, disk reads/writes to locate the problem queries. Then, it is another topic to to tune the query/indexes.
There is a lot to learn and you may need help from a professional rather then figuring this all out on your own - unless you have lots of time.
Jim
Jim Murphy
http://www.sqlwatchmen.com
@SQLMurph
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply