Making SSAS Developer Edition act like standard edition

My understanding is that the Developer Edition of SQL/SSAS contain all of the functionality of the Enterprise Edition. Is there a way to force it to act as if it were Standard Edition (and therefore subject to all of the limitations of SE)

The reason I ask is that with our product we're trying to maintain compatibility with both SE and EE. I realize I can just install SE instead of DE, but if there's a way to simple toggle the behavior, that would be even better (especially since I already have DE installed. :)

Answer this question

Making SSAS Developer Edition act like standard edition

Lorenzo Minore
I asked around and we don't have a setting per server to downgrade the edition. You could install the standard edition as a named instance eventually (side-by-side with your current developer edition).

Adrian Dumitrascu.
Stacy
Ah, good tip, thanks. Unfortunately, that's not quite good enough for us, because we're doing programmatic manipulations of the cube definition using AMO. But it's good to know about, nonetheless.
AnObject
A partial answer:

If you have a BI project (that you open with Visual Studio to design and then deploy to AS2005), there is a project setting for specifying the Edition (right click on the project node, use 'Properties' and notice the edition setting at the top of the page). This will affect the validations to be done in the tools only (in Visual Studio for the BI project), the AS2005 server will do his own validations (based on its Developer Edition that you mention).

Adrian Dumitrascu.
Jeff Roediger
Well, it's nice to know definitively. Thanks for the info. Feel free to add that to the enhancement request list for the next version. ;)
Sean Aitken
Thanks Adrian. I would prefer to be able to just fix the server level, so I don't need to change the code to support this (once the product is deployed, these checks aren't really necessary). But in the absense of that capability, I can probably make do with the validation stuff.
liber
In this case, you can use the AMO's Validations. After you create or change a major object with AMO, before you call the .Update method, use the .Validate method, passing it explicitly the StandardEdition (otherwise it will use the engine's edition).

Sample code:

Cube myCube = ...;

ValidationErrorCollection errors = new ValidationErrorCollection();

myCube.Validate(errors, true, ServerEdition.Standard); // 'true' = include detailed errors, no problem to use 'false' for our scenario

if (errors.Count > 0)

{

// We either specified something invalid or we used features unsupported in the standard edition

foreach (ValidationError error in errors)

{

Console.WriteLine(error.FullErrorText);

}

}

Adrian.
Making SSAS Developer Edition act like standard edition

Answer this question