Brian H. Madsen
4/27/2007 11:31:09 PM
**** NOTICE - STARTING TIME HAS CHANGED *****
Last month we discussed both the time and also what everybody's thought were regarding having a virtual presentation.
The time wasn't quite resolved IMHO as one slot was the same as we currently have whilst the other was an earlier slot.
If you think it would be a good idea, I'd like to trial the earlier time slot and see how that goes. Let me know by emailing me at firstname.lastname@example.org (my sqlserver.org.au email is still swamped and we are possibly going to set up a different account for me).
But, the concensus was pretty much that a virtual presentation at the venue would be a good idea to try out. This opened up an opportunity which has been presented so far to a few of the other SQL Server user groups across the country - which is of course the reason for this email.
We are going to try it out here in Perth - and May is the target month for this event.
A few news items - we have a new SQL Server MVP in Australia. A well-deserved recognition came in form of a notification email to Peter Ward on the 1st of April. You may remember we had him across earlier this year in one of the best presentations we've had so far. Matched only by Greg Linwoods index presentation.
I myself also received yet another award from MSFT - i'm still an MVP Visual Developer ASP.Net. This also came in form of the email on the 1st of April.
Anyways, on to the topic..
*** Event Details *******************************
Topic: Secrets of Fast Detection and Recovery from Database Corruptions
Presenter: Paul Randal, Redmond, SQL Server Storage Engine
Date: 10th of May 2007
Venue: Excom offices, Level 2, 23 Barrack Street
About the Presenter:
Paul started in the industry in 1994 working for DEC on the VMS file system and check/repair tools. In 1999 he moved to Microsoft to work on SQL Server, specifically on DBCC.
For SQL Server 2000, he concentrated on index fragmentation (writing DBCC INDEXDEFRAG, DBCC SHOWCONTIG) and various algorithms in DBCC CHECKDB. During SQL Server 2005 development was the lead developer/manager of one the core dev teams in the Storage Engine, responsible for data access and storage (DBCC, allocation, indexes & heaps, pages/records, text/LOB storage, snapshot isolation, etc). He also spent several years rewriting DBCC CHECKDB/repair.
Since SQL Server 2005 shipped, Paul has managed the Program Management team for the core Storage Engine to become more focused on customer/partner engagement and feature set definition.
Paul regularly presents at conferences around the world on high-availability, disaster recovery and Storage Engine internals. His popular blog is at http://blogs.msdn.com/sqlserverstorageengine.
About the event:
How can you tell whether your data is corrupt? If you have corruption, how do you work out what’s wrong with the database? How do you ensure you have a valid backup? If you don’t have a valid backup, how and what do you repair? If you do have a backup, how do you work out whether you should restore or repair? And at what granularity? How do you go about determining what went wrong in the first place? It’s all about limiting downtime and data-loss when a corruption occurs - from knowing the tools to understanding the choices to planning a successful strategy. Some of the features discussed: torn-page detection and page checksums, IO read-retry, backup checksums, consistency checks (DBCC CHECKDB and related commands), and database repairs. Facing database corruption is almost inevitable in every DBAs career - make sure you're prepared when it happens to you.
To recap, this will be a virtual presentation, where Paul will be sitting in Redmond and we will go through this via Live Meeting.
I will try and do a screencapture trial with Live Meeting and hopefully it'll run fine.
Hope to see you there!!!!
Venue: Level 2, 23 Barrack St - Excom Offices |
Duration 2 |
On: Thursday, May 10, 2007