Incident Support

Stay in control

Incident Support

An incident is an event that should be managed quickly or it may escalate into an emergency, crisis or a disaster.

Without effective management an incident can disrupt business operations, services, security and other vital business functions. Today most businesses rely heavily on their database availability and that is why database incident management is one the most critical component of business operations.

We can help you manage your database incidents effectively. In this process we will identify, analyze, and fix incidents and prevent future recurrences.

I need to resolve
my current incident

I would like to know
my database risks

I would like to decrease
future incidents

I need protection from
all future incidents

Over the years we have resolved numerous common incidents, which have leaded us to accrue a set of comprehensive standards, thresholds and flowcharts. We use all of our resources and expertise to successfully and quickly complete the diagnostic and troubleshooting process and avoid unnecessary cost.
  • Long Execution Duration
  • Low Concurrency
  • Slow Response Time
  • Deadlocks and Much Blocks
  • Timeouts
  • High Resources Consumptions
  • Security Breakdown
  • Slow ETL/SSIS Packages
  • Database Errors/Warning
  • Wrong Results
  • Lost Data
  • Data Corruption
  • Long Down Time
  • Data Availability Breakdown
  • Poor Data Modeling
  • Poor Database Design
  • Poor Middle Tier Design
  • Poor Application Design
  • Poor SQL Scripts
  • Poor Transaction Design
  • Weak Maintenance Plans (Indexes, Statistics, Data Archiving and etc.)
  • Unreliable Disaster Recovery Plan
  • Poor Data Space Design (File-Groups & Partition Schemes)
  • Poor Data Life Cycle Design (Active, Archived, Inactive and Historical Data)
  • Weak Application and Database Architecture
  • Unmanaged Side Effects
  • Incorrect SQL Server Configuration
  • Incorrect Operation System Configuration
  • Weak Infrastructure
  • Slow Network IO
  • Poor Error Handling
  • Poor Event and Error Logging
  • Not Maximizing SQL Server Features
  • Inadequate Tracing & Monitoring System
  • Old Versions of Main and Third Party Tools & Application
  • No Proactive Maintenance Plans
  • SQLMax Library
  • SQL Server DMVs/DMFs
  • Profiler
  • Windows and SQL Server Logs
  • Windows Performance Monitor
    • CPU
    • Memory
    • Data Read
    • Data Write
    • Physical Disk
    • Network
    • Database Files I/O
    • Waits & Latches
    • SQL Statistics
    • Locks
    • Plan Cache
    • Cursors
    • SQL Errors
    • SSIS

Incident Support Work Flow

  1. Incident Intake
    • Identification, categorization and logging
    • Prioritization based on impact, urgency and SLA guidelines
  2. Provide backups & baselines
  3. Incident Resolution Cycle
    • Investigate the causes of the incident and determine the affected area
    • Provide and apply the resolution
    • Evaluate results
    • Solution delivery
    • Restore/recovery
  4. Closing Procedure
    • Archive project logs and reports
    • Conduct post mortem meeting (Lesson Learned)