Re: novice runs into incomprehesnible (to him) error message

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

thanks to both repliers...i checked the dsv and the datatype for customer id
is system.int32 in each table. i also checked and customerID is the key in
the case table....i know i made a mistake here since other readers got thru
this - it's just tough finding it.
thanks,
--
jim


"Jamie MacLennan (MS)" wrote:

> I think the key is that the Customer Id column from the Actors table is
> connected to the wrong column in the Customers table as indicated by the
> error specifying the "Home Ownership" would be the case key. Maybe you have
> marked Home Ownership as the key to the case table?
>
> --
>
> -Jamie MacLennan
> SQL Server Data Mining
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Raman Iyer [MS]" <ramaniy@xxxxxxxxxxxxxxxxxxxx> wrote in message
> news:ORyvec67FHA.3048@xxxxxxxxxxxxxxxxxxxxxxx
> > When you add a nested table to a mining structure, there's an implicit
> > join relationship from the nested table to the case table. For instance,
> > if you are modeling customers and their purchases, the case key would be
> > [Customer Id] and it would be bound to a "Customer Id" column in the
> > source Customers table from the DataSourceView (DSV). The source for the
> > "Purchases" nested table would be a transaction table, say
> > "CustomerPurchases", that contains multiple product rows for each
> > customer in the Customers table. The CustomerPurchases table should have a
> > foreign key called "CustomerId" that joins the table to the Customers
> > table. This column does not show up in the mining structure's nested table
> > but it's specified in the "ForeignKeyColumns" collection in the nested
> > table column's properties.
> >
> > The error you're seeing is due to the fact that the server requires the
> > source columns for the nested table's ForeignKeyColumn(s) and the case
> > table's Key column (accessible via its Properties ->General->KeyColumns)
> > to have matching data types.
> >
> > You can edit the ForeignKeyColumn(s) by right-clicking on the nested table
> > in the Mining Structure editor, selecting Properties and clicking on the
> > "..." button for ForeignKeyColumns in the Misc section.
> >
> > You should verify that you selected the correct column when you created
> > the relationships for CustomerId in the MovieClick Data Source View. This
> > is likely the source of the problem.
> >
> > --
> > -Raman Iyer
> > SQL Server Data Mining
> > [This posting is provided "AS IS" with no warranties, and confers no
> > rights.]
> >
> > "jimwill3" <jimwill3@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:27B4E3BE-6117-49A1-888B-36C63B3C7EF3@xxxxxxxxxxxxxxxx
> >> working thru the sql server 2005 datamining book - in chapter 3 trying to
> >> build the mining model for movie click i get the following:
> >> Error 1 Error (Data mining): The data type of a foreign key binding
> >> (ordinal=1) for the 'Actors' nested table does not match the data type of
> >> the
> >> corresponding key binding for the 'Home Ownership' case key of the
> >> 'MovieClickStruct' mining structure. 0 0
> >>
> >>
> >> as i am very new to this i'm having a hard time figuring out what it
> >> means
> >> and how i messed up the process along the way.
> >> thanks,
> >> --
> >> jim
> >
> >
>
>
>
.

Quantcast