EV SQL DB maintenance error

There's nothing *to* resolve though, for the most part the SQL databases that EV use, whether its the Directory, Vault Store or Fingerprint, are normalized databases, with many indexes, primary keys, foreign keys, constraints, stored procedures, views, user defined types etc etc.

So where as you can say its a result of how the database is designed, I would agree with you except this is not a negative, for the databases to be as performant as they are, there really isn't any other choice.

Asking them to resolve an issue that quite clearly sits with SQL Server is like asking Symantec not to write indexes or DVS files that would cause fragmentation on the drive, its just not possible as its handled by Windows and the storage technology itself, and its the same way with SQL indexes becoming fragmented, its just part and parcel that goes with databases and their maintenance

If you actually Google the message that you are getting, you will find thousands of results, such as
http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/623d635e-94c7-4cdd-80f5-b46ab17cbbde

or
http://blog.sqlauthority.com/2007/08/17/sql-server-2005-explanation-and-script-for-online-index-operations-create-rebuild-drop/

I guess my point is that you can't take what is pretty much SQL 101 for a regular DBA and have EV support perform that function for you, because there are many instances where a good DBA can make sure that your databases are integral and performant, just as a SAN Admin can make sure you have the correct and performant storage solutions for your needs, or your networking team can make sure your network is optimized etc, none of those functions should be expected to be replaced by a vendors support.