WPI was a major reason SQL Server Express destroyed my boot partition: I'd never used WPI before, really didn't intend to be using anything like it, and, thus,

WPI was a major reason SQL Server Express destroyed my boot partition: I'd never used WPI before, really didn't intend to be using anything like it, and, thus, didn't know WTF it was doing -- your documentation is about the first I've seen. So, not knowing WTF WPI was doing, I ended up with two different versions of SQL Server installed, something I would NEVER want to have. Such multiple installed instances are NOT independent and, thus, get terribly confused. Then just to get started, I ran some really simple T-SQL scripts about logons, users, and permissions. Soon SQL Server got sick and wouldn't query, uninstall, repair, reinstall, or install, and for SQL Server the usual Windows System Restore wouldn't. Apparently Microsoft has something over 10,000 reports of SQL Server getting sick and then refusing to uninstall. Then the only solution is to reinstall all the software on the boot partition. Net, such nonsense cost me MONTHS last year. Pissed? No, I'm not pissed. Long ago I was WAY passed just pissed, and I'm MUCH more than pissed now. WebMatrix won't solve such problems but claims to solve problems I don't have: Visual Basic .NET, ASP.NET, ADO.NET, .NET, and T-SQL have all been fast, fun, and easy to use. There is NO reason for me struggle with at best poorly documented GUI nonsense and another layer of garbage to cause problems and keep me from knowing what is going on. WebMatrix looks like an unanesthetized root canal procedure, and I won't submit to it. For progress, Microsoft needs to take all their documentation, throw it out, all of it, and start over. I mean this quite literally and very seriously. Then they need to fix SQL Server, e.g., the fact that it won't uninstall, and especially fix the new security model first in the 2005 version which is badly broken and which apparently so far no one inside Microsoft or outside understands -- literally. As it stands, from the information readily available, it appears that no serious computing should have anything at all to do with SQL Server. Ease of use of SQL Server administration and management is less credible than virginity in a dirt cheap whore house.