ADO Data Access

ADO data access is the fastest cleanest and most supported technology when it comes down to database access. ADO data access comes with complexity and tedious coding and in conjunction with SQL it even becomes worse. Ignoring the fact that SQL is extremely powerful and considering the fact that developers like to use object related programming constructs, the concept of ORM (Object relational Mappings) has evolved in multiple flavors. ORMs attempted to replace the power of SQL by hiding it behind Object Query languages. Have they really achieved simplicity, ease of maintenance and performance gains? After using all of these technologies in multiple enterprise systems, we came to the conclusion that they definitely do not. Read more on why Orasis has developed Orasis Mapping Studio and how you can reduce the cost of building your data access tier.

The journey started from Java with Hibernate and continued in .Net with NHibernate, LinQ SQL and lately EF. All of these technologies use reflection to populate the model objects and most of them impose a one to one relationship between a class and the actual database table and others define “Entities” that are 100% bind to the framework. In addition to that, they use ado data access to get data in and out of the database. The complexity of these object query languages, the performance penalties in database operations as well as the huge limitations in maintaining the data access tier lead Orasis Software give a new approach to the creation and development of the database access tier that takes away the ADO.Net complexity and the SQL blues. Ado data access now makes sense. A visual toolset that integrates with Microsoft Visual Studio and allows custom crafting of your data access tier for only what you need and how you need it. Read more on the features of the product and watch demos on how easy and pleasant it has become to deal with building Ado data access code automatically.