Submitted Questions

  • Indexing on frequently updated table

    I was asked a question in an interview, where I was given a situation which is: I have registered to an online gaming website. It displays my rank on the basis of my score when I play a game. Database table has 2 columns: 1. UserName 2. Score. Since the login page was loading very slowly so the programmers created an non-clustered index on UserName and now the welcome page problem is solved. But since...

    Yaman

    • Aug 10th, 2015

    First of all table is not well designed. Table should have a clustered index. Right now its a heap and if we create a clustered index on username its a bad idea as data gets physically sorted everytim...

    nabin

    • Mar 25th, 2015

    create clustered index on name. Reason is clustered index should be applied on columns which do not change frequently. Since the user will register once and will not change name that frequently it is ...