Hi
I have a system which Profiles people. However a new profiler has been written which is better, and all the old profiled members have to be moved to the new profiler tables.
I have a Members table with member data in it, it contains the old profile data in the table too, or at least the ID's per member.
In the new profiler things work slightly different.
I'll give an example:
Lets say MemberID 3241 is a smoker, SmokerID = 3 (Moderate Smoker)
And he drinks occasionally, AlcoholID = 2 (Light)
These ID fields are kept in the Members table which link to a table of their own i.e. memSmoking Table, or memAlcohol Table
The new profiler table works different. In the sense that the Alcohol and Smoking are all in the same table, but with different OptionID's and ValuesID's
Here is some sample code that i wrote. Just copy and paste, it will give you a base to work from. I'm trying my best to supply as much information as possible, so if i left anything out then please let me know? And thanks for the help in advance 
Code Snippet
--Sample Code:
--Members Table
DECLARE @.Members TABLE (MemberID INT IDENTITY(1,1),
ClientID INT,
Name VARCHAR(50),
Surname VARCHAR(50),
GenderID CHAR(1),
MaritalStatusID INT,
MemSmokingID INT,
MemAlcoholID INT)
INSERT INTO @.Members VALUES (211, 'Carel','Greaves', 'M', 2, 1, 3)
INSERT INTO @.Members VALUES (211, 'Jill', 'Jenkins', 'F', 1, 3, 4)
SELECT * FROM @.Members
--
--Profile Attrubutes
--
DECLARE @.memGender TABLE (GenderID CHAR(1), Description VARCHAR(50))
INSERT INTO @.memGender VALUES ('M', 'Male')
INSERT INTO @.memGender VALUES ('F', 'Female')
SELECT * FROM @.memGender
DECLARE @.memMaritalStatus TABLE (MaritalStatusID INT, Description VARCHAR(50))
INSERT INTO @.memMaritalStatus VALUES (1, 'Married')
INSERT INTO @.memMaritalStatus VALUES (2, 'Single')
INSERT INTO @.memMaritalStatus VALUES (3, 'Devorced')
INSERT INTO @.memMaritalStatus VALUES (4, 'Widowed')
SELECT * FROM @.memMaritalStatus
DECLARE @.memSmoke TABLE (MemSmokingID INT, Description VARCHAR(50))
INSERT INTO @.memSmoke VALUES (1, 'Nil')
INSERT INTO @.memSmoke VALUES (2, 'Light')
INSERT INTO @.memSmoke VALUES (3, 'Moderate')
INSERT INTO @.memSmoke VALUES (4, 'Heavy')
SELECT * FROM @.memSmoke
DECLARE @.memAlcohol TABLE (MemAlcoholID INT, Description VARCHAR(50))
INSERT INTO @.memAlcohol VALUES (1, 'Nil')
INSERT INTO @.memAlcohol VALUES (2, 'Light')
INSERT INTO @.memAlcohol VALUES (3, 'Moderate')
INSERT INTO @.memAlcohol VALUES (4, 'Heavy')
SELECT * FROM @.memAlcohol
--
--New Profile Attributes
--
DECLARE @.MemberOptionAtributes TABLE (ValuesID INT IDENTITY(1,1),
OptionID INT,
DisplayName VARCHAR(50))
INSERT INTO @.MemberOptionAtributes VALUES (2, 'Male')
INSERT INTO @.MemberOptionAtributes VALUES (2, 'Female')
INSERT INTO @.MemberOptionAtributes VALUES (3, 'Married')
INSERT INTO @.MemberOptionAtributes VALUES (3, 'Single')
INSERT INTO @.MemberOptionAtributes VALUES (3, 'Devorced')
INSERT INTO @.MemberOptionAtributes VALUES (3, 'Widowed')
INSERT INTO @.MemberOptionAtributes VALUES (4, 'Nil')
INSERT INTO @.MemberOptionAtributes VALUES (4, 'Light')
INSERT INTO @.MemberOptionAtributes VALUES (4, 'Moderate')
INSERT INTO @.MemberOptionAtributes VALUES (4, 'Heavy')
INSERT INTO @.MemberOptionAtributes VALUES (5, 'Nil')
INSERT INTO @.MemberOptionAtributes VALUES (5, 'Light')
INSERT INTO @.MemberOptionAtributes VALUES (5, 'Moderate')
INSERT INTO @.MemberOptionAtributes VALUES (5, 'Heavy')
SELECT * FROM @.MemberOptionAtributes
--MemberProfileLookupValues Table
DECLARE @.MemberProfileLookupValues TABLE (EntryID INT IDENTITY(1,1),
MemberID INT,
OptionID INT,
ValueID INT)
--This is how the data should be inserted, but i don't know how to do it in bulk for all the members in the members table (There are over 1000000)!
INSERT INTO @.MemberProfileLookupValues VALUES (1, 1, 1)
INSERT INTO @.MemberProfileLookupValues VALUES (1, 3, 5)
INSERT INTO @.MemberProfileLookupValues VALUES (1, 4, 7)
INSERT INTO @.MemberProfileLookupValues VALUES (1, 5, 13)
INSERT INTO @.MemberProfileLookupValues VALUES (2, 1, 2)
INSERT INTO @.MemberProfileLookupValues VALUES (2, 3, 3)
INSERT INTO @.MemberProfileLookupValues VALUES (2, 4, 9)
INSERT INTO @.MemberProfileLookupValues VALUES (2, 5, 14)
SELECT * FROM @.MemberProfileLookupValues
--Here is a piece of actual code that i tried that i thought would work but it inserted all the fields for all options for all members (WHOOPS!)
/*SET NOCOUNT ON
INSERT INTO _MemberProfileLookupValues (MemberID, OptionID, ValueID)
SELECT M.MemberID, '6', CASE M.MaritalStatusID WHEN 1 THEN '7'
WHEN 2 THEN '8'
WHEN 3 THEN '9'
WHEN 4 THEN '10'
END
FROM Members M
INNER JOIN _MemberProfileLookupValues ML ON M.MemberID = ML.MemberID
WHERE M.Active = 1
AND ML.OptionID <> 6
GO
*/
Carel:
What is the objective here; I am afraid I missed it.
|||Old Profiler uses these tables
@.Members
@.memSmoking
@.memAlcohol
@.memMaritalStatus
New Profiler uses these Tables
@.MemberOptionAtributes
@.MemberProfileLookupValues
So the memberID From the @.members table has to be inserted into the @.memberProfileLookupValues table, where the OptionID matched the type of attribute i.e. Smoking, Alcohol etc
Smoking = OptionID (4 in this case) i get the OptionID values from the @.MemberOptionAtributes table
Alcohol = OptionID (5 in this case) i also get the OptionID values from the @.MemberOptionAttributes table
When it comes to the memory tables i created, just look at the INSERT STATEMENT for the @.MemberProfileLookupValues table at the bottom and compare to the fields in the @.Members table.
OptionID's Come from the @.MemberOptionAtributes table. The valuesID's just have to be set to the right places.
for example:
If you look at the memSmoking Table
it has 4 ID's
1
2
3
4
In the @.MemberOptionAtributes table the OptionID for Smoking is 4
as far as the values are concerned for smoking in the MemberOptionAtributes table
@.memSmoking .memSmokingID(1) = @.MemberOptionAtributes .ValueID(7)
@.memSmoking .memSmokingID(2) = @.MemberOptionAtributes .ValueID(8)
@.memSmoking .memSmokingID(3) = @.MemberOptionAtributes .ValueID(9)
@.memSmoking .memSmokingID(4) = @.MemberOptionAtributes .ValueID(10)
I hope this helps, i'll keep trying to give as much info as possible.
Kind Regards
Carel Greaves
=== Edited by Carel Greaves @. 23 Jun 2007 9:32 PM UTC===
This was the porst that i posted yesterday, i sat thinking about the problem again today, and came up with something that might help me a little more, and maybe unconfuse the situation.
I want to insert all the generated memberID's in the members table into the @.MemberProfileLookupValues table with the AlcoholID's and MemSmokingID's
Hovever the New Profiler accepts the MemberID, OptionID, and ValuesID
Where the old way it was done was basically a pivotted way of doing it, i'm basically just un-pivvotting the table in the new table.
--Real Code that i actually used.
INSERT INTO _MemberProfileLookupValues (MemberID, OptionID, ValueID)
SELECT m.MemberID, '12', CASE MC.HealthInterestID
WHEN 1 THEN '71'
WHEN 2 THEN '72'
WHEN 3 THEN '73'
WHEN 4 THEN '74'
WHEN 5 THEN '75'
WHEN 6 THEN '76'
WHEN 7 THEN '77'
WHEN 8 THEN '78'
WHEN 9 THEN '79'
WHEN 10 THEN '80'
WHEN 11 THEN '81'
WHEN 12 THEN '82'
WHEN 13 THEN '83'
WHEN 14 THEN '84'
END
FROM Members m, _MemberProfileLookupValues ml, memHealthInterests mc
WHERE m.memberID = ml.MemberID
AND m.MemberID = mc.MemberID
AND m.Active = 1
AND ml.OptionID <> 12
GO
The problem that i had with this statement is that it Inserted the memberID with all of these field per memberID, instead of looking for where the values is = lets say 9 and insering the values 79 (According to the CASE)
This was the post is started two days ago, wouold someone please be able to help me out.
Just look at my @.Members table and the @.MemberProfileLookupValues
This was the porst that i posted yesterday, i sat thinking about the problem again today, and came up with something that might help me a little more, and maybe unconfuse the situation.
I want to insert all the generated memberID's in the members table into the @.MemberProfileLookupValues table with the AlcoholID's and MemSmokingID's
Hovever the New Profiler accepts the MemberID, OptionID, and ValuesID
Where the old way it was done was basically a pivotted way of doing it, i'm basically just un-pivvotting the table in the new table.
Code Snippet
--Real Code that i actually used.
INSERT INTO _MemberProfileLookupValues (MemberID, OptionID, ValueID)
SELECT m.MemberID, '12', CASE MC.HealthInterestID
WHEN 1 THEN '71'
WHEN 2 THEN '72'
WHEN 3 THEN '73'
WHEN 4 THEN '74'
WHEN 5 THEN '75'
WHEN 6 THEN '76'
WHEN 7 THEN '77'
WHEN 8 THEN '78'
WHEN 9 THEN '79'
WHEN 10 THEN '80'
WHEN 11 THEN '81'
WHEN 12 THEN '82'
WHEN 13 THEN '83'
WHEN 14 THEN '84'
END
FROM Members m, _MemberProfileLookupValues ml, memHealthInterests mc
WHERE m.memberID = ml.MemberID
AND m.MemberID = mc.MemberID
AND m.Active = 1
AND ml.OptionID <> 12
GO
The problem that i had with this statement is that it Inserted the memberID with all of these field per memberID, instead of looking for where the values is = lets say 9 and insering the values 79 (According to the CASE)
|||Carel,
I've been hoping (obviously, against hope) that you would see the mistakes inherrent in attempting to shove a EAV data model into a relationation data engine. Here, I'm going to allow someone else to attempt to explain it again. (From: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=61024&whichpage=2, Michael Jones:
I think that the query you posted is a perfect illustration of the biggest disadvantage of the Entity/Attribute model, that it saves a little work up front in data modeling by allowing “open ended” insertion of new attributes at the cost of having to program the true data structure into each query. Of course, there are other annoying little problems, like enforcing not null, DRI, domain integrity, default values, check constraints, creating useful indexes, transactional integrity, etc. Basically, it takes all the most useful features of a relational data model, and throws them away.
I have to revise my other non-PC comment: "Encoded in binary, then base64 encoded into text? That’s one of the stupidest thing I've ever seen, but it looks like a stoke of genius compared to using an Entity/Attribute data model!!! What brain-dead morons came up with that!? I know it had to be a committee, because no one could be that stupid all on their own!"
The 'Original Members' table is the 'best' way to store this data. Both attempts of using some form of EAV is a bastardization of the relational database, and will always cause you more grief than it is worth. The task at hand is but one more example.
Using the code you provided (and thank you for the DDL and sample data!!!), it seems that you may be over-complicating the process. I think that it will work for you like this:
Code Snippet
INSERT INTO @.MemberProfileLookupValues( MemberID,
OptionID,
ValueID
)
SELECT
m.MemberID,
'6',
CASE m.MaritalStatusID
WHEN 1 THEN '7'
WHEN 2 THEN '8'
WHEN 3 THEN '9'
WHEN 4 THEN '10'
ELSE NULL
END
FROM @.Members m
EntryID MemberID OptionID ValueID
-- -- -- --
1 1 6 8
2 2 6 7
Please do yourself a favor and do some research on the issues, problems, and pitfalls related to EAV data and relational databases.
(There are EAV databases available -I don't know how they evaluate...)
|||Hi Arnie
Thanks for the help with that thread. I read what went on there and i agree with what the guys are talking about. Unfortunately i have been given the task of converting from the old model (Which is right) to the new model i.e. (EAV).
I don't have much say in the matter as the company outsourced the EAV system which was created and actually paid money for it.
When i ran my query to insert the memberID's into the EAV model then it would run through the whole case statement and insert each value per member. for example.
Instead of looking for where the value is 1 and then assigning it value 7.
It would insert values (7, 8, 9, and 10) per memberID for all memberID's. That was my problem. (And it would do it Multiple Times)
Maybe something is wrong, but it looks right to me and it makes sense. (i'm not too concerned about the type of model at present moment) i just want the data to go into the tables right.
Code Snippet
--INSERT memSmokingID Data of Members from Members Table
SET NOCOUNT ON
INSERTINTO _MemberProfileLookupValues (MemberID, OptionID, ValueID)
SELECT m.MemberID,'9',CASE M.MemSmokingID
WHEN 1 THEN'59'
WHEN 2 THEN'60'
WHEN 3 THEN'61'
WHEN 4 THEN'62'
END
FROM Members M
INNERJOIN _MemberProfileLookupValues ML ON M.MemberID = ML.MemberID
WHERE M.Active = 1
AND ml.OptionID <> 9
GO
|||Why do you JOIN to [_MemberProfileLookupValues]?
That JOIN produces a row in the resultset for each row in [_MemberProfileLookupValues] -and I think that you only want one row per [Members] row.
Unless I don't have a complete picture of the data, you would be better off, as in my previous example, leaving the JOIN and WHERE clause out of the query. (I suspose you could still have the [m.Active = 1] filter though...)
|||As i said in my previous post, stupidity resides EVERYWHERE 
Thanks Arnie (AGAIN!!!) he he
makes sense now to me why it would keep on inserting more and more duplicates.
