table design policy sql server

Question

0.00/5 (No votes)

See more:

SQL-Server-2008

hi all pro
i have a project for my university that is a small sale system
i have a table for Transaction and one for TransactionItems (Goods within that Transaction)
am i true???????????????????
what Tables and Relations Policy Do you Recommended to me?
please help me , thanks

Posted 31-Aug-12 18:13pm

daghune

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
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.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Accepted Answer · 2012-08-31T18:53:00

The tables and their relations depend on the requirements of your project.

However in your example most likely the transaction should have a primarey key, possibly a surrogate and the transactioitem would have a foreign key column referencing the transaction table. Also it most likely would make sense to define the foreign key to cascade delete operations on transaction table to the transactionitem table.