|
[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 jflanner in MS SQL Server
Hi Folks:
I have an ETL process that inserts a good number rows into a table periodically. (Hundreds of rows into a partitioned 30 million of row table.) The table is available to an update function in the online application. By business rules - it is impossible for an online user to want to update a record that is being inserted. (They must select an existing record to online update.) Also - the ETL process is insert only. It is stored procedure based, inserting from a local load table that has been scrubbed. Primary key scrubbing is done successfully offline. The ETL process is 100% responsible for 100% of the inserts. Rows are not manufactured elsewhere.
So - the processes are isolated by business rules. The users can only update rows that exist, and the ETL process only inserts rows that do not exist.
My probelm is - I observe the ETL process blocking online users to the point of time out generation. (Not good to be me when that happens regularly.) I have control over the ETL process, but I have limited influence over the online app. I have tried changing the ETL process first to paglock and now to rowlock - but it still blocks.
Anyone have any ideas how I can get around this?
20091111-EE-VQP-89 - Hierarchy / EE_QW_3_20080625