March 31, 2012 at 12:27 am
Sir/s,
I'm using SQL 2005 and our Database size is 6.18 GB now and currently I'm facing problem of Timeout expired. Any quick tool which can release me from this error instantly. I'm also looking for Data tuning but not succeed. please help. we have 60 users connected to application and when this Timeout occurs, whole work stucks. I tried Shrinking and it works for 1-2 days and again the same problem occurs.
Please Help
Mukund
March 31, 2012 at 2:36 am
Quick tool for you is to hire a professional who can help you identify performance problems and provide a solution.
March 31, 2012 at 1:43 pm
Alexander Suprun (3/31/2012)
Quick tool for you is to hire a professional who can help you identify performance problems and provide a solution.
There is no quick fix outside of hiring a professional to assess the problem and work through some resolutions.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 31, 2012 at 2:52 pm
Shrinking is liable to make the problem worse, not better, as it severely fragments indexes.
There's no quick fix, no magic switch or setting. Performance tuning is the process of finding the worst problems and fixing them, repeat until performance is acceptable.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 31, 2012 at 3:58 pm
mukund.bklwh (3/31/2012)
Sir/s,I'm using SQL 2005 and our Database size is 6.18 GB now and currently I'm facing problem of Timeout expired. Any quick tool which can release me from this error instantly. I'm also looking for Data tuning but not succeed. please help. we have 60 users connected to application and when this Timeout occurs, whole work stucks. I tried Shrinking and it works for 1-2 days and again the same problem occurs.
Please Help
Mukund
Are you doing any nightly maintenance to the database? Which recovery model is your database using?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2012 at 1:35 pm
this info is 2 handy
April 9, 2012 at 1:41 pm
Definately look at the articles Gail references above in her post. You have a small database and not a whole lot of users.
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply