A) Don't Use VIEWS pointing to other DBs. Use SProc's to return Data-Sets that are joined from multi-databases.
B) No need to do this. Suggestions: - Design your database - Design the back-end of your application - Design the front-end of your application. Never start in reverse, cause then your database will, almost assuredly, be unsupportable. On Monday, March 12, 2012 2:50:08 PM UTC-5, Dani wrote: > > Hi all! > I´m writing a web interface in MVC3 with 2 backend databases, one server, > same provider SQL Server 2008 R2. > > I´ve made a little research on this and found 2 possibilities: > a)- Creating a view in DB 1 pointing to DB2. data model is generated > from there. This solution would be applicable to DataBase First approach. > > b)- in DB1 creating a synonym to reference DB2 and modifying the > entityTypeConfiguration mapping to point to the synonym. This option is > suitable for Code First approach. > > as i'm opting for Code First approach, option b would do. > > But now, > 1) what about performance? am i going to have any performance issues when > fetching large amout of data from any of the databases? > 2) And this question is about Code First approach: what happens when > upgrading/updating my application on client´ site, is the database created > again from scratch? > > please help! > > many many thanks in advance! > have a great arvo! > Daniela. > > -- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
