On Wed, Mar 14, 2012 at 6:17 AM, Goldie <john.w...@woodsoft.us> 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 dotnetdevelopment@googlegroups.com To unsubscribe from this group, send email to dotnetdevelopment+unsubscr...@googlegroups.com 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
