Penetrate Synonyms

[Brook Mithani]

Somecommon synonyms of penetrate are enter, pierce, and probe. While all these words mean "to make way into something," penetrate carries a strong implication of an impelling force or compelling power that achieves entrance.

1. When another blames you or hates you, or people voice similar criticisms, go to their souls, penetrate inside and see what sort of people they are. You will realize that there is no need to be racked with anxiety that they should hold any particular opinion about you.

- Marcus Aurelius, Meditations

2. Water is the softest thing, yet it can penetrate mountains and earth. This shows clearly the principle ofsoftness overcoming hardness.

- Lao Tzu

3. The secret of Buddhism is to remove all ideas, all concepts, in order for the truth to have a chance to penetrate, to reveal itself.

- Hanh Nhat Thich, Buddha Mind, Buddha Body: Walking Toward Enlightenment

Regarding scenario 3 - If I don't want to to use "User Written Code" in order to write a SQL Execute Query to enforce Explicit execution like below, that would otherwise work perfectly (would like to maintain auto-generated DIS code if possible)

If you've got 1 sever instance with multiple databases and you want to join tables from multiple databases then you could also create a synonym in database A pointing to the table in database B. In doing so you then could use a single connection (single libname) for your joins which should allow SAS to push processing to the DB.

With 1500+ tables (more coming) I imagine it would require a maintenance script to make sure all are put into synonyms for all databases object - Would be easier if it was possible to put synonyms on the entire MS SQL Database. I think it might would be a little bit too much maintenance for us, but I can definitely see the benefits and use in other use-cases.

From my understanding synonyms are just another object in a schema so there is nothing specific required on the SAS side to access synonyms. It's just a normal libname using SAS/Access to SQL Server (or SAS/Access to ODBC).

If you want to go down this path then I also believe that it wouldn't take that much to create a maintenance script which keeps synonyms in sync with the data sources. Unlike for views you don't even have to define the columns but it's just on object level. A synonym in my simple world is - sort of - nothing else than a symbolic link to the actual object.

Unless you follow @Patrick 's suggestion and merge all relevant tables into one schema using aliases (or views), I think you are stuck with option 3. But I don't see what you mean with "Lose all metadata trace".

It has become a sort of dogma that user-written code should be avoided at all cost, but I think it is a wrong notion that has it's origin in the early days of DI Studio. It was often necessary to migrate existing programs as one big block of user-written code to get things up and running, and then just leave it that way. And the whole concept was a blow to a programmer's self-esteem. I remember very well the feeling of a big chef suddenly reduced to heat ready meals in a microwave oven, and it was very tempting to code everything as usual and put it in a user-written transformation.

Time has taught us to appreciate metadata and has shown us the problems that arise from code with hardcoded library assignments and table names, because they don't have a metadata trace. But the dogma often results in extremely complicated jobs with dozens of extracts, joins, appends and incomprehensible complex expressions that makes it impossible to figure out what is going on in the job, and all that only to avoid a user-written transformation that would be much easier to maintain. And some tasks are impossible in standard transformations, which makes user-written code (or user-defined transformations) unavoidable.

Of course data should be prepared and further processed in standard transformations, and user-written code used only for single tasks that cannot be solved by standard transformations. But in that case, and if care is taken to ensure that the metadata trace of columns works, there is no real difference between a standard transformation and a user-written transformation.

Then all the surrounding auto-generated code is the same, and the only difference between e.g. a standard join and a user-written join is that in the standard join only expressions and where-clauses are stored as text strings in metadata textstore objects, while the whole "working" code is stored as one textstore object in a user-written transformation.

To ensure that the metadata trace of column use works, and to make the transaction as robust as a standard transformation, there are some rules that must be followed, so here comes what I consider good practice for user-written transformations:

The code must be manually written, but apart from that the development of a user-written transformation following these rules is not more complicated than the development of any other transformation. A great help is to do things in the right order, especially:

This was written with standard transformation "User Written Code" in mind, but please note that it also applies to coding and using a user defined transformation, which has the extra benefit of user-defined transformation options that can be used in the code.

I was hoping that like DIS already can construct good pass-through if using identical libnames, there was a possibility to make DIS generate good pass-through using two different libnames (on the same MS SQL Server). Perhaps by using SAS/ACCESS for MS SQL instead of SAS/ACCESS for ODBC - or some other workaround.

My point about avoiding UWC/UWT was only because that it would be my own obvious/easy/first-choice go-to solution - I was looking for answers beyond the obvious - hence my comment about not using UWC/UWT (the Pass-Through example code I provided).

We already have 1500 tables and many DIS jobs with many joins - I did not want to go through all of them adding new UWC/UWT to solve the issue, I was hoping for another fix I was not aware of already.

It has not in any way been the purpose with my question to be advocating for not using UWC/UWT. I totally agree that well written/constructed UWC/UWT can be a good solution - But that was not what I was looking for (was hoping to learn something new). However, I would not have been satisfied with a UWC/UWT solution, IF there was a better solution hiding somewhere.

After reading my post again I think if I had just not have used the wording "Lose all metadata trace" in the final paragraph, I might not have been misunderstood and the attention of the reader would not be distracted from my actual question/challenge.

Tableau's Ask Data and Metrics features were retired in Tableau Cloud in February 2024 and in Tableau Server version 2024.2. With advances in natural language technologies, we're developing an improved interface that will make it easier to ask questions of your data and stay on top of changes. For more information, see How Tableau AI and Tableau Pulse are reimagining the data experience.

People may not use the same terminology found in your data source, so data source owners and Tableau administrators can add synonyms for specific data field names and values. Synonyms you enter are available throughout your organization, making data analysis quicker and easier for everyone.

When a field or value has similar usage throughout your organization, use data roles to apply the same synonyms across multiple data sources. For example, data roles are a great choice if every subsidiary uses the same names for business departments, or if product lines have a consistent set of sub-products.

Using data roles for synonyms saves you a lot of time, because you can manage them centrally in Tableau Cloud or Tableau Server. From Ask Data, you can publish new data roles and apply existing ones created in Ask Data or Tableau Prep(Link opens in a new window).

Want your resume to showcase how you sustain progress by expanding capabilities and resources? While 'Extended' suggests lengthening timeframes, more compelling language can reinforce your strategic foresight. Our guide explores vivid alternatives that highlight how you ensured continuity, increased capacity, and enabled ongoing success.

This statement is too vague and does not provide any specific information about how the knowledge was extended. It is better to provide specific examples or details to showcase the specific areas of knowledge that were expanded or improved.

While it may seem like a helpful statement, it lacks impact and does not highlight any specific achievements. Instead, it is better to mention the outcomes or results of extending the deadline, such as "Successfully extended the deadline by two days, allowing for additional research and resulting in a more comprehensive final report."

This statement is too vague and does not provide any specific information about the responsibilities that were extended. It is better to provide specific examples or details to showcase the specific tasks or duties that were added or expanded.

While it may seem like a positive statement, it lacks impact and does not highlight any specific achievements. Instead, it is better to mention the outcomes or results of extending your network, such as "Successfully extended my professional network by attending industry conferences and events, resulting in valuable connections and increased opportunities for collaboration."

Instead of using "Extended," job seekers can use synonyms like "Addressed," "Resolved," or "Assisted" to convey their role in handling customer inquiries. These alternatives highlight their ability to effectively communicate with customers, provide solutions to their problems, and ensure customer satisfaction.

When describing relationship-building experience, job seekers can opt for synonyms such as "Cultivated," "Fostered," or "Nurtured." These terms emphasize their skills in building and maintaining relationships with clients, stakeholders, or team members, showcasing their ability to establish trust, collaboration, and long-term partnerships.

3a8082e126