Click here to Skip to main content

Christ_88 asked:

Open original thread
Hi everybody,
I have started to design a database and every time i rethink about it, i am finding that i can use a new table instead of a field, and enhance the program ability.
 
but at the end i find out that there are a lot of tables with a lot of relations,so it means a lot of queries to the database, but on the other hand it can make my software what i am looking for.
 
what is your idea? is it wrong to use a lot of relations in a database?
 
thank you for you answers.
Tags: C#, SQL, ASP.NET, ADO.NET, LINQ, entity

Preview



When answering a question please:
  1. Read the question carefully.
  2. Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
  3. If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Let's work to help developers, not make them feel stupid.
Please note that all posts will be submitted under the The Code Project Open License (CPOL).



Advertise | Privacy | Mobile
Web03 | 2.8.1411022.1 | Last Updated 26 Mar 2009
Copyright © CodeProject, 1999-2014
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100