We're implementing an application that has two tables that house user data. This data exists as part of our security database elsewhere on the network. The tentative plan is:
Create a view that mines all of the user demographic data we need in the new db. Publish this view with "view only" access. Subscribe to the security database with the new db to access this data.
Is it possible to then structure the published data to fit into application tables so that it appears seamless to the application? The application is proprietary and cannot be changed.
Thanks,
Create a view that mines all of the user demographic data we need in the new db. Publish this view with "view only" access. Subscribe to the security database with the new db to access this data.
Is it possible to then structure the published data to fit into application tables so that it appears seamless to the application? The application is proprietary and cannot be changed.
Thanks,