SQL Server change

[Big Chief Sitting Duck]

We're on OneWorld XE (upd6) sp23. If that matters ( I'm new to all this ) Here's the question. If I set the IMITM column on OWDTA.F4101 i.e. the Item Master, to be a primary Key in *SQL Server*, will this break anything?

Cheers

 

[eydeak]

I don't really know much about SQL Server as a back end, but here are
some general comments.



As defined in base JDE, IMITM is already the primary key for F4101. I
would expect it to show up as the primary key in the back end database.
(It does on DB2) I would be extremely wary of messing with a table's
primary key outside of the JDE tools.



In general, we try to handle all of the table definition within Table
Design Aid (TDA) in JDE. Primarily, if you generate the table from
within TDA or generate the table indexes within JDE, it can wipe out
indexes defined outside of JDE. Also, if an index is defined outside of
the JDE tool, you can't reference it directly within JDE.



I am only a developer. Hopefully you can get more technical detail from
a DBA lurking out there.



Ellen Deak

Senior Systems Developer

Cooper Standard Automotive

JDE EnterpriseOne (OneWorld XE Update 7 SP23_M1), AS400 DB2 V5R3M0,
Citrix Clients

 

[GSI Inc.]

Re: RE: SQL Server change

The SQL server will already have the correct definition at the "back end". Again I would not mess with a tables keys especially a table that is used in countless UBE's, BSVW's, Forms etc. Ouch what a mess that could make. It is already setup the way you wish. It already has an index for each item number, itm, litm and aitm. - Angelis

 

[Big Chief Sitting Duck]

Re: RE: SQL Server change

Interestingly, although the IMITM column is defined as a primary key in the Table Design Aid, unlike many other JDE tables the IMITM column hasn't actually had the PRIMARY KEY constraint added in SQL Server. Now, since the idea of a primary key is so fundamental to relational database design I cannot imagine the JDE validation of this key is in any way different to the SQL Server validation.

So we've physically added it to the SQL Server table def in our prototype environment and will let you know if this causes any issues. I can't imagine that it would.

We have