1

I was wondering performance wise does creation and call to a table it self costs any performance?

I have a small table which will have about six columns and two rows. Problem is that from architectural point of view the table is in officiant there should be three tables with from two to three columns related via keys.

My dilemma is correct architecture vs performance but I have no actual understanding of performance the right architecture would take up.

P.S. The data from database will be retrieved only once.

asked Oct 17, 2012 at 9:52

1 Answer 1

2

I would go with design over performance in this case. You will have more trouble if somehow your database scheme grows when you just have performance in your mind. Also I don't think that there will be any noticeable performance difference between your approaches.

Remember: Good design is better for maintainability.

answered Oct 17, 2012 at 9:56
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

Draft saved
Draft discarded

Sign up or log in

Sign up using Google
Sign up using Email and Password

Post as a guest

Required, but never shown

Post as a guest

Required, but never shown

By clicking "Post Your Answer", you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.