c# - Benefits of switching from SQL Server to Versant OODB -

Profit to the company (if any) (not for developers only) I acquired SQL Server 2008 by switching Versant Can OODB?

More about the project and the fact with the answer (let me know that you need more):

• Very little team, almost never used OODB .
• The project uses NHibernate 2.
• About 75% of test coverage.
• ASP.NET MVC app.

  At this stage I can not justify the switch due to the following points (mostly not related to DB4O, related to mainstream OODB):

  • Tooling is much worse than RDBMS's world where "manager", professor, integration / migration tools and others;
  • Documentation is very important which I can see and mixed heavily with Java;
  • Not so much resources on the net compared to RDBMS on the net;
  • Switching to another database may be problematic (in opposition to RDBMS);
  • Learning curve for developers and IT
  • Additional licensing costs;
  • Additional maintenance costs;
  • Any integration with MSDeployment (including automatic backup, MSBuild, packaging, etc.);

    Here is a comment by a real user who switched from SQL Server 2005 into Versant

    About VOD.Net from me and my colleagues

    I shared my thoughts in professionals and opposition

    PROS: (in a word: speed)

    • The data engine is fast to read and write, which is 5 to 10 times that of what we did
    • It comes to the same thing compared to data Data Access Layer Technologies
    • It also reduces the amount of time it takes to develop new functionality
    • It creates a string of hard objects and the data
    • Data import is easy in VOD

      CONS: (In a word: Need for troubleshooting skis. Li>

      • Our main negative point is the administration tool usable (Administration Console and Object Inspector)
      • The buttons / links are not clear about the things we do when we try to use it
      • Worst Compliment / Database Update Errors are not clear enough, we know that class is the cause of error but this is not the reason, so we have to debug ourselves.
      • Using the verification database menu option could not work and show errors (depending on time)
      • Application migration
      • When a DAL pattern migrates application Is it doing so ??? If you try to keep the same code for the UI, then it is long to work with the VOD

        In RA ©, I VOD.Net for Senior Developers Skill Enterprises I recommend using. Compound / large data structure is making definite new applications faster than migrating existing applications. Object inspector needs a new format to become more user-friendly.

        We have addressed some light inspector concerns by providing LINQpad support. I think that you should decide to switch on the basis of technical advantage, not on any emotional discussion. Apart from this, Vestent is a Microsoft Partner, and there are many opportunities for OO Skills Versatile or good people.