While working on resolving the issue I recently posted about Optim corrupting NVARCHAR(MAX) data fields, I decided that we could possibly work around this issue in the short term by creating a View against the table with the NVARCHAR data and CAST that column as VARCHAR(MAX) since Optim handles VARCHAR fine. The plan was to use the View in the Access Definition.
My initial test worked when running just against the View in question....but once I add the View into the Access Definition with a dozen other tables I run into an issue of not being able to traverse the View. I know there is no way to create defined RI Constraints against a View...but it appears you can't create a logical Optim relationship against a view either. Optim only allows tables, not Views, in a relationship.
Which makes me question why views are allowed in an Access Definition at all (beyond being the start table) since they are bypassed without a relationship...
Anyone else out there run into this issue with Views and were you able to be creative and make it work?
Appreciate any insight on this one.
------------------------------
Keith Tidball
Progressive Insurance
------------------------------
#InfoSphereOptim#Optim