Free Webcast: Using the MMC to Manage and Learn TSQL and Source Code
Wednesday, March 8
Want to tune up your SQL Server Management skills. Our very own SQL Server MVP stephen Wynkoop is presenting a Free webcast next Wednesday, March 9th. Learn how to use MMC to generate code, interact with version control, and manage your servers. Click here to get registered now!
$$SWYNK$$
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)
Characteristics of an Architectural DBA
Today we come to the end of my DBA Characteristics Lists. Together we have brainstormed characteristics that are valuable to any DBA, characteristics unique to an Operational DBA, characteristics unique to a Developer DBA, and today Characteristics unique to a Database Architect
In my definition of a Database Architect they must understand the needs of an Operational DBA and a Developer DBA. They may even play both roles. They must understand those characteristics in order to effectively engineer a comprehensive database solution meeting Business needs
A Database Architect establishes the framework for hardware and software integration of relational databases and data warehouses with data sources and data consumers. They are skilled in:
- ETL tools such as SQL Server Integration Services,
- Database Design Patterns and Normalization for both relational databases and data warehouses
- Database Consumption Methods
- Data Storage Techniques such as Direct attached disk, SAN, SSD, RAID configurations
- Database Optimization Techniques such as Partitioned Tables, Queues, TSQL, Query Plans, Data File Separation, Partial Backup Techniques, Indexes, XML optimization, Full Text Indexing
- Database Failover Techniques such as Clustered SQL Servers, Mirroring, Replication, Log Shipping, SAN Replication and Third Party tools for failover
- Analysis of Requirements for new functionality or extended functionality, sometimes integrating with legacy systems outside of the Database
- Integration with External Appliances
These skills overlap to some degree with an Operational and Developer DBA. The Architect must be strong in all of these areas in order to design a comprehensive solution that a developer can implement, an operator can manage, and meets the necessary business requirements within budget.
Following are some characteristics I see in this individual that sets them apart:
- Experience – You can’t just do this without having been around the block
- Self Motivated – Must constantly be learning new technologies in Hardware and Software to provide the best solution. This often means they must learn technology on their own
- Networks – This is a characteristic I missed on the other DBA roles and should have included…but this is even more important for an Architect. There is too much to know, so network to enhance your ability to fill gaps in your experience
- Communicates to Peers – This individual must clearly communicate how things fit and work together (i.e. Packaging, ERD, Data Flow, Interfaces )
- Communicates to Management – Through understanding of the Business Opportunity and Available Budget the individual communicates optional solutions, benefits of each solution, and estimated cost
- Enables Others – Finds best results through enabling the success of others
- Generalized Specialist – Specializing in database capabilities with reasonable understanding of all data consumers in each layer
Today completes my series of DBA Characteristics. If you have more you’d like to add, drop me a line at btaylor@sswug.org.
Cheers,
Ben