Concatenate Address Columns in Database vs. Keeping Them Separate

We have a client that has created a SQL view to use for the Vendor lookup in FCi. The view has taken 3 address fields from their ERP and concatenated them into one. 1 of the address fields contains the actual vendor address, but the others can contain DBA information (not addresses). Would they get better matching results by separating them out to three columns and telling the lookups to use all 3 as address fields or keep it as one?




Please sign in to leave a comment.