Jeremiah Peschka - Sept 5, 2014 Noon CST
Designing a Data Strategy
Jeremiah (Blog | LinkedIn | Twitter) solves data problems using SQL Server, Riak, Hadoop, and other database tools. He has over a decade of experience with performance tuning and scalability database. Jeremiah is a Microsoft MVP; MCITP for SQL Server 2005 – 2012; develops the .NET Riak client; and is a Cloudera Certified Developer for Apache Hadoop. He’s also a big fan of coffee.
If you’ve worried about outgrowing your current database or wasting countless hours moving to the wrong data platform, listen up. There is an overwhelming array of database options on the market, knowing which to pick is difficult. Before jumping in, it’s important to have a list of questions to make your decision easier. In this session, we’ll cover a set of questions to get your team started in the decision making process. This session is for senior developers and software architects looking to expand their horizons.
Data Architecture underpins just about
everything we do in IT. Without a clear understanding of how data is
structured, there is no reliable way to derive meaning from it. Data
Architecture drives the design and governance of data systems, and thus should
be of interest to any data professional. Data Architecture provides the
blue-prints that we all share, whether we be DBAs, data integration developers,
database developers, data warehousing professionals, data presentation
developers or client-side application developers persisting data for later
Data Architecture Virtual Chapter will focus on data architecture concerns as
they impact users, developers and DBAs on the Microsoft SQL Server platform. We
want to make data architecture accessible to all data practitioners, and drive
the point home that Data Architecture is a set of practices and a body of
knowledge that overlaps almost all database professionals to some degree.
at email@example.com or twitter is @DArchVC