|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by ONYX in MS SQL Server, SQL Server 2005
I have a strange anomaly happening with a SQL Based application that we have. Every once in a while, the DB goes into a state where it's almost as if it's been put in "single user mode". In any case, the DB is inaccessible. So, to get it back, I have to right click on it, take it offline, then put it back online and everything is okay after that.
Having said all of that, since this occurs at randoom times, I want to run either Profiler or Auditing to see if I can capture what is causing this behavior. I want to know what kind of effect this will have on performance turning on Profiler or turning on Auditing. Which one will be less invasive or have less of an effect on Performance.
Incidentally this is SQL Server 2005 SP2 on a Windows 2003 Server
Thank you.
20091111-EE-VQP-92 - Hierarchy / EE_QW_3_20080625