Rigid and flexible relationship

SQL Server Analysis Services Attribute Relationships

rigid and flexible relationship

PDF | Background: Findings from an earlier weight reduction program indicated that control of eating behaviors could play a major role not only in weight loss. Read how you can be flexible in a relationship, and find happiness. Our attachment to things, to ideas and to certain views can make us rigid and unrelenting. Do not forget to properly set the attribute relationship type (rigid or flexible). If you can, use rigid. If the relationship is flexible and a change is detected during.

These hierarchies help both the user understand how to move through a dimension, but they also serve a second, and potentially more important role as a way to improve performance of aggregations and queries. Improve SQL Server Analysis Services Performance with the Usage Based Optimization Wizard An integral part of creating performant aggregations is to create and maintain the appropriate attribute relationships for your hierarchies.

The reason the relationship is so important is because the hierarchy, the attribute relationship, and any related aggregations work in conjunction with each other to produce faster results for a query.

Furthermore, because the relationship has been established, the measure rollup by year can look to see if there is an aggregation at the year level. If that level is not available and if the attribute relationship is setup properly which we show later in the tipthen instead of having to look all the way down to the date key value, SSAS can just try to find an aggregate at the next level of the relationship, which would be quarter in our example.

Summating the data at the quarter level would be much faster than having to drill down to the date key level. Even if no aggregation exists at the quarter level, then the query could look to the month level which again would be faster than summing the data at the date key level.

To show this process in practice, let us take a look at an example using a date field. These databases are available for download, free, on CodePlex at: For our date example, I actually create a new data dimension, Date TEST, based on the existing date view in the data source view. As shown below, year, quarter, month, week, and date were added as attributes to the dimension.

Flexible and rigid relationship

As noted in the second screen print, SSAS displays a caution triangle and displays a warning that says that no attribute relationships exists in the hierarchy and as such performance may be impacted.

Thus, we now know we should create an attribute relationship, but it is not required. To create the relationship we need to click on the Attribute Relationship tab. As shown in the following illustration, we currently do have attribute relationships setup; however all of them directly link each attribute back to the Date Key, the lowest level. No intermediate relationships exist to efficiently rollup the hierarchy levels.

You will also notice that the attribute relationship tab contains two views. The graphical view is on the top of the below screen print while the detail list view is shown at the bottom. In order to create a relationship, we can either use the drag and drop method or manual add method via the tool bar button. As shown below, to create our relationship, we actually start at the lowest level and then drag our attribute to the next higher level value.

rigid and flexible relationship

In our example, the Date key is already related to each of the four attributes in the hierarchy. As such, our first level of the relationship, which is Date Key to Week, has already been established. As you can see in the below illustration, we now have established the Date Key to Calendar Week to Calendar Month relationships.

Do not forget to set properly attribute relationship type (rigid or flexible).

Often, individuals choose the path of resistance and refusal to change, because they equate being flexible with settling or weakness. But it is actually the opposite. By letting go of these attachments, we are not denying our beliefs and values, we are simply giving up the mandate that we must control every aspect of them.

It is not the same as being detached. Rather, it simply means you are not holding on, you are not grasping. When you become non-attached, expectations and emotions will no longer control your life.

And you will have a new sense of clarity that allows you to see the truth that lies at the heart of the matter, which ultimately helps you be more flexible with your partner. We feel validated and we feel that we have sound judgment. Granted, those are all positive things. But what do we get out of being right when we are in a relationship?

rigid and flexible relationship

The need to be right leads to the need to win an argument. And the need to win an argument means your partner has to lose. And if you really care about your partner, why would you want them to lose? When you let go of your need to be right, you open yourself up to a generative and exciting environment where both you and your partner can learn and grow together.

rigid and flexible relationship

This also creates a safe space in the relationship where both you and your partner can trust the other to engage in compassionate listening and effective communication techniques.

But what we really should be focusing on is ensuring our partner shares our same values.

How to be flexible in a relationship

And they play a role in most aspects of your life — the choices you make, how you interpret scenarios, the reactions you have, who you choose to spend time with, the expectations you make. Read more about how values drive your decisions. When someone respects and honors your values, you feel safe and secure.

But when someone denies those values, it can make you feel uneasy, or perhaps even cause you suffering. And a lack of shared values with your partner will only lead to continuous arguments and ongoing frustrations that can ultimately lead to the demise of your relationship.