Michelle A. Poolet

Michelle A.
Poolet
Cofounder,
Mount Vernon Data Systems
10 142 10

Michelle Poolet, MCIS and Zachman Certified Enterprise Architect tm, has been part of the Information Technology community since long before she started Mount Vernon Data Systems LLC in 1990. She’s been working with Microsoft SQL Server since version 6.0, focusing on transactional database design, administration, and performance tuning. She’s also earned her chops in classroom teaching, OJT training, and IT systems project management.
 
For detailed information, check out Michelle’s profile on LinkedIn.

Articles
SAN Storage Server
The SQL Server 833, What Is It?
Here's a story that I'd like to share, about the infamous SQL Server 833. As you may know, an event 833 (or error 833, as it’s sometimes called) is a signal from the SQL Server that it’s waiting for records that it’s requested.
sql server database design drawing
Database Design Essentials
If you’re designing a database from scratch, there are 10 things you absolutely need to do to ensure a successful database project.
data architecture
What's the Difference Between a Data Architect and an Enterprise Architect? 1
Long story short, the enterprise architect's responsibility is over-arching across the entire enterprise, whereas the Data Architect has a subset of the enterprise architect's responsibilities, which are focused mainly on the data itself.
Software written on a computer screen
Comparative Review: Sizing Up Data Modeling Software 6
Find out how six popular data modeling software packages stack up to each other.
Building damaged by an earthquake disaster
The Smart DBA's Guide to SQL Server Disaster Recovery, Part 2
In this conclusion of our two-part series, we show you how to develop, deploy, and perform day-to-day maintenance of your SQL Server disaster-recovery plan.
laptop with fire flames on keyboard
The Smart DBA's Guide to SQL Server Disaster Recovery, Part 1
We apply the first 5 Ds of our 7D Method to the SQL Server disaster-recovery scenario. In Part 1, we focus on Discovery and Design, and in Part 2, we'll show you how to Develop, Deploy, and maintain your SQL Server disaster-recovery plan Day-to-Day.
eyeball looking through data
E-Discovery Q & A for Data Warehouse Administrators
At some point in your career you might get a request, possibly in the form of a court order, to hand over electronically stored information that’s under your care. What can you do to prepare for this eventuality?
Red Hard Disk Drive
What is Slack Space?
Slack space is a form of internal fragmentation, i.e., wasted space, on a hard disk.
Man typing on a computer keyboard with data in background
What is ESI?
Electronically stored information (ESI) is data and information that is created, manipulated, stored, transmitted, and utilized in digital form.
Computer data on disks under magnifying glass
What Are Forensic Images and Forensic Copies?
A forensic image is an image or exact, sector by sector, copy of a hard disk. A forensic copy is a file-level copy of data from a hard disk.
Data storage cubes
Design your Data Warehouse for Performance
Data warehouse performance is tied to the performance of the underlying storage subsystem. Discover what you need to know to design a storage subsystem for maximum performance.
Data Warehouse planning grid.
The Data Warehouse Project Discovery Phase
Gathering requirements is absolutely necessary in the discovery phase of successful data warehouse project. In this article, we'll walk through the highlights of gathering requirements for the three project tracks—Technology, Data, and Application Layer.
Checklist
Data Warehouse Requirements Checklist
When you're gathering requirements in the Discover phase of creating a data warehouse project here is a handy checklist.
data warehouse illustration
Some Musts To Avoid When Developing Your Data Warehouse Project
There are certain things you should NOT do when developing your data warehouse project. Here's a short list of nine musts to avoid.
yellow uh-oh road sign
Lessons Learned from Poor Data Warehouse Design 1
Here are the business and design factors that you need to consider and address when designing your data warehouse.
Comments
The Trouble with Type Tables
January 29, 2013
Good job explaining reasons to use what you call "type tables", what I call "lookup tables". Couple this articles with InstantDoc ID #48811, which I wrote...
A Case for Shorter SQL Server Conference Sessions
March 24, 2012
I'm with you, Brian -- 60 minutes is just too long for any presentation other than a class or workshop. Thirty minutes I can do, like you said, once or maybe even twice a...
Will SSDs Cause Performance Tuning Experts to Go the Way of the Milkman?
June 23, 2011
Brian, you have a point when you say "this is the first time Ive started to see a pattern of throwing hardware at the problem being a decent answer." Hardware, not...
Is There a Shortage of SQL Server Experts?
August 26, 2010
What's your definition of an Oracle DBA, and how would you define a SQL Server DBA? I'm not sure we're talking about the same perception here.

In my experience,...
Is Microsoft Leaving Small Business Behind?
March 22, 2010
You've obviously struck a nerve, Mike. Your points are very well taken. As a consultant to and advocate for small businesses, I agree with your assessment that the products you...
Newsletter Signup

Sponsored Introduction Continue on to (or wait seconds) ×