It’s all the same company. If they don’t have good checks for usability or quality control in one area, why should i assume they will be any better in a different area?

imagine if a car company like Toyota suddenly started to put out cars of lesser quality because one area lost focus on quality control and usability…

BTW, I’m not commenting from a position of authority (I don’t know the folks who made those decisions and I don’t work there). I was trying to help based on everything I learned about SQL Azure so far.

I’m also not asserting that it’s a good design. I’m just pointing out that the structure of the docs was used to draw conclusions about quality of patch testing which seems to be unrelated.

if a conscious decision was made to have those links included in order to show what is NOT supported, then that decision was wrong.

there is no way you can convince me that it makes sense to link to items you do NOT support, and then not link to something that you do support. that is the complete opposite behavior of anything i would describe as useful. i would rather think it was an oversight by someone as opposed to a strategic decision. if it was a decision then that person needs to be given the opportunity to participate in some usability seminars.

can you imagine if i showed my child pictures of four desserts they will NOT be eating after dinner? how silly would that be? and then, under my breath, i mention that we have some crackers for dessert but they have to climb up into the cupboard to get it themselves.

yeah, it’s like that. it makes no sense to have built the site in that manner. someone needs to think simpler, and from an end-user point of view when it comes to documentation.

Why? Because one of the main issues with migrating to SQL Azure is that it supports a subset of features compared to SQL Server. So the screen-shot above is intended to help evaluate migration rather than standard dev help.

What I’m saying here is that you should’ve draw conclusions on availability of dev docs and patching/testing policy based on this screenshot. Cheers!

I have faith in you, Buck.