March 12, 2010 at 5:24 pm
How can a midsized company such as ours go about eliminating timeout caused by users. Is it possible? Anything causes timeouts from jobs running simultaneously as server requests to locking e.t.c. Any input would be nice. The company is growing and we are currently looking at ideas and strategies to go about this.
I wanted to rub minds with the professionals on here before I proceed. Thanks
March 12, 2010 at 9:28 pm
sqlislife (3/12/2010)
How can a midsized company such as ours go about eliminating timeout caused by users. Is it possible? Anything causes timeouts from jobs running simultaneously as server requests to locking e.t.c. Any input would be nice. The company is growing and we are currently looking at ideas and strategies to go about this.I wanted to rub minds with the professionals on here before I proceed. Thanks
There's only one way to do this... fix the bad code and the bad indexes. And, make no doubt about it, it's because of bad code and bad indexes. For users using ad hoc queries, build a reporting server that they can use. The best fix would be to hire a really good DBA and then give him/her the authority (s)he'll need to fix things for you.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2010 at 6:54 am
Just to pile on a bit, I'm with Jeff. It sounds like your architecture, your structures, and your code are to blame. You need to get someone in who can identify the causes of the problems and offer viable solutions and then implement those solutions.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 15, 2010 at 12:42 pm
Thank you very much for your responses. They have been taken into consideration.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply