RKRizwan Khan
← Back to all projects

Peter-Kremser · Data & Automation · August 2012 — September 2012

Peter-KremserDatabase Administrator

I structured the design, performance, backup and automated maintenance of an SQL database as one connected operating process.

Organisation
Peter-Kremser
Period
August 2012 — September 2012
Role
Database Administrator
Focus
Data & Automation
Peter-Kremser: Abstract infrastructure illustration for the Peter-Kremser engagement

Situation

The database needed a clear technical basis for schema, indexing, backup, recovery, jobs, replication and controlled data import and export.

Constraints

  • Changes within an already established IT environment
  • Short, clearly scoped engagement
  • Internal system and operating details remain confidential

My scope of responsibility

I took over database administration from design and indexing to backup, recovery, agent jobs, replication and file management.

Documented scope of work

Key decisions

Optimise database design and operations together. Indexes, files, jobs, backup and replication affect one another; isolated measures could have created new bottlenecks.

  1. I planned the database structure and indexing for efficient queries.
  2. I implemented backup, restore and maintenance workflows with database agent jobs.
  3. I configured replication, file management and import and export processes.

Technology in use

SQL Server

SQL Server was part of the documented toolset in this Data & Automation engagement.

Indexing

Indexing was part of the documented toolset in this Data & Automation engagement.

Backup & Restore

Backup & Restore was part of the documented toolset in this Data & Automation engagement.

Replication

Replication was part of the documented toolset in this Data & Automation engagement.

SQL Agent

SQL Agent was part of the documented toolset in this Data & Automation engagement.

Evidence and limits

The database gained a traceable foundation for performance, maintenance and recoverability.

Role
Database Administrator
Period
August 2012 — September 2012

Lesson from the engagement

Database stability comes from the interplay of logical design and a disciplined operational lifecycle.

Confidentiality note: Internal architecture and operating data of this engagement are not published.

Related case studies

Planning a demanding change to your Microsoft infrastructure?

View PowerShell Automation as a service Discuss your project