Logical Design is not a lost art, after-all

A couple of days ago, a team member came to me and asked whether they could help me with anything SQL Server related. After a discussion, she showed a real interest in learning SQL Server in far greater detail. I was really excited by this. I wanted to start off by having her design a basic Customer / Sales schema – This would be our basis for covering just about everything related to SQL Server.

The reason I started to kick off with a schema design was so she had something she knew well (she’d design and develop it, afterall) to work from. Once we had a schema in place, we could start working through the concepts of keys, constraints, indexes etc and then move in to loading dummy data, performance tuning and so on.

Today, I have the biggest smile on my face because she presented me with a logical model for her design. I was caught off guard and super excited. You see, I never asked for a logical model. I just gave her some requirements for the schema and said that when your complete, we’ll review it. The fact that she has taken time to review the requirements and put a logical model in place is just awesome. So many people jump straight in to the physical model.

Now, I have not yet reviewed the logical model. I want to see the logical and physical model together and then probe on the various decisions she has made.

She has always been a star ETL developer for me but I am blown away by this. I’m seriously impressed (if you hadn’t guessed).

Leave a Reply