Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
in our extraction app, we are connecting to some X database to get the customer details, now due to some restrictions from higher management we are not allowed to use that X database, so they are trying to find the replacement tables in a new database called Y.
and above Qvds with customer details are used in many Qlik apps.now we have to change our extractor script by pointing everything to new database Y...
Based on my imgination/assumption this change is going to invite lot of new issues if we are not very careful in this transition...
Any one you faced this kind of situation...??? please with your expertize suggest the things i have to do/plan to avoid problems later...??
Thanks much in advance....
If Y is just a dump of X you need only to change the database-name in your connection-statements. Are these statements centralized in some include-variables this change will be quite easy and fast - if not you will need to change it in each script.
Are there bigger differences - other tables/fields/formattings/data - you have a big problem and it will need a lot of efforts to change/adapt everything and it might be even more sensible to develop everything new from the scratch ...
- Marcus
Thank you very much Marcus,
Hoping that it will be mostly a dump, am expecting that the field names may variey for some tables. so can we please summarize some points where we have to be very careful by considering the situation as : few field names in some tables are changed from X to Y..
1. renaming the new field names to old field names will save us lot of rework.
2. checking the field name base functions used in the backend like substring,left ,right etc...
Please put your points here by taking the above seanario... Thanks Again.