Problem 1 Developers come to you with a new physical database server that hosts a single database. It’s going to be your responsibility now. Currently the server is running off a single hard drive, the operating system and database files are all on that one drive. You realize you have to provide some fault tolerance…
Month: October 2011
70-450: SQL and RAID 5/10
Continuing SQL and RAID, let’s pick up RAID 5 and RAID 1+0 (or just 10) This content is still for the first skill measured in the 70-450, per the official Microsoft page for the 450: Designing a SQL Server Instance and a Database Solution (14 percent) Design for CPU, memory, and storage capacity requirements. This…
70-450: SQL, RAID 0, RAID1
Let’s get ready for the 70-450. Hit the official Microsoft page for the 450, and you’ll see the first skills measured on the exam: Designing a SQL Server Instance and a Database Solution (14 percent) Design for CPU, memory, and storage capacity requirements. This objective may include but is not limited to: RAID, calculating table…
SQL103 – Designing Triggers
We’ve finally made it to the last post in the SQL103 series. I’ve written posts about triggers before. I’ve shared with you how triggers can be good things and bad things. It’s all in how you design them. Today, I hope to teach you how you can design good triggers. Let’s dive right in! Understand…
SQL 103-Designing Stored Procedures
We’re nearing the end of the SQL103 series. We’ve designed tables, relationships, indexes and views. There’s plenty more to learn. Today we’re going to discuss designing stored procedures. When you start designing stored procedures you’re generally trying to build a wrapper around a collection of T-SQL statements that you can then hand off to developers….
SQL103 – Designing Indexes
So you’ve designed your tables, then you set up your primary and foreign keys. You even defined views that your programmers will use to present the data to end users. What’s next? Well, if you want to take a proactive approach to database design, you’re going to want to start thinking about indexing. Initial Indexes…
SQL103 – Designing Views
One of the next steps, after designing your tables is designing your views. You’ll often need to create them so that programmers will have access to the data in several tables, but you want to provide them an easier way to pull out the data. It’s a lot easier for them to use: SELECT *…
SQL103 – Prevent Dirty Data
Now that we’ve built relationships between our tables, we want to take the next step with our design is making sure the data stored in our tables is as clean as possible. The tool you’ll use for this insurance, is called a constraint. The good news is you’ve already learned one type of constraint.You’ve established…
SQL 103 – Relating Your Tables
Last time we were discussing how to build normalized tables. We designed 3 tables: Customer, Address and PhoneNumber. The Address and PhoneNumber tables are related to the Customer table, but how do we relate two tables? Primary Keys When we talk about relating one table to another, we’re really talking about relating a row…
SQL 103 – Normalized Table Design
So last time we were discussing the difference between normalized and de-normalized database design. We also discussed our case study, the CRM company. We decided to begin our database design by designing normalized tables to track customers and contacts with those customers. Let’s continue with that case today. We want to build tables to store…