và phân phối dữ liệu này để tất cả các khách hàng thời gian thực được kết nối với nó. Những khách hàng này có thể là khác AWS, thường là một AW khách hàng. rtclient: khách hàng thời gian thực trên AW chịu trách nhiệm cho việc cập nhật cơ sở dữ liệu AW địa phương. | Chapter 14 UCCE Databases 223 the majority of tables have a 14-day retention period with some tables having a default of 30 days. Table 14-3 Administrative Workstation Types AW Name Type Purpose Database Administration Client Ability to view and modify the UCCE configuration but it has no database Administration Server and Real-time Data Server AW Configuration Real-time reporting Configuration-only Administration Server Configuration Administration Server Real-time and Historical Data Server and Detail Data Server AW-HDS-DDS Configuration Real-time and historical reporting Call detail extraction call variable and agent detail Cisco Unified Intelligence Suite Feed Administration Server and Real-time and Historical Data Server AW-HDS Configuration Real-time and historical reporting Historical Data Server and Detail Data Server HDS-DDS Historical reporting Call detail extraction call variable and agent detail Cisco Unified Intelligence Suite Feed Note You can also set purge cycles for the galaxy tables but these settings have been omitted from this table. The purge settings can be modified in the registry but the more intuitive way is to run through web setup for the respective servers. Figures 14-2 and 14-3 display the data retention settings and purge settings during logger setup. If you change the settings on one logger it is recommended that you also mirror the changes on the second logger. Data retention periods for the HDS are typically much greater than for the logger and usually run into several years rather than a number of days or weeks. The purge cycle will still run on a daily basis however and delete data that is older than the retention period. Another purge mechanism that operates on the UCCE databases prevents the database from growing beyond 80 percent of capacity. Should a database grow beyond this size system performance can degrade. The database-sizing purge also occurs on a daily basis at the scheduled purge time. Administrators should be aware .
