Editorials

Characteristics of a Architectural DBA

Find Out What’s New at SSWUG SelecTViews
Check out this week’s SelectTViews So much data, so many databases…to the moon! Cloud exit strategies, cloud security considerations, wireless access to data… Jeopardy!(tm) ….and the SSWUG Virtual Conference, Bus. Intelligence Upgrade hesitations and much more.

$$SWYNK$$

Featured Article(s)
Top Ten Database Blunders (Part 1 of 4)
As a PTO (Performance, Tuning, and Optimization) consultant, I’ve seen some pretty crazy problems. Although the names have been changed, these stories are true. You’ll hear me rank the 10 worst real-life blunders, why they’re so expensive, and how to avoid them in your career.

Featured White Paper(s)
Essential Performance Tools for SQL Server DBAS
Optimizing SQL Server performance can be a daunting task. Especially so for an increasing number of reluctant DBAs faced with… (read more)

Featured Script
dba3_prc_DaysWeeksYearsInRange_Article
— Determine the days weeks and years in a given range — Modeling Date Logic II: Queries, Functions, Procedures for Busines… (read more)

Characteristics of a Development DBA
As a continuation of Characteristics for a DBA, today I am considering the role of the Database designer. In my opinion, this title represents the DBA who designs what the Operations DBA maintains.

This is a completely different set of skills. In fact, the goals are somewhat different so that conflict between the two different roles may arise.

  • Loves Change in a Good Way – Perfects and extends database design and performance strategies
  • Documents – Schema (ERD) and Procedural Interfaces
  • Security Guru – Understands and implements Schemas, Views, Stored Procedures, Alias, etc. effectively resulting in reduced exposure
  • Thirsts for Technology – Craves a thorough understanding of database design techniques and query methods resulting in optimized performance. Learns the nuances of the database engine
  • Expands Skills Beyond Database Code – Understands the impact of the database design on the consumers (walk in the other guys shoes). Able to contribute to ORM
  • Requires Accuracy – Thoroughly tests Database Procedural Code, Schema accuracy and default data (lookup table contents)
  • Follows Release Process – Manages Release of Database Change efficiently in conjunction with application code. This process reduces the conflict with Operations though clear communication of change.

Tomorrow we’ll look at a the characteristics of a Database Architect…the individual who puts all the different SQL Server technologies together resulting in a complete persistence architecture with ETL, Data Warehousing, Broker Services, Reporting, SharePoint, etc.

As always, your comments are welcome. Send you additions, contradictions or comments for DBA characteristics (or anything else for that matter) in an email to btaylor@sswug.org.

Cheers,

Ben