Our next meeting is Thursday, April 26 - 6:30pm

Ryan Duclos will return to present "SQL Azure Reporting"  

This is the same session he's planning for SQL Saturday #132 (June 9), so we've offered him the chance to work out any pacing bugs with the new presentation while we get to see it first!  So for those who planned to see it at SQL Saturday,  it's like getting a free extra session!

Description

SQL Azure Reporting is a CTP offering and part of the SQL Azure and Windows Azure Platform. The SQL Azure Reporting component is based on SQL Server Reporting Services (SSRS). It is a cloud-based service offerring a subset of SSRS technology. In this session we will go over the basics of getting SQL Azure Reporting setup and wired up.

***It is assumed that you have familiarity with designing/managing SSRS reports

About the speaker

Ryan Duclos is a Senior Technical Consultant for Perficient, Inc. (PRFT), where he is passionate about Microsoft development utilizing the .Net Framework, SQL Server, and Windows Azure technologies. He lives and works in LA (Lower Alabama!) and loves spending time with his family, as well as being a Community Influencer for Microsoft.

Ryan is the President of the Lower Alabama .NET User Group and is also involved with the Pensacola SQL Server User Group. In addition Ryan is a frequent speaker at numerous Code Camps, SQL Saturday & User Group events.

Location 

Pensacola State College

1000 College Blvd, Pensacola, FL

Room 2169 

Click here for map

Topic 1:	Change Data Capture
Description:	Change Data Capture (CDC) is one of the new features available for SQL Server 2008 Enterprise and Developer Editions, which allows you to easily track and keep history of all DML (Data Manipulation Language) changes on user tables such as INSERTs, DELETEs, and UPDATEs with little or no overhead. Change Data Capture has been used primarily to track changes for incremental loads using SSIS for the ETL process in Data Warehousing and Business Intelligence because it allows you to identify new data and data that changed or was deleted since last incremental load. Before Change Data Capture in SQL Server 2005 and prior versions, identifying new or changed data required some level of custom programming, triggers or third party tools. These solutions work well but introduce additional overhead to your production systems. This is the main reason why Change Data Capture was introduced in SQL Server 2008; to eliminate overhead while tracking new and changed data. But Change Data Capture use is not limited as a tool for ETL Process. It can be used for many other purposes where overhead, simplicity and cost might impose a restriction. Some of these scenarios include: 1) You are a developer adding or modifying existing code and you need to see the difference in the data output on a particular table. 2) You are a DBA and need to audit several tables in a database and need to report which data was changed, what were the new and previous values, who did the change and when was the change made. 3) You were tasked to delete several records on a highly transactional production database and unintentionally deleted records that you were not supposed to with no possibility of rolling back the changes (no explicit transaction) and no possibility of restoring a backup. 4) You are a DBA and need to know which tables and columns are being written to the most in your database. 5) You are a DBA and need to know how many new records are being entered into your database in a period of time and the percentage of change of existing records. In most cases you would want to know what changed and which were the values before the change. One of the most important benefits of this feature is that it allows you to see the data before & after an UPDATE or DELETE statement, which in turn allows you to query and recover data overwritten or deleted quickly without the need of a database restore. It also captures each new row inserted. CDC accomplishes this task by reading the committed operations from the log file and inserting the changed records in a tracking table that mirrors the source (tracked) table. The records inserted in this tracking table contain both the value before the change and the value after the change along with the metadata associated with the change. The metadata can be queried to identify the type of DML operation as follows: 1 = Delete 2 = Insert 3 = Update (record’s value before update) 4 = Update (record’s value after update)
Go to Source:	http://sqljoe.wordpress.com/2010/08/18/change-data-capture-as-a-tool-for-business-intelligence-disaster-recovery-auditing-and-more/
Location:	We will be meeting in room 509, which we have reserved from 5:30-9:00pm
Map:
Campus Map:	Click for a detailed PSC campus map