Transcript Oakwood Modern PowerPoint Template

What is the role of a
SQL Server
Architect?
SQL Server Architect
And would you ever want
to be one?
Scott Shaw, MCT, MCSA
[email protected]
www.dbaexperience.com
@shawsql
http://www.linkedin.com/
in/scottpshaw
Big Data
Business Intelligence
Database Administration
NoSQL
Hadoop
Agenda
• Overview of Data
Management Roles
• Emerging Technologies
• SQL Architect
Expectations
• The pluses and the
minuses
• Data Management is not
restricted to being only a
DBA
• The expectations for a
SQL Architect can be
daunting
• The role may differ
depending on the
environment
Data Management Roles







SQL Server Developer
SQL Server DBA
SQL Server Consultant
SQL Server BI Administrator
SQL Server ETL Developer
SQL Server Data Warehouse Administrator
SQL Server Architect
Many of these skills are combined and mixed together
Data Management Roles
 What I see are contributing factors to the confusion:
 There is no SQL Server “degree”
 Few people, especially those hiring, have any idea what we do.
 Many companies don’t know what the problem is. They only know they have data
issues.
 The industry is dependent on buzzwords
 Companies have been burned by unqualified, “accidental” DBA’s.
 Salaries are high – what are companies getting for their money?
 Assumption that an individual can know all the skills
Changing Roles
 Requirements are changing and the traditional DBA role is becoming more and
more complex. DBA’s may be required to:






Advise on and implement BI solutions
Architect hardware recommendations
Configure virtual server environments
Integrate disparate database systems
Troubleshoot and performance tune SAN environments
Develop stored procedures and functions
It’s no longer about just keeping the lights on
Emerging Technologies
In-Memory
Databases
NoSQL Solutions
Azure (Cloud
Computing)
Private Cloud
Big Data - Hadoop
MPP Appliances
Polyglot\Polybase
Hybrid
Architectures
Role of the SQL Architect
The primary role of a SQL Architect is to put it all
together in the context of business objectives
The solution must be accessible by both nontechnical and technical business owners
Other Considerations
 A architect must be concerned with the scope and feasibility of delivery.
 This is why it is critical for a SQL Architect to have delivery experience
 An architect needs to be open to unfamiliar technologies which may, in fact,
serve a company better than known technologies
 An architect needs to understand the “system” and all dependent processes
 How will implementation of the solution affect other components?
 An architect is the “Google” of the company
 He\She is who they go to for answers
Most Common Questions
FAQs
What are other
companies doing?
Which is the best
option?
Can you discover and
document our
environment?
How can we scale?
Technical Questions








High availability
Disaster recovery options
Virtualization
Licensing
Maintenance plans
Hardware specification
Data and log file strategies
“Best Practices”
Role of the SQL Architect
In many cases, companies simply want to make sure
they are on the right path
Upsides
What are the upsides to
being a data architect?
• Explore new technologies
and their relationships
• Sense of control and
influence
• Insight into enterprise
business objectives
• No on-call pager
Downsides
Sound exciting? Keep these
things in mind.
• Stressful, on-the-spot
questioning.
• Documentation,
documentation,
documentation.
• Take your work home with
you
• Lack of a sense of
completion
Characteristics of a Good Architect
If you want to be an
architect:
• Be comfortable with
feeling uncomfortable
• Be willing to take a stand
on what you know is the
right solution
• Be open to alternative
ideas
• Develop the ability to
listen
• Develop a resume of
unique experiences
Questions?
QUESTIONS?