It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,878
×6,036
×5,940
×4,318
×73
×7

question asked: Mar 17 '17, 10:58 a.m.
question was seen: 2,313 times
last updated: Mar 20 '17, 12:45 p.m.

Related questions

LQE Re-Indexing taking lots of time

0
Pankaj Sharma (40●11●70) | asked Mar 17 '17, 10:58 a.m.
edited Mar 20 '17, 12:45 p.m. by Paul Slauenwhite (8.4k●1●2)

My Team is migrating the data from one server to another servers, they are using Server Rename Process to migrate, But this process also requires LQE re-indexing which takes generally 18-20 days (because of huge data) to complete and if any error occurs they have to restart indexing.


And they have to do this for at-least 4-5 times before everything is set (I assume) for Production server.
So I  need to understand:
  1. What is the affect if LQE indexing is not done immediately
    • What loss that we will have to suffer, can that be recovered later?
  2. Can users work on Application if LQE indexing is running
    • What loss that we will have to suffer, can that be recovered later?
    • If yes How can we manage user traffic / performance for the application?

Be the first one to answer this question!

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.