http://blogs.msdn.com/nickmalik/archive/2006/10/25/soa-and-database-coupling.aspxWhat do you do if two enterprise services share the same database? I am running into this all the time. As we work to break apart legacy applications, we need to recognize that 'stovepipe' applications are written from the perspective of 'put everythingen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/nickmalik/archive/2006/10/25/soa-and-database-coupling.aspx#1193297Sat, 02 Dec 2006 16:26:26 GMT91d46819-8472-40ad-a661-2c78acb4018c:1193297Keith<p>So if I have a normalized database does it make sense to break it up into several logical sections as there own DB? &nbsp;An application DB for loan applications? &nbsp;A customer DB for customers? &nbsp;We do not have a CRM system. &nbsp;When we process loans create a processing DB? &nbsp;Then we wrap all interface interaction with web services? &nbsp;In discussion, I believe people have interpreted this to mean break up or normalized DB for the sake of SOA</p>http://blogs.msdn.com/nickmalik/archive/2006/10/25/soa-and-database-coupling.aspx#5114132Tue, 25 Sep 2007 10:06:21 GMT91d46819-8472-40ad-a661-2c78acb4018c:5114132Sam Gentile<p>I am still reeling from seeing the Red Hot Chili Peppers with Mars Volta 2 nights ago in Philly at the</p>