Jump to content

index or split fields


damerit

Recommended Posts

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
Share on other sites

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
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.