May 9, 2005 at 7:26 am
Hi
Please help me.
I have application and database server at one location and i am i have utilization bare going to 100% with only 255 users connect at given point of time. we have goan through each and every sp's and reinvented the entire application. We have put new hardware with dual process on dell with 2 GB of rams. i still have this issue existing since last 3 months. Because of this issue i am forced to become DBA in sql server. And that the main reason why i am on this site trying to work out this issue.
Any have any ideas regarding this please feel free to write to me.
Regards
May 9, 2005 at 7:36 am
What's the avg run time of the queries?
What are the most ran queries?
How many queries/minute do you run?
Do you have auto-clause or auto-shrink set to on on any production database???
May 10, 2005 at 3:37 am
Application server.... ".Net"?...advice seen elsewhere is "not to run SQL server and IIS on the same server".
Presume you have "Profiled" the SQL code + DB to ensure you have optimal structures/code....or used PerfMon?
Have you done any investigation on Network latency issues?
The information given is tempting but too brief. You really need to provide more detail....metrics on performance on the lines of those suggested by Remi.
Purchasing the services/experience of an expert may be cost-effective.
May 10, 2005 at 7:38 am
Only 255 users? This is a pretty serious application. You can't expect this to work with a PC mentality or a PC budget. Did you know that this kind of application used to take a mainframe with a legion of personnel? Sounds like you are in WAY over your head. What does "forced to be a DBA" mean? If you have a database with 255 users the very minimum you need is a full-time experienced DBA. As awesome as SQLServerCentral is, you're not going to even scratch the surface of a solution from a forum post. You definitely need to hire an experienced consultant just to start.
Mike
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply