Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
rajtechnocraft
Creator
Creator

is renaming of fields more time consuming then loading the original field

Dear Community,

My table contains close to 10 lakh records.

Just wanted to know if i renaming of  the fields in the table will consume  more time in data reload then reloading the table with original field names.

Regards

Raj

4 Replies
Miguel_Angel_Baeyens

Hello Raj,

Yes, it takes longer than using the original field names. However, sometimes is required, since your database names may not be helpful to the further development (I'm thinking of SAP).

I use to do all the necessary steps when loading from the data souce and store the results into QVD files (even Excel spreadsheets), then create another load from the QVD, that shouldn't require any additional work and the load will be fast. It's a two tier scenario but it allows you yo work faster based only in QVDs in the development time.

Hope that helps.

Miguel Angel Baeyens

BI Consultant

Comex Grupo Ibérica

rajtechnocraft
Creator
Creator
Author

thanks it helps.......

magavi_framsteg
Partner - Creator III
Partner - Creator III

I would not say renaming fields takes longer.

load a from myqvd.qvd

load a as b from myqvd.qvd

If you do not supply an alias for the field, it automatically gets the qualified column name as field name.

Behind the scenes it actually does like this:

load a as a from myqvd.qvd

But I agree with Miguel:

You should have atleast 2 tiers in your data model, and it is in the first tier the renaming of fields should take place.

Miguel_Angel_Baeyens

Hi,

I didn't mean keeping the optmized load from QVDs. If we are talking about that, then the QVD will load optimized even renaming and using one WHERE EXISTS() clause. Further than that, the optimization breaks and the load time will depend on the hardware, background running software, memory and so on.

And all the above obviously depends (and it could be viceversa) on the volume of data you are going to load. If performance is not critical because of the number of records, aggregations, joins and hardware, you probably don't find much difference one way than the other.

Hope that helps.

Miguel Angel Baeyens

BI Consultant

Comex Grupo Ibérica