SQL Server relationships (Access 2003 SP3)

[patt]

After developing a database in SQL and creating 4 tables, i now want to draw the relationship lines between them. I presume i need them to set referential integrity as in Access.

I have struggled with this for quite a while last night.

I bet it's easy, but darned if i can see how to.

[HansV]

It's done by creating restraints on a foreign key. See for example Defining cascading referential integrity constraints in SQL Server.

[MarkLiquorman]

Open the SQL Server Management Studio, and click down to your database. Underneath that is a choice of "Database Diagrams". This works much like the Access diagrams, but has several advantages. Primary among these is that you can create multiple diagrams, so you don't have to define all your relationships in one big diagram (as you do with Access). Of course, with only 4 tables, this isn't much of an advantage.

[patt]

Do you just drag the mouse between like fields in the different tables, i couldn't do this.

[patt]

Thanks Hans, i will check this out.

[MarkLiquorman]

You have to click on the grey box next to a field and then drag it.

[patt]

Thanks Mark, that is fine.

However it comes up with Yes to Enforse for Replication. Do I need to set this to No?

[patt]

Can you tell me Hans what OBJECT_ID is in that sample you posted for me?

Is it a passed in parameter? Is that a Stored Procedure?

[MarkLiquorman]

That's correct, set this to No.

[HansV]

I don't have the slightest idea, sorry.

[gdrezek]

Hi Pat,
T-SQL (Transact SQL) definition: OBJECT_ID
It is a unique id number for an object in a database. This blog has a nice explanation of it.
Checking to see if the OBJECT_ID is > 0 is one way to query the existence of that table in the code Hans referenced.

[patt]

Thanks Gary, nice explanation in that blog. The other 2 references (T-SQL and OBJECT_ID) give valuable explanations as well.

I will read and reread that blog.