Hi Every one, I am doing a POC with the xenapp in out environment. I am able to install and get all the charts tables populate with data. But it uses three different Indexes, my question is does it really need three different indexes, is there any specific reason why it uses three different indexes. any help is greatly appreciated.
Hi Mohankesireddy,
Looking at the XenApp app I have here, I have the following indexes:
The following reasons apply to not only the XenApp app, but pretty much any other complex app you care to think of...
Different security requirements for data - An index is the lowest logical unit that security may be effectively applied to. For example, you want your Ops team to see the alerts data, but not the perfmon data (not a realistic example, but I hope you understand my meaning).
Different retention rates - You may want to keep your alert data, and winevents data for 30 days, but only care about your perfmon data for 7 days. Separate indexes allow you this flexibility (and is crucial for compliance purposes)
Different storage requirements - What is another team needed to use some data in a mission critical manner (e.g. alerting) so needs to ensure that their searches run as quickly as possible. With separate indexes you can specify separate (quicker) storage tiers making this possible. Alternatively, you might need to backup some security related data for long periods (e.g. 7 years) to you can move that indexes data to cheaper storage.
Effective compression - Grouping similar data together helps with compression rates.
Summary Indexing - The creation of an additional index for the purposed of summarisation greatly increases the performance of apps, dashboards, and searches.
There are a bunch of other reasons (incl. performance), but I believe these alone justify why it's a good idea to use multiple indexes... all of which would have been relevant to the developer as they created the XenApp app.
Hope this helps 🙂
Hi Turk,
No there is not specific reason, Just wanted to understand why they need three different indexes.
Hi there - Is there any reason why you think this would be a problem?
Hi Mohankesireddy,
Looking at the XenApp app I have here, I have the following indexes:
The following reasons apply to not only the XenApp app, but pretty much any other complex app you care to think of...
Different security requirements for data - An index is the lowest logical unit that security may be effectively applied to. For example, you want your Ops team to see the alerts data, but not the perfmon data (not a realistic example, but I hope you understand my meaning).
Different retention rates - You may want to keep your alert data, and winevents data for 30 days, but only care about your perfmon data for 7 days. Separate indexes allow you this flexibility (and is crucial for compliance purposes)
Different storage requirements - What is another team needed to use some data in a mission critical manner (e.g. alerting) so needs to ensure that their searches run as quickly as possible. With separate indexes you can specify separate (quicker) storage tiers making this possible. Alternatively, you might need to backup some security related data for long periods (e.g. 7 years) to you can move that indexes data to cheaper storage.
Effective compression - Grouping similar data together helps with compression rates.
Summary Indexing - The creation of an additional index for the purposed of summarisation greatly increases the performance of apps, dashboards, and searches.
There are a bunch of other reasons (incl. performance), but I believe these alone justify why it's a good idea to use multiple indexes... all of which would have been relevant to the developer as they created the XenApp app.
Hope this helps 🙂
Thanks Turk. this helps.