Workspace Streaming

A lot of customers (especially specialist DBAs) ask us time and again what needs to go in as a part of the regular database maintenance cycle for SQL Server Database Server hosting Symantec SWS DB. While we leave it to MS to talk about general SQL DB maintenance in detail, we shall elucidate a few generic practices that will help keep SWS database well oiled, greased and in good shape. This can also be used as a generic best practice for other DBs as well. Also note that the points are SQL centric, as most of our customers use MS SQL DB.

1. IF possible, host SWS database on a separate server

   Do not get us wrong here. We are NOT demanding a separate Server for hosting our DB alone. Albeit light weight, we still consider our streaming and Virtualization systems to be Important. We have observed on occasions that some error(s) on other databases percolate through the system, effectively putting the SWS Database (Appstream) in bad shape.

   NOTE: The above is just a suggestion. SWS can coexist with other DBs in the same server. This is available out of box with default installation.

2. Keep the DB updated with latest DB updates

   Updates typically are bug fixes and / or performance enhancement tweaks. So always helps to keep the DB updated.

3. Allocate and monitor memory usage

   Allocate enough memory for the DB and ensure that the allocated memory is fully utilized by the Database. The allocation of memory would depend on observation during peak usage.

4. Maintain data files and log files on physical drives, but on different drives

   This is a recommendation from MS to ensure that there are minimal I/O conflicts and resource contention.

5. MS recommends that file growth be monitored and controlled in DB.

   File growth is inevitable with usage, but it has to be controlled and monitored. Fifty Mb file size is recommended for a 50 GB database.

6. Use tools to defragment the database and re-index all databases in the server.

   This improves performance.

7. Any scheduled job on databases that have been moved or deleted has to be terminated.

   If the server in the past hosted an application database, with scheduled jobs created around that database, and if that DB was removed or terminated for some reason, it is the administrator's responsibility to terminate those scheduled jobs. Otherwise, the jobs will continue to run in the background and in the process consume resources.

8. Disable or remove unnecessary logins for easier Control and Maintenance
9. Designate a DBA to maintain and monitor the database.

   It would certainly be a great advantage if the DBA also had some idea about the way the product works and also some knowledge about the SWS DB Schema.