<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Database maintenance</title><link>https://community.telligent.com/community/11/w/user-documentation/67222/database-maintenance</link><description /><dc:language>en-US</dc:language><generator>14.0.0.586 14</generator><item><title>Database maintenance</title><link>https://community.telligent.com/community/11/w/user-documentation/67222/database-maintenance</link><pubDate>Thu, 18 Jul 2019 17:06:18 GMT</pubDate><guid isPermaLink="false">4b24631f-5f26-461c-a4cd-5fb90f3aeb16</guid><dc:creator>Grant Pankonien</dc:creator><comments>https://community.telligent.com/community/11/w/user-documentation/67222/database-maintenance#comments</comments><description>Current Revision posted to User Documentation by Grant Pankonien on 07/18/2019 17:06:18&lt;br /&gt;
&lt;p&gt;[toc]&lt;/p&gt;
&lt;p&gt;Maintenance is not always considered when deploying a database; however, we have found that maintenance can be a critical component to maintaining the health of a database. As a general rule, all tables with clustered indexes should be reindexed on a schedule. We recommend that you do this once a week. However, depending on your community&amp;#39;s activity, you may want to do this once a month.&lt;/p&gt;
&lt;h3 id="database_maintenance_scripts"&gt;&lt;a name="Database_maintenance_scripts"&gt;&lt;/a&gt;Database maintenance scripts&lt;/h3&gt;
&lt;p&gt;Telligent Community Server includes a number of database maintenance scripts:&lt;/p&gt;
&lt;h4 id="database_reindex"&gt;&lt;a name="Database_reindex"&gt;&lt;/a&gt;Database reindex&lt;/h4&gt;
&lt;p&gt;We include the&amp;nbsp;&lt;span style="font-family:courier new,courier;"&gt;cs_system_dbreindex&lt;/span&gt;&amp;nbsp;stored procedure in the Community Server &amp;nbsp;codebase. &lt;span style="font-family:courier new,courier;"&gt;cs_system_dbreindex&lt;/span&gt;&amp;nbsp;can be scheduled (via a SQL Job) to reindex clustered indexes.&lt;/p&gt;
&lt;h4 id="table_statistics"&gt;&lt;a name="Table_statistics"&gt;&lt;/a&gt;Table statistics&lt;/h4&gt;
&lt;p&gt;Table statistics should be updated on days that reindexing does not occur. Again, there is a stored procedure included in the Community Server codebase called&amp;nbsp;&lt;span style="font-family:courier new,courier;"&gt;cs_system_updatestatistics&lt;/span&gt; that can be scheduled for this purpose.&amp;nbsp;&lt;/p&gt;
&lt;h3 id="database_growth"&gt;&lt;a name="Database_growth"&gt;&lt;/a&gt;Database growth&lt;/h3&gt;
&lt;p&gt;We have also found that people generally do not track physical database and log growth over time. Tracking table and index growth over time gives you an idea of how fast your community is growing and can give you an idea of what your disk space needs will be.&lt;/p&gt;
&lt;p&gt;Tracking physical database growth can be done with the SQL Server stored procedure &lt;span style="font-family:courier new,courier;"&gt;sp_spaceused&lt;/span&gt;&amp;nbsp;on a table-by-table basis. Additionally, the number of rows per table is a good metric. The number of rows per table provides you with the averages of the growth of your data over time within your community.&lt;/p&gt;
&lt;h3 id="database_backups"&gt;&lt;a name="DatabaseBackups"&gt;&lt;/a&gt;Database backups&lt;/h3&gt;
&lt;p&gt;We recommend that you schedule a single full-database backup once a week; a differential backup each day (not on full backup days), and log backups for the maximum recovery time you are allotted for your site.&lt;/p&gt;
&lt;p&gt;For more information about backup options refer to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx" rel="noopener noreferrer" target="_blank"&gt;http://msdn.microsoft.com/en-us/library/ms187510.aspx&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For additional data about backup schedules refer to&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://vyaskn.tripod.com/sql_server_administration_best_practices.htm" rel="noopener noreferrer" target="_blank"&gt;http://vyaskn.tripod.com/sql_server_administration_best_practices.htm&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Even though&amp;nbsp;older versions of SQL Server are specified, the processes are the same.&lt;/p&gt;
&lt;h3 id="database_tracing"&gt;&lt;a name="Tracing"&gt;&lt;/a&gt;Database tracing&lt;/h3&gt;
&lt;p&gt;The most effective way to determine load on your website is through some simple database traces achieved with SQL Profiler or Windows Perfmon (&lt;span style="font-family:courier new,courier;"&gt;perfmon.exe&lt;/span&gt;). For SQL Profiler, initial traces can use the default settings.&amp;nbsp;From there, you can determine if more precise traces are necessary. &lt;a href="http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/852720c8-7589-49c3-a9d1-73fdfc9126f0.mspx?mfr=true" rel="noopener noreferrer" target="_blank"&gt;Click here &lt;/a&gt;for an exhaustive guide to counters that can help track performance of your IIS service.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: database&lt;/div&gt;
</description></item><item><title>Database maintenance</title><link>https://community.telligent.com/community/11/w/user-documentation/67222/database-maintenance/revision/2</link><pubDate>Mon, 01 Jul 2019 18:07:27 GMT</pubDate><guid isPermaLink="false">4b24631f-5f26-461c-a4cd-5fb90f3aeb16</guid><dc:creator>Former Member</dc:creator><comments>https://community.telligent.com/community/11/w/user-documentation/67222/database-maintenance#comments</comments><description>Revision 2 posted to User Documentation by Former Member on 07/01/2019 18:07:27&lt;br /&gt;
&lt;p&gt;[toc]&lt;/p&gt;
&lt;p&gt;Maintenance is not always considered when deploying a database; however, we have found that maintenance can be a critical component to maintaining the health of a database. As a general rule, all tables with clustered indexes should be reindexed on a schedule. We recommend that you do this once a week. However, depending on your community&amp;#39;s activity, you may want to do this once a month.&lt;/p&gt;
&lt;h3 id="database_maintenance_scripts"&gt;&lt;a name="Database_maintenance_scripts"&gt;&lt;/a&gt;Database maintenance scripts&lt;/h3&gt;
&lt;p&gt;Telligent Community Server includes a number of database maintenance scripts:&lt;/p&gt;
&lt;h4 id="database_reindex"&gt;&lt;a name="Database_reindex"&gt;&lt;/a&gt;Database reindex&lt;/h4&gt;
&lt;p&gt;We include the&amp;nbsp;&lt;span style="font-family:courier new,courier;"&gt;cs_system_dbreindex&lt;/span&gt;&amp;nbsp;stored procedure in the Community Server &amp;nbsp;codebase. &lt;span style="font-family:courier new,courier;"&gt;cs_system_dbreindex&lt;/span&gt;&amp;nbsp;can be scheduled (via a SQL Job) to reindex clustered indexes.&lt;/p&gt;
&lt;h4 id="table_statistics"&gt;&lt;a name="Table_statistics"&gt;&lt;/a&gt;Table statistics&lt;/h4&gt;
&lt;p&gt;Table statistics should be updated on days that reindexing does not occur. Again, there is a stored procedure included in the Community Server codebase called&amp;nbsp;&lt;span style="font-family:courier new,courier;"&gt;cs_system_updatestatistics&lt;/span&gt; that can be scheduled for this purpose.&amp;nbsp;&lt;/p&gt;
&lt;h3 id="database_growth"&gt;&lt;a name="Database_growth"&gt;&lt;/a&gt;Database growth&lt;/h3&gt;
&lt;p&gt;We have also found that people generally do not track physical database and log growth over time. Tracking table and index growth over time gives you an idea of how fast your community is growing and can give you an idea of what your disk space needs will be.&lt;/p&gt;
&lt;p&gt;Tracking physical database growth can be done with the SQL Server stored procedure &lt;span style="font-family:courier new,courier;"&gt;sp_spaceused&lt;/span&gt;&amp;nbsp;on a table-by-table basis. Additionally, the number of rows per table is a good metric. The number of rows per table provides you with the averages of the growth of your data over time within your community.&lt;/p&gt;
&lt;h3 id="database_backups"&gt;&lt;a name="DatabaseBackups"&gt;&lt;/a&gt;Database backups&lt;/h3&gt;
&lt;p&gt;We recommend that you schedule a single full-database backup once a week; a differential backup each day (not on full backup days), and log backups for the maximum recovery time you are allotted for your site.&lt;/p&gt;
&lt;p&gt;For more information about backup options refer to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx" rel="noopener noreferrer" target="_blank"&gt;http://msdn.microsoft.com/en-us/library/ms187510.aspx&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For additional data about backup schedules refer to&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://vyaskn.tripod.com/sql_server_administration_best_practices.htm" rel="noopener noreferrer" target="_blank"&gt;http://vyaskn.tripod.com/sql_server_administration_best_practices.htm&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Even though&amp;nbsp;older versions of SQL Server are specified, the processes are the same.&lt;/p&gt;
&lt;h3 id="database_tracing"&gt;&lt;a name="Tracing"&gt;&lt;/a&gt;Database tracing&lt;/h3&gt;
&lt;p&gt;The most effective way to determine load on your website is through some simple database traces achieved with SQL Profiler or Windows Perfmon (&lt;span style="font-family:courier new,courier;"&gt;perfmon.exe&lt;/span&gt;). For SQL Profiler, initial traces can use the default settings.&amp;nbsp;From there, you can determine if more precise traces are necessary. &lt;a href="http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/852720c8-7589-49c3-a9d1-73fdfc9126f0.mspx?mfr=true" rel="noopener noreferrer" target="_blank"&gt;Click here &lt;/a&gt;for an exhaustive guide to counters that can help track performance of your IIS service.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: database&lt;/div&gt;
</description></item><item><title>Database maintenance</title><link>https://community.telligent.com/community/11/w/user-documentation/67222/database-maintenance/revision/1</link><pubDate>Mon, 01 Jul 2019 18:02:40 GMT</pubDate><guid isPermaLink="false">4b24631f-5f26-461c-a4cd-5fb90f3aeb16</guid><dc:creator>Former Member</dc:creator><comments>https://community.telligent.com/community/11/w/user-documentation/67222/database-maintenance#comments</comments><description>Revision 1 posted to User Documentation by Former Member on 07/01/2019 18:02:40&lt;br /&gt;
&lt;p&gt;[toc]&lt;/p&gt;
&lt;p&gt;Maintenance is not always considered when deploying a database; however, we have found that maintenance can be a critical component to maintaining the health of a database. As a general rule, all tables with clustered indexes should be reindexed on a schedule. We recommend that you do this once a week. However, depending on your community&amp;#39;s activity, you may want to do this once a month.&lt;/p&gt;
&lt;h3 id="database_maintenance_scripts"&gt;&lt;a name="Database_maintenance_scripts"&gt;&lt;/a&gt;Database maintenance scripts&lt;/h3&gt;
&lt;p&gt;Telligent Community Server includes a number of database maintenance scripts:&lt;/p&gt;
&lt;h4 id="database_reindex"&gt;&lt;a name="Database_reindex"&gt;&lt;/a&gt;Database reindex&lt;/h4&gt;
&lt;p&gt;We include the&amp;nbsp;&lt;span style="font-family:courier new,courier;"&gt;cs_system_dbreindex&lt;/span&gt;&amp;nbsp;stored procedure in the Community Server &amp;nbsp;codebase. &lt;span style="font-family:courier new,courier;"&gt;cs_system_dbreindex&lt;/span&gt;&amp;nbsp;can be scheduled (via a SQL Job) to reindex clustered indexes.&lt;/p&gt;
&lt;h4 id="table_statistics"&gt;&lt;a name="Table_statistics"&gt;&lt;/a&gt;Table statistics&lt;/h4&gt;
&lt;p&gt;Table statistics should be updated on days that reindexing does not occur. Again, there is a stored procedure included in the Community Server codebase called&amp;nbsp;&lt;span style="font-family:courier new,courier;"&gt;cs_system_updatestatistics&lt;/span&gt; that can be scheduled for this purpose.&amp;nbsp;&lt;/p&gt;
&lt;h3 id="database_growth"&gt;&lt;a name="Database_growth"&gt;&lt;/a&gt;Database growth&lt;/h3&gt;
&lt;p&gt;We have also found that people generally do not track physical database and log growth over time. Tracking table and index growth over time gives you an idea of how fast your community is growing and can give you an idea of what your disk space needs will be.&lt;/p&gt;
&lt;p&gt;Tracking physical database growth can be done with the SQL Server stored procedure &lt;span style="font-family:courier new,courier;"&gt;sp_spaceused&lt;/span&gt;&amp;nbsp;on a table-by-table basis. Additionally, the number of rows per table is a good metric. The number of rows per table provides you with the averages of the growth of your data over time within your community.&lt;/p&gt;
&lt;h3 id="database_backups"&gt;&lt;a name="DatabaseBackups"&gt;&lt;/a&gt;Database backups&lt;/h3&gt;
&lt;p&gt;We recommend that you schedule a single full-database backup once a week; a differential backup each day (not on full backup days), and log backups for the maximum recovery time you are allotted for your site.&lt;/p&gt;
&lt;p&gt;For more information about backup options refer to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx" rel="noopener noreferrer" target="_blank"&gt;http://msdn.microsoft.com/en-us/library/ms187510.aspx&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For additional data about backup schedules refer to&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://vyaskn.tripod.com/sql_server_administration_best_practices.htm" rel="noopener noreferrer" target="_blank"&gt;http://vyaskn.tripod.com/sql_server_administration_best_practices.htm&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Even though&amp;nbsp;older versions of SQL Server are specified, the processes are the same.&lt;/p&gt;
&lt;h3 id="database_tracing"&gt;&lt;a name="Tracing"&gt;&lt;/a&gt;Database tracing&lt;/h3&gt;
&lt;p&gt;The most effective way to determine problems within the database (related to performance) is through SQL Profiler.&amp;nbsp; An&amp;nbsp;&lt;a href="http://technet.microsoft.com/en-us/library/aa173918(v=SQL.80).aspx" rel="noopener noreferrer" target="_blank"&gt;exhaustive review of SQL Profiler can be found here&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: database&lt;/div&gt;
</description></item></channel></rss>