CoetzeeW (4/2/2009)
If any one that think's SQL is less complex then Oracle or DB2 then I would assume you have excessive knowledge in these products to make such a decision. Then if one says that SQL server is not complex then take a minute and dwelve into the SQL server architecture..let's say memory Architecture ..you will be suprised that there are many complex components involved in the SQL server memory arhictecture and then on top of that try mapping those components back to Windows memory architecture ...wow seems simple enought...:hehe:But let's not focus on comments about complexity and focus on the article that was written and the way of thinking that must sometimes change to fix a problem in 10min or spend 1 hour....
I apologize for my reply about the complexity comments. I didn't convey what I was thinking properly. I completely agree SQL Server is complex inside. It has a simpler user interface (from my experience with the other platforms) but it by no means is a simple product 🙂 Teams of great developers have spent countless hours developing the various versions and it's architecture is complex. Thanks for the reply about that, you said it much better than I did 🙂
As for the second part of your comment, are you saying a methodology would reduce time to 10 minutes or drag it out to 1 hour? I am hoping that it saves time, most of those steps and principles aren't lengthy and they only increase time by a little. In the ambulance call example, if we were to rush through, miss a couple steps we could have maybe saved a couple or few minutes but the outcome wouldn't have been better and could have been worse.
__________________________________________________
Mike Walsh
SQL Server DBA
Blog - www.straightpathsql.com/blog |Twitter