SQL Server Table relatioinship, and Best way to store data question!

Question

0.00/5 (No votes)

See more:

I am kind of new to SQL Server. I am a CS student so I need helps! (don't have school right now, self learning)

I am wondering if there is a way to have a list of tables(List name) and each of those list names has a list of messages(strings)?

or is there a type of way I could store this data so it can be retained each time I changed it? I was thinking of having it retained through an SQL server. But I am not sure how I could store it.

This is the thing i'll be messing with.
List<LinkData>

class LinkData{
public string listName;
public LinkedList<string> messages;
}

Posted 7-Jul-11 5:19am

Member 8015046

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)

dasblinkenlight · Accepted Answer · 2011-07-07T05:46:00

Solution 1

In RDBMS, this is modeled as two tables with a one-to-many relationship: table M with messages has a foreign key to the table N, with list names:

SQL

create table N (
    id bigint identity primary key
,   listName varchar(max)
)

create table M (
    id bigint identity primary key
,   n_id bigint not null references N(id)
,   message varchar(max)
)

Be prepared that RDBMS is a big paradigm shift from what you've seen in "imperative" programming with traditional algorithms and data structures. Don't worry, it will all make sense in time as you work your way through a few dozen examples.

Good luck!

Posted 7-Jul-11 5:46am

dasblinkenlight

Comments

Member 8015046 7-Jul-11 12:00pm

Hahaha I don't understand that. I am using Microsoft SQL management studio. I have made two tables. One with one column that has listName, and another table with one column that has messages. Is there anything I need to change? And how do I make them related? I am messing with database diagrams right now.

fjdiewornncalwe 7-Jul-11 12:43pm

Your initial table requires a unique id that can then be used in a column in the child table as a foreign key. The example above shows what the table layouts should be.

dasblinkenlight 7-Jul-11 12:18pm

> Hahaha I don't understand that.
You need some theoretical background then - first few chapters of any book on RDBMS would greatly improve your understanding.
> Is there anything I need to change?
Yes, you need to add id columns to both tables, and a foreign key to the table with messages. Adding a foreign key makes tables related. You can copy-paste the declarations from the answer into a query in SQL management studio, and look at the resulting diagram for tables N and M.

Member 8015046 7-Jul-11 14:08pm

So if I wanted to add information. Do I add the listName in Table N, then go to table M and have the n_id = listName's id, then put the message?

dasblinkenlight 7-Jul-11 14:14pm

Correct, that's how you do insertions. Deletions are generally done in reverse order, although you could also use a cascading delete.