Steps: 1. Give the name of the alias , automatically it assigns the columns of the physical table 3. Even it inherits all the properties of the physical table. Post a Comment. Copyright - mkashu. Designed by Templateism. Datawarehouse Architect. About Support Center. Trends OBIA 7. By kashif on November 17, There is absolutely no performance issue with aliases.
Aliases are also handy because when you create an alias its name can be included in the SQL as a comment — which can give you information as to exactly which LTS was being used. Never be afraid to create aliases, and use them freely. No Account? Sign up. By signing in, you agree to our Terms of Use and Privacy Policy. Already have an account? Sign in. By signing up, you agree to our Terms of Use and Privacy Policy.
Enter the email address associated with your account. We'll send a magic link to your inbox. Email Address. All Sign in options. Enter a Email Address. Choose your interests Get the latest news, expert insights and market research, sent straight to your inbox. Newsletter Topics Select minimum 1 topic. Enterprise Software. Nabhanil Mondal November 21, 0 Comments. Amol Palkar Posted November 19, 0 Comments. Anonymous Posted November 19, 0 Comments. Jeff M. Kurt Wolff Posted November 20, 0 Comments.
Anonymous Posted November 20, 0 Comments. As stated below vanilla RPD uses aliases a lot —. Anonymous Posted October 5, 0 Comments. Jeff, Kurt, Have you guys ever seen an Alias table joined to an Opaque View table in the Physical Layer not bring back all the expected matches? Only the primary names of subject areas, hierarchies, levels, tables, and columns appear. This feature works in a different way from SQL aliases or the alias feature in the Physical layer.
It simply provides synonyms for object names, much like synonyms in SQL. Aliases are created automatically when you rename presentation objects. For example, if you change Catalog to Catalog1, the original name Catalog is added to the Aliases list.
0コメント