Jason and Koen have pointed out the flaws in this question.
I wonder how many people will end up answering (correctly) "developer edition" and finding out that that answer is treated as wrong.
But there's another flaw - this one in the SQL Server product (we have a non-optional option, which is surely a flaw) not in the question:-
Maybe there should be a none of the above answer; the question doesn't state what release it is about, so it should be assumed to be about 2008, 2008 R2, or 2012 (the ones currently fully released and on standard support); according to Jason none of those supports vardecimal, and if that's correct clearly no edition of any of them does. But looking at database properties using SSMS for sql 2012 or ssms 2008 R2 in developer edition provides a list which says the vardecimal storage option is enabled - I don't currently have a 2008 system to try it on, but I imagine it's the same - and that line is in weak type, which I think means you can't change it, so maybe Jason is wrong - the thing that isn't supported is disabling the feature, the feature itself is supported, so a "none of the above" answer isn't needed. Of course the idea that something which can't be switched off is listed as an option raises an interesting question: if you can't switch it off, it isn't optional so why say it's an option? The ways of Microsoft are indeed arcane. :w00t: And this isn't just a funny thing in SSMS: I can use
sp_tableoption '<table>', 'vardecimal storage format' 1 (or 0)
to tell the system whether an individual table is allowed to use the format, and
select name, object_id from sys.objects where objectproperty(object_id, N'TableHasVarDecimalStorageFormat') = 1
will then list or not list the table depending whether I set the property to 1 or to 0, so something really is going on there, it's not just SSMS being silly.