|
[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 JimR123b in MS SQL Server, SQL Query Syntax
We have a table with over 20 million rows in it, with each row having a datetime field (let's call it "TimeStamp"), containing the date and time when the row was created.
As the table is quite large, it makes doing queries on it very slow.
We would like to implement a system that archives off old data (e.g. where the row's timestamp is older than 3 months) to another identically structured table. We would also like to delete data from the archive table for over a certain age (e.g. delete rows that are more than 2 years old).
Considering that the table has many rows, what's the most efficient way of implementing this?
Is there a way of "moving" data from one table to another? i.e. Performing the archiving process in one step (a "move"), rather than two steps ("insert into archive table from select", then "delete" from original table).
20091111-EE-VQP-89 - Hierarchy / EE_QW_3_20080625
