ER/Studio - Embarcadero Technologies Product Documentation
ER/Studio - Embarcadero Technologies Product Documentation ER/Studio - Embarcadero Technologies Product Documentation
TUTORIALS > DIMENSIONAL MODELING The result is that Approved_Product becomes the Fact table. The parent tables of Approved_Product will all become dimension tables and the Product_Patent table will be designated as undefined. As another exercise, select another dimension table and change the type of dimension depending on the desired data refresh rate as in the following illustration. Dimensional Tables Icons in the Data Model Explorer have changed to reflect the dimensional model designation. Dimensional type set to Type 1. Fixed is the default. Now designated as a Fact table. Manually set to a Bridge table. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 386
TUTORIALS > AUTOMATING TASKS Automating Tasks ER/Studio is equipped with a highly documented Automation Interface. The automation interface is driven by the Sax Basic language (a derivative of the Visual Basic for Applications language) and serves many purposes, fundamentally for enabling you to customize ER/Studio through an application interface There are two main reasons to employ the Automation Interface: • Automate Routine Tasks – Automate tedious, routine modeling tasks or customize ER/Studio to enforce modeling practices in your organization. For example, you can write a macro that will automatically colorize child tables that contain propagated foreign keys. Or, you can write a macro to automatically insert a specific name and primary key into new entities as they are created. • Collaborate with other applications – Your ER/Studio models contain valuable metadata that you can access from applications such as Microsoft Excel, Access, and Outlook. Using ER/Studio's automation interface, you can collaborate with any external application that has an exposed API or its own automation interface. In this walk-through, we’ll demonstrate an example of how to leverage ER/Studio’s automation interface to dramatically increase modeler productivity. You will not be writing any Sax Basic (VBA) code in this walk-through. You will running a macro that is included with the product. You can write your own macros using the Sax Basic Integrated Development Environment included in ER/Studio. Creating Macros Using the Sax Basic integrated development environment, you can expand upon the functionality offered in the sample macros provided or create macros to automate model development and maintenance. To access the Sax Basic development environment, click Tools > Basic Macro Editor. TIP: The automatic appearance of lists as you type, allows you to select and insert ER/Studio Automation Objects. After inserting an object, you can get information about the object by selecting it and then clicking the Browse Object tool on the application toolbar. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 387
- Page 335 and 336: ADMINISTRATOR’S REFERENCE > ESTAB
- Page 337 and 338: Tutorials The tutorials are intende
- Page 339 and 340: TUTORIALS > GETTING STARTED WITH ER
- Page 341 and 342: TUTORIALS > LOGICAL AND PHYSICAL MO
- Page 343 and 344: TUTORIALS > LOGICAL AND PHYSICAL MO
- Page 345 and 346: TUTORIALS > LOGICAL AND PHYSICAL MO
- Page 347 and 348: TUTORIALS > LOGICAL AND PHYSICAL MO
- Page 349 and 350: TUTORIALS > LOGICAL AND PHYSICAL MO
- Page 351 and 352: TUTORIALS > LOGICAL AND PHYSICAL MO
- Page 353 and 354: TUTORIALS > LOGICAL AND PHYSICAL MO
- Page 355 and 356: TUTORIALS > DOCUMENTING AN EXISTING
- Page 357 and 358: TUTORIALS > DOCUMENTING AN EXISTING
- Page 359 and 360: TUTORIALS > DOCUMENTING AN EXISTING
- Page 361 and 362: TUTORIALS > DOCUMENTING AN EXISTING
- Page 363 and 364: TUTORIALS > DOCUMENTING DATA LINEAG
- Page 365 and 366: TUTORIALS > DOCUMENTING DATA LINEAG
- Page 367 and 368: TUTORIALS > DOCUMENTING DATA LINEAG
- Page 369 and 370: TUTORIALS > DOCUMENTING DATA LINEAG
- Page 371 and 372: TUTORIALS > DOCUMENTING DATA LINEAG
- Page 373 and 374: TUTORIALS > DIAGRAM NAVIGATION AND
- Page 375 and 376: TUTORIALS > DIAGRAM NAVIGATION AND
- Page 377 and 378: TUTORIALS > IMPORTING AND EXPORTING
- Page 379 and 380: TUTORIALS > IMPORTING AND EXPORTING
- Page 381 and 382: TUTORIALS > IMPORTING AND EXPORTING
- Page 383 and 384: TUTORIALS > DIMENSIONAL MODELING Si
- Page 385: TUTORIALS > DIMENSIONAL MODELING Wo
- Page 389 and 390: TUTORIALS > AUTOMATING TASKS 7 Name
- Page 391 and 392: TUTORIALS > COLLABORATIVE MODELING
- Page 393 and 394: TUTORIALS > COLLABORATIVE MODELING
- Page 395 and 396: TUTORIALS > COLLABORATIVE MODELING
- Page 397 and 398: TUTORIALS > COLLABORATIVE MODELING
- Page 399 and 400: TUTORIALS > COLLABORATIVE MODELING
- Page 401 and 402: TUTORIALS > COLLABORATIVE MODELING
- Page 403 and 404: TUTORIALS > COLLABORATIVE MODELING
- Page 405 and 406: TUTORIALS > COLLABORATIVE MODELING
- Page 407 and 408: TUTORIALS > COLLABORATIVE MODELING
- Page 409 and 410: Glossary A Active File Directory: T
- Page 411 and 412: GLOSSARY Denormalization: The inten
- Page 413 and 414: GLOSSARY M Macro: Code written in t
- Page 415 and 416: GLOSSARY S Scale: The scale of a nu
- Page 417 and 418: Index Symbols 284, 299, 308 @var su
- Page 419 and 420: INDEX Metadata Import Options 44 Me
- Page 421: INDEX Adding a Macro 315 Deleting a
TUTORIALS > DIMENSIONAL MODELING<br />
The result is that Approved_<strong>Product</strong> becomes the Fact table. The parent tables of Approved_<strong>Product</strong> will all<br />
become dimension tables and the <strong>Product</strong>_Patent table will be designated as undefined. As another exercise,<br />
select another dimension table and change the type of dimension depending on the desired data refresh rate as<br />
in the following illustration.<br />
Dimensional Tables<br />
Icons in the Data Model Explorer have<br />
changed to reflect the dimensional<br />
model designation.<br />
Dimensional type set to Type 1.<br />
Fixed is the default.<br />
Now designated<br />
as a Fact table.<br />
Manually set to a Bridge table.<br />
EMBARCAD<strong>ER</strong>O TECHNOLOGIES > <strong>ER</strong>/STUDIO® 8.0.3 US<strong>ER</strong> GUIDE 386
Change language