Quote Originally Posted by Pradeep1210 View Post
Won't it be a bad idea to consider multi-column index where single column index is required?


some columns are used with other columns in more scenarios but then those other columns are also used in other parts of the app which made the composite index a bad idea. Looking at it now, It's probably better to just leave it with 1 index per field. The indexed fields are necessary as the database grows but then there's the problem with the database size. I do like to keep things simple and I don't think there are ways to avoid the database size problem apart from taking the app back to the drawing board.