Working up a data model for a new systems architecture – been spending the last few months working in MS Word, whiteboards and sticky notes. Feel like we’ve hit diminishing returns by looking at this in the abstract, so I figured I’d hack up an instance in MS SQL to see how much of this thinking stands up to reality.
I tracked down a few online resources to get me back into SQL (it’s been nearly a decade since I dug in deep) – two of note were:
- How to Install SQL Server 2012 Management Studio Express on Win7 and Create a local SQL database
- DBA community on StackExchange
After a day or so messing around with this, my valued conspirator Dale Cox mentioned Entity Framework to me:
And thus was the Bright Light of Truth shone upon my works. For a guy like me who’s working out the business needs, transforming into Stories, and usually has a lot more to say about UX than about MVVM constructs or SQL queries, this is the perfect level for me to dig into next. Entity Framework, Model First, using Visual Studio 2013? I still wouldn’t pay thousands of $$$ for this tool, but here’s one way that it stays relevant for me.