T-SQL - Select with relationships

[realJSOP]

I have two tables with a relationship set on a given column (the related column names are the same in each table, and both tables have that column set as the primary key). Do I still have to do a join to get data from both tables, or does the configured relationship magically enable it? Here's what I have so far (I actually list the individual columns I want to retrieve, but for the sake of brevity, I'm using "SELECT *". Also, The ID column is the primary key and the column on which the tables are related.

SELECT *
FROM TableA a, TableB b
WHERE a.ID = b.ID

.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

[amer shammout]

i want to tell you that is the relationship ypu set is not relationship but it is a constraint but the where statment "WHERE a.ID = b.ID" make the relationship or join statment

[i j russell]

Yes you still have to do a join if you want data from both tables. A Foreign Key constraint is there to only allow non-null values that are in the parent column. The FK plays no part in the query; If you were to remove it, the query would still work just as well. By the way, your chosen style of joins is not considered to be good practice and may well be deprecated in future versions of Sql Server.

SELECT *
FROM TableA a
JOIN TableB b
ON b.ID = a.ID

The primary reason for this is that if you forget/remove the WHERE clause you have a CROSS JOIN. This can't happen with the suggested approach. Ian