BT is creating lot of results split thus results storing in performance warehouse is turned off...
We are notified that one of our BT is facing issue with split results and its stopped storring in performance warehouse, could any1 please help me on this. what we can do in this case.
Best Answer
Hi Suraj,
the main question is what this BT is used for. If you use the BT to search for a certain transaction it doesn't have to be stored, you can still search. If you are using it to track a certain transaction over time it's a different thing. Charting a BT with thousands of splittings is pointless, a chart will be unreadable.
Some examples that might help here:
1. Lets assume you got an internal application with 2000 users. You can create a BT to find out who is using the app most frequently, but charting that over time wouldn't make sense. In that case the storing of the BT should be disabled.
2. Similar example, a webapp which is avertised via banners all over the internet, possibly creating 3-4million entrypoint > no point in charting this. Possibly use the % approach here. You are not interested into each single banner here, you want to know which ones work best. If its just a few hundred that left it's ok to stored them
3. a method is being called with with 10 different values > you can easily chart that over time and track which values is used most frequently, perfect for storing.
regards, Günter
Hi Suraj,
Also from looking at your BT you are splitting on 5 different measures, it may make sense to create multiple business transactions breaking up the splittings across them. I would evaluate if you can do that or not. My other suggestion is if you don't need to chart the data to just turn off the performance warehouse storage for that BT, you will see information there as long as it stays in the session storage but then is lost as the session store is cleaned up by the server. To evaluate how long your session storage goes back to right click on your system profile and click details and it will tell you there.
HTH,
Kyle
As Kyle indicated, re-consider the what information (visit info) you are trying to display.
1. BT with no filter should be avoided.
2. Can you enumerate number of splittings upto, say few 100s?
3. Avoid storing Unique splittings in PWH, instead use session storage or use option export to Big data via HTTP.
