Hi all, thanks for your feedback!
Goldie, could you please explain: - why I don´t need synonyms? - why I shouldn´t use views? - if i have sprocs in db1, with CRUD operations upon db2 tables how do i access them with Entity Framework code first? I've got my data model designed already. The reason why I'm using 2 databases (or more in the future) is because of data volume. It´s highly probable that I have to use distributed data servers to cater for good data accessibility from the customer end. Stephen, if I use views, how can I perform CRUD operations upon the tables referenced by the views, from Entity Framework code first? Thank you again! Have a great arvo! Dani On Wed, Mar 14, 2012 at 11:30 AM, Stephen Russell <[email protected]>wrote: > On Wed, Mar 14, 2012 at 6:17 AM, Goldie <[email protected]> wrote: > > A) Don't Use VIEWS pointing to other DBs. Use SProc's to return > Data-Sets > > that are joined from multi-databases. > -------------- > > I disagree. Views are great for just this situation. > > View rock for ORM environments as well. > > > > 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. > -------------------------------- > > Design is an easy thing to say but hard to do well. > > Design is the vehicle to determine if things work together. Does my > physical building structure fulfill what I need? Can users use the > device I just invented. Is my data accessible to my application and > others that might need it. > > You first identify the requirements that generate your first draft of > data repository structures. You next generate the data objects that > will be populated to contain that data. You now cross reference your > schema to validate everything is contained. > > Are you a third normal or a fourth normal data designer? Could your > developers ever figure out fourth normal? Does this get in the way of > reporting later on? > > So I still say design is not that easy. > > -- > Stephen Russell > > 901.246-0159 cell > > -- > 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 > -- 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
