Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
Have a situation where I have two datasources both pointing to the same sharepoint online site; one name is in camel case and the other is all lower case.
At first thought that one should be removed for sanity sake and hopefully some performance improvement too. Unfortunately I can not test as the Delete button is greyed out. No doubt permissions.
Next I tried changing one name to be the other and visa versa. No error was given and both data source urls would be exactly the same and both would still exist.
What I discovered during the name change was what tables where connected to each data source path. The lowercase named datasource had only one table while the other camel caps had the rest of the tables.
Thinking is this a smart way of splitting the load/refresh? I have a feeling that the lowercase named source and associated table was added last. The whole load/refresh takes forever for the many tables data source (camel caps name).
Would it follow that one could replicate up to the full name. ie lower/upper case permutations of the character lenght of the sharepoint online name :}
Would that be worth while for load splitting? ie one name per table(s)
Any cons?
Just to clarify, for example
https://root/subroot.sharepoint.com/sites/longname
https://root/subroot.sharepoint.com/sites/Longname
https://root/subroot.sharepoint.com/sites/lOngname etc
Solved! Go to Solution.
@garythomannCoGC , One of the way , I think of, to correct source, if open tables in power query one by one. Open Advance editor (right click on table). Correct the code. And then apply at repeat it for each table
@garythomannCoGC , One of the way , I think of, to correct source, if open tables in power query one by one. Open Advance editor (right click on table). Correct the code. And then apply at repeat it for each table
User | Count |
---|---|
99 | |
86 | |
78 | |
75 | |
71 |
User | Count |
---|---|
112 | |
105 | |
96 | |
74 | |
66 |