Boxing Day : Tips For Getting Your Database Ready



Boxing has has been an Canadian tradition for decades. And retail analysts are expecting the 2017 edition to set new sales records. Analysts predict that many customers would rather wait get the Boxing day deals, then buying before Christmas. Considering the weather forecast saying that Boxing day will have traditional Canadian winter, analytics expect more customer would rather stay home and shop online then go out for door crasher deal. This also mean that your database should be up and running and working optimal during this shopping euphoria.

Review performance metrics from last year, forecast this year’s consumption, and then load test based on those numbers.

  • Pull the trends from last year’s holiday shopping weekend.

  • Trends should include the number of transactions/second, throughput, application and disk response time, batch requests/second, CPU, and memory utilizations

  • Forecast the current year’s load based on last year’s consumption

  • Assess whether the hardware can bear the forecasted capacity

  • Perform load testing on the servers, simulating the point-of-sale transactions

  • Adjust hardware based on the testing results

Evaluate backup and failover strategy, and perform disaster recovery testing

  • Ensure your backup strategy is proper and in place.

  • We also recommend having a redundant copy of your backup on an external storage device or in a data center

  • Ensure backups can be restored efficiently when needed

  • Perform a dry run of your backup and restore procedure

Perform disaster recovery (DR) testing to ensure your system runs properly on the DR server

  • Perform server health check and configuration check

  • Perform an overall health check of your database serverEnsure memory, NIC cards, and hard disks are all healthy

  • Ensure power connectivity and power backups are in place

Perform a database configuration check:

  • Look for common configurations, make sure memory settings are accurate, and ensure threads, parallelism, and other settings are per the hardware

  • Test high availability solution and perform connection pooling for estimated traffic

  • The database server should be able to manage the estimated number of incoming requests during peak traffic times.

  • Ensure that the application and the database are configured for connection pooling and that it is set to an optimal value

The database server should be configured for any hardware failure as well as any database failure, which means an appropriate high-availability solution should be in place.

For example:

  • For SQL Server: Clustering along with mirroring, log shipping, replication, always on, etc.

  • For Oracle: RAC along with a standby database, replication, always on, etc.

Ensure all recent, ongoing, and pending issues are resolved

  • Extract and analyze the errors and issues that have occurred recently or are recurring in nature, including problems and incidents recently fixed

  • Review recent changes to your database configuration, including changes made due to a problem or incident. These may include patch updates, application updates, structural changes, added schedules, modified file parameters, and other configurable items

  • Establish freeze datesTo avoid unseen risks, implement a code/configuration freeze date

  • List challenges and risks involved with any unavoidable implementations

  • Review any changes with respect to all points mentioned above