Introduction


A professor at MIT is quoted as saying, "Design is what you do when you don't [yet] know what you are doing."[1] This is very trueeven for application architects. It seems that so many of us depend on the wisdom of others to design their systems that we fail to learn the fundamentals of system design. As a result, the end product can scale, run efficiently, and be maintained for decades to comecome what may.

[1] George Stiny, Professor of Architecture, Massachusetts Institute of Technology, 21 June 2002.

IMHO

"Too many of the designs I see lack the solid foundations needed to have them last beyond the next strong wind."[2]

[2] William Vaughn, President of Beta V Corporation, 22 July 2006.


Before getting started on a tour of Visual Studio and SQL Server 2005, I feel a need to lay some groundwork. In my previous books[3], it was assumed that the reader had a firm understanding of how SQL Server works, knew how to write T-SQL, and knew how to build a normalized relational database. Since then, I've seen too many questions that could be simply answered by a better understanding of those fundamental tenants. To make it easier for you to understand why one architecture or technique is suggested over another, let's start by providing some foundational material that should help make your choice of architecture and how you build your applications easier. Of course, if you think that you're up to speed on all of these issues, feel free to skip on down.

[3] I've written at least 11 booksnot counting the volumes I wrote for Microsoft and other companies over the years.




Hitchhiker's Guide to Visual Studio and SQL Server(c) Best Practice Architectures and Examples
Hitchhikers Guide to Visual Studio and SQL Server: Best Practice Architectures and Examples, 7th Edition (Microsoft Windows Server System Series)
ISBN: 0321243625
EAN: 2147483647
Year: 2006
Pages: 227

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net