"failed with the following error: "Online index operations can only be performed in Enterprise edition of SQL Server.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly."
Or, perhaps, the failure reason is that the SQL Server in question is Standard Edition, and that's pretty much it?
Other suggestions here (if you're not in Standard Edition!).
It would be nice, though, if SQL were clever enough to know when it's running Standard Edition, and not give you the option of an Online Index Operation when you're building the maintenance plan, now wouldn't it?! Or is that a Moon-on-a-Stick request?
Subscribe to:
Post Comments (Atom)
use SERVERPROPERTY in your T-SQL
ReplyDeleteDear Anonymous
ReplyDeleteValid point, but I was creating a Maintenance Plan in the Wizard, not writing SQL. Of course, if I were creating an indexing script to be applied across several servers, then that would be a good idea.
SELECT ServerProperty('engineedition') is presumably what you're thinking of?
Ta muchly