Group items tagged

"ORM users have grown accustomed to thinking in terms of .NET and LINQ, forgetting the specifics of particular databases, differences in their functionality and effectiveness of certain SQL-constructions. In this article, we shall briefly discuss some of the problems that the user may face in the process of developing an application for Entity Framework (EF), which is meant to interact with Oracle, MySQL, PostgreSQL or SQLite rather than Microsoft SQL Server. I hope this will be useful both for users who create an EF-application for these databases for the first time as well as for those who create an application that must support interaction with multiple databases, i.e., SQL Server and Oracle. As examples of implementing EF-providers for databases other than SQL Server, we shall use Devart ADO.NET providers."

"Bad data always seems to appear when, and where, one least expects it. Sam explains the great value of a defensive approach based on constraints to any team that is developing an application in which the data has to be exactly right, and where bad data could cause consequential severe financial damage. It is perhaps better seen as creating a test-driven database"

"SafePeak is a plug-and-play Dynamic Database Caching Solution, designed to improve data access performance for Applications built on SQL Server. It offloads the read queries and stored procedures which perform "Select" by dynamically caching in-memory result sets, thereby reducing read response time and overall database load."

"Summary: In this paper we'll look at the new Entity Framework 4 that ships with .NET Framework 4 and Visual Studio 2010. I'll discuss how you can approach it's usage from a model-first perspective with the premise that you can drive database design from a model and build both your database as well as your data access layer declaratively from this model. The model contains the description of your data represented as entities and relationships providing a powerful approach to working with ADO.NET, creating a separation of concerns through an abstraction between a model definition and its implementation."

"This is octalforty Wizardby, a powerful yet easy to use database continuous integration & schema migration framework primarily targeting .NET. The latest release is Alpha 3. "

"Datomic is a new database designed as a composition of simple services. It strives to strike a balance between the capabilities of the traditional RDBMS and the elastic scalability of the new generation of redundant distributed storage systems."

"Gabriel Schenker's excellent series of posts on "How we got rid of the database" offers a great insight on the benefits of a CQRS/ES application. One of the problems often seen with designing user interfaces that introduce eventual consistency into the mix is how to present this new paradigm to the end user. But whether we've thought or not, eventual consistency is all around us, as Gabriel points out in a few examples:"

"PetaPoco is a tiny, fast, single-file micro-ORM for .NET and Mono. Like Massive it's a single file that you easily add to any project Unlike Massive it works with strongly typed POCO's Like Massive, it now also supports dynamic Expandos too - read more Like ActiveRecord, it supports a close relationship between object and database table Like SubSonic, it supports generation of poco classes with T4 templates Like Dapper, it's fast because it uses dynamic method generation (MSIL) to assign column values to properties"

"When building larger scale applications, message queues are often very helpful for both distributing and aggregating workloads. Distributed workloads are a natural fit for message queues, simply having multiple readers attached to the same queue is often enough. Aggregation, usually implemented with one reader and multiple writers, is used to bundle lots of small updates into a large block. This facilitates the use of advanced database techniques such as the use bulk inserts instead of individual insert/update statements."

"There is a popular design for a database that requires a built-in audit-trail of amendments and additions, where data is never deleted, but merely superseded by a later version. Whilst this is conceptually simple, it has always made for complicated SQL for reporting the latest version of data. Alex joins the debate on the best way of doing this with an example using an indexed view and the filtered index."

"Based on DbDeploy, the popular Java version, DbDeploy.Net 2 is written using modern .net technologies and provides support for MsBuild and command line execution."

"If you keep your data according to its version number, but need to work only with a particular version, what is the best SQL for the job? Which one works best? Which one do you use and when?"

"vFabric SQLFire is a memory-oriented, shared-nothing distributed data management system designed for applications that demand high speed, scalability and availability."