November 24, 2011 at 8:19 pm
Hi all,
Environment is like
OS :Windows 2000 SP4 Enterprise edition
memory : 8GB
SQL Server : MSSQL2000 SP1 Enterprise edition
Data & Log files are on same drive
In this environment I have checked logs, there are no long running jobs/queries. This environment is having performance issue.
My solution for P.T
-> Service Pack SP4 apply to SQL Server
-> Change of Data & log file location
-> Index rebuilding
I am getting 4 hours of downtime as Db size is 26 GB
can you suggest me exact steps. And step by step index rebuilding process. as this is production db.
Sagar Sonawane
** Every DBA has his day!!:cool:
November 24, 2011 at 9:15 pm
please someone guide me...
Sagar Sonawane
** Every DBA has his day!!:cool:
November 24, 2011 at 9:51 pm
Saga... (11/24/2011)
Hi all,Environment is like
OS :Windows 2000 SP4 Enterprise edition
memory : 8GB
SQL Server : MSSQL2000 SP1 Enterprise edition
Data & Log files are on same drive
In this environment I have checked logs, there are no long running jobs/queries. This environment is having performance issue.
My solution for P.T
-> Service Pack SP4 apply to SQL Server
-> Change of Data & log file location
-> Index rebuilding
I am getting 4 hours of downtime as Db size is 26 GB
can you suggest me exact steps. And step by step index rebuilding process. as this is production db.
You have not provided any information about your performance problem, or why you believe that the steps above will resolve it.
Unless you can point to a specific bug that is fixed in 2000 SP4, then installing it won't solve your problem.
Changing Data and Log file location so they are on different drives could very well help, but if the CPU is the limiting factor, then it won't solve your problem.
Index maintenance should be part of an ongoing strategy, not something you do one time.
So, here are my questions:
1. what are the symptoms of the performance problem (slow queries? user complaints? data loads taking too long? specific reports or stored procedures?)
2. How have you measured the performance and what numbers are you seeing? (cpu load, avg disk queue length, buffer cache hit ratio, profiler trace, etc?)
3. please describe the new drives, and how you imagine the data files being spread amongst them.
4. what is the recovery mode of the database? You mentioned that the db is 26 GB, how big the data, and how big is the log?
November 24, 2011 at 11:58 pm
Saga... (11/24/2011)
can you suggest me exact steps. And step by step index rebuilding process. as this is production db.
Sagar,
My suggestion to you is... if you are not sure about something, don't play with the production servers.
Firstly do it in the dev/test server. If you are satisfied with the result and confident, then only deply it to production.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply