Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
gary_b2008
Starting Member
2 Posts |
 Posted - 2008-11-26 : 05:42:41
|
| Im moving a database from Access to SQL server for a call centre environment for about 40 users, each updateing the database about twice per minute. Each user calls a subset of the customer table and records call status (No Answer/Callback/Sale etc etc), along with user name, date, time of call. The customers that havnt been contacted are called again the next day and so on until they are contactedThe databae has 2 tables: a customer table and a calls table, I want a live dashboard style feature to see how many sales each user has so far for the day requiring an aggregate query. Relationally i should add a record to the calls table each time a customer is called but Im considering storing the calls for the day in extra fields in the customers table, and this data would be archived to the calls table nightly. Would this improve performance?Whats your ideas. Im using an Access Project as the front end. |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2008-11-26 : 11:11:27
|
| extra fields (uuugh)....become a real problem when being manipulated for reports, etc and also when the number of "calls" per customer per day exceed what you plan for.....design it right, and the performance will disappear away (once you implement indices properly)....you'll avoid far many other headaches than going the other way.you can always archive old calls to a similiar structured archive table at off peak times to maintain optimum performance. |
 |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2008-11-26 : 11:13:58
|
| You should just keep the Calls table the way it is. Just make sure you have a foreign key relationship between Calls and Customers.Depending on your requirements, you should consider adding a Sales table related to the Calls table with a foreign key. Usually you need to capture more information for a sale than on a typical call, and since Sales are much lower volume than calls, there is no reason to have them in the Calls table.CODO ERGO SUM |
|
|
|
|
|
|
Quicky... Skip on Relational Model For Speed...