Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2002-01-30 : 08:51:01
|
Carl writes "Here's the deal:1. Two tables - First table is "Contact". It contains contact info, likeContact_Name, Address, etc., etc, and also Password2. Second table is "Main". it contains "Make, Model, Size, etc., etc., andalso Password.All records in both tables are keyed to that Password. The entireoperation in both tables keys all identities, privileges, etc. to thatpassword.Each record contains a Password in the "Main" table. That Password,therefore, is duplicated many times in the Main table. There is only onerecord with that same Password in the "Contact" Table.Looks like I need some type or recursive search feature (search within asearch?) to accomplish my normalization. I want many records with the samepassword keyed to the one contact record with that same password.And here is the kicker. In the search I do not want the password to be apart of the apparent search criteria, but obviously it has to be keyed tothe "Contact" record, somehow, as in with that password. In other words, Iwant to search for a record in the Main Table, containing Make and Model,which also happens to contain a password, (but it's not shown to the user.)I want each instance of a found record to join theContact info from the Contact table. That Contact Table record containsthat same password as that instance of the Main table record. So, I needsome kind of search, which obtains the password from each record found andthen joins that found record with the Contact table entry, having that samepassword.That way each Main table record does not have to waste database space withContact info duplicated as many times as their are records in the Maintable.So, I am attempting to take each found record from the Main table search,and combine it with its related Contact table record. Password is neverpart of the user defined search, but each Main table record needs to beaware of its own Password, so it can join itself with the Contact tableinfo with the identical Password." |
|
|
|
|
|
|