Using Arc 10.3.1 in a versioned environment, I am trying to build a model that will join two tables, then create a definition query to only show records that differ in one attribute field between the two joined tables (The field is called request_status) If the records differ between the two, then it will copy over the request_status from on fc to the other fc.
In the model I tried to do the join and then select by attributes, but this wants to create a new fc (which i dont want to do) So my idea was to create the join in a copy of my FC in the table of contents, and then have the model load the pre-joined table and calculate the fields as normal to move over the request_status.
On a side note, I think its best to use the definition query to limit my fc down a bit, otherwise I am doing a field calculate on over 100,000 records, and the time to do this is prohibitive.
My question was is it bad practice to leave these two feature classes permanently joined? Will it cause performance issues, or database issues with the sde?
أكثر...
In the model I tried to do the join and then select by attributes, but this wants to create a new fc (which i dont want to do) So my idea was to create the join in a copy of my FC in the table of contents, and then have the model load the pre-joined table and calculate the fields as normal to move over the request_status.
On a side note, I think its best to use the definition query to limit my fc down a bit, otherwise I am doing a field calculate on over 100,000 records, and the time to do this is prohibitive.
My question was is it bad practice to leave these two feature classes permanently joined? Will it cause performance issues, or database issues with the sde?
أكثر...