XenDesktop 5 Database Sizing and Mirroring Best Practices精选.pdfVIP

XenDesktop 5 Database Sizing and Mirroring Best Practices Table of Contents Database Planning 2 Database Sizing 2 Sizing the database file 2 Sizing the transaction log 3 Database Mirroring 4 Database Mirroring Options 4 Database Mirroring Setup 4 Broker SQL Configuration String Setup 5 Database Mirroring Best Practices 6 Controller configuration changes 6 Database Mirroring Maintenance 7 Deleting a Mirrored Database 7 External References 8 Page 1 Database Planning There are a number of important areas to consider when planning an SQL database for XenDesktop 5.0, including: • Database Sizing • Database Mirroring This article provides information about database sizing and mirroring, discusses some best practices, and provides links to additional information. Database Sizing When sizing an SQL database, two aspects are important: 1. The database file 2. The database transaction log file Sizing the database file The size of the database file de pends on the following factors: • The number of configured and registered workstations • The number of connected sessions • The connection rate • The number of managed desktops • The number of provisioned desktops Each of the above factors impacts the sizing requirements. Each desktop (managed or unmanaged) requires: • Approximately 2.9 KB for registration and worker state information • Approximately 5.1 KB for session state. • 0.042 KB for each connection log record. By default, these are purged after 48 hours. Each MCS provisioned desktop also requires: • Approximately 1.8 KB for Active Directory computer account information • Approximately 1.94 KB for MCS machine information For example, with 20,000 unmanaged desktops, in a