damerit Posted November 14, 2008 Share Posted November 14, 2008 Guys, We have an application that has a table with around 27,000 records and the consist of open and closed call information. The uppers and some noobie are pushing to move the closed calls to seperate table, which does consist of 95% of the data. I suggested using an index because splitting the table will affect much source changes and I don't think splitting the table will be that much of a benefit. What do you guys think? Should we split or index? thanks, Link to comment https://forums.phpfreaks.com/topic/132715-index-or-split-fields/ Share on other sites More sharing options...
Barand Posted November 14, 2008 Share Posted November 14, 2008 Some of those closed calls are probably pretty old and it's maybe a good idea to archive them. Whether you archive on closure or when they become a certain age would, IMO, depend on how much processing/analysis was required on open and recently closed calls. For example, our help desk produces performance charts going back six months. After that there is no need for the closed ones to be on file unless we need to dredge up historical records. Link to comment https://forums.phpfreaks.com/topic/132715-index-or-split-fields/#findComment-690402 Share on other sites More sharing options...
Mchl Posted November 14, 2008 Share Posted November 14, 2008 27'000 records is not much for MySQL table. Using EXPLAIN you could probably find out, if adding indexes would speed up your queries. Link to comment https://forums.phpfreaks.com/topic/132715-index-or-split-fields/#findComment-690431 Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.