Julien, Christine2010-08-262010-08-262017-05-112010-08-262010-08-262017-05-112009-12December 2http://hdl.handle.net/2152/ETD-UT-2009-12-540textNearly all modern software applications, from the simplest website user account system to the most complex, enterprise-level, completely-integrated infrastructure, utilize some sort of backend data storage and business logic that interacts with the backend. The ubiquitous nature of this backend/business dichotomy makes sense as the need to both store and manipulate data can be traced as far back as the Turing Machine in Computer Science. The most commonly used technologies for these two aspects are Relational Database Management Systems (RDBMS) for backend and Object-Oriented Programming (OOP) for business logic. However, these two methodologies are not immediately compatible and the inherent differences between data represented in RDBMS and data represented in OOP are not trivial. Taking a .NET developer’s perspective, this report aims to explore the RDBMS/OO dichotomy and its inherent issues. Schema management theory and algebra are discussed to gain better perspective of the domain and a survey of existing solutions for the .NET environment is explored. Additionally, methods outside the mainstream are discussed. The advantages and disadvantages of each are weighed and presented to the reader to help aid in design implementations in the future.application/pdfengSoftware developmentImpedance mismatchRDBMSORMODBMS.NETWhat can the .NET RDBMS developer do? A brief survey of impedance mismatch solutions for the .NET developerthesis2010-08-26