Duration too long

[timscronin]

Hearing complaints from users about speed on db server (I have almost no control on design) it just has to work. Ran profiler looking for all sql statements over 4000 millsec and in one hour returned over 715 tsql statements. Over 300 of these were over 10000 milliseconds. THis is on an 8 way Dell with 8 gig of RAM. Looking for opinions, how bad does this look compared to other servers you are taking care of?

 

[JayKusch]

That is really a question that cannot be fully answered.

I could "probably" take your current system and with properly applied indexes, stored procedure tune ups and some basic MDF and LDF allocations on seperate disc, increase the performance quite a bit.

Then again, we could take your current configuration and I could really bring it to its knees by writing some bad stored procedures, run other applications on the server like IIS, Exchange Server and some monitoring tools.

So in saying this, it really depends on what apps your server is running, hopefully just SQL Server, how well designed your database schema(s) are. How much cross-database transactions are occuring, how well the stored procedures are written and if the databases have the appropriate indexes are just a few of the items that need to be concidered.

Thanks

J. Kusch

 

[timscronin]

Restating my first statement, I have no control over design, that's part of the issue. This is only one db. LDF on RAID 10, mdf on a SAN. ALmost no sp's at all, TSQL in their code pulls the statements and specifies indexes. (not changeable) More interested if someone considers these durations poor.

 

[JayKusch]

Depends on what the stored procedure is doing.

Thanks

J. Kusch