July 2, 2010 at 8:08 am
Good morning people.
We recently acquired a new server and migrate the bank SLQ server for it.
He was bemmais fast for queries, but when we record some information (user save any information, or any given) it freezes, it becomes very slow. I checked the memory and processing and are stable (using proce is 1-4% and memory is 4gb of 2.8), but I noticed that the hd is working a lot(overworked). What may be happening?
the version of sql is 2005 sp2
45 users
Thanks!
July 2, 2010 at 8:23 am
That is a rather broad question so here are some follow up questions. Is there anything besides SQL running on the server? How do users interface with SQL? What makes you beleive the HD is Overworked? What is triggered when the users update (are stored procedures running, are temp tables used)? How many records are being updated at a time? What else is sql doing when and update takes place? Are there iny locks or blocks that are occuring?
Dan
If only I could snap my figures and have all the correct indexes apear and the buffer clean and.... Start day dream here.
July 2, 2010 at 9:08 am
Dan
Thanks for the feedback.
There is an instance in sql itself, but disabled it, and there is a person who makes access via terminal. What makes me believe that the HD works hard, the LED of Hd dont stops blinking when accessing the system and save information on it.
The other questions I am waiting for a person who works with me, answer me
July 2, 2010 at 9:14 am
There is an instance in sql itself, but disabled it,
you disabled the instance of SQL? then how does SQL respond to anything?
Dan
If only I could snap my figures and have all the correct indexes apear and the buffer clean and.... Start day dream here.
July 2, 2010 at 12:16 pm
Sorry I expressed it badly. is not instance, we have a backup software that runs sql server, but I stopped him.
- User interfaces accessing SQL Server through ODBC
- There are several triggers implemented (I will not list them because they are many). The triggers are implemented without using Stored Procedures
- I have a large number of records updated. There are about 45 users using the system actively, but consultations are saving little information.
The strange thing is that the old server that have a setting below the new, the system was running much better.
July 2, 2010 at 1:19 pm
now that we have some more information take a look at an article written by Gail shaw on information needed to be able to help with performace problems.
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
I would also look at some of the DMV's and performace information available in SQL 2008.
microsoft has a performace dashboard you can install that will allow you to capture information.
Also look at profiler to get some clues as to what may be going on.
There are a lot of possible scenarios that could be going on. If it is a SQL problem it could be a missing query or a setup issue but most likely it is a porrly written query on the application side. It is also possible that indexes need to be rebuilt. Do you currently have regular maitenance jobs?
While I would not quarentee that there is not a hardware issue I would not say a large number of writes indicated by the light is really an indication of a problem.
Dan
If only I could snap my figures and have all the correct indexes apear and the buffer clean and.... Start day dream here.
July 6, 2010 at 7:10 am
Thanks for the help.
The problem was the size allocated for the database that was the limit. It was not until we increase the size of the database and it solved the problem
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply