George McGeachie Metadata Matters Limited. ER SIG June 9th,

Transcription

1 George McGeachie Metadata Matters Limited ER SIG June 9th,

2 an industry-leading data modeling tool that enables companies to discover, document, and re-use data assets. With round-trip database support, data architects have the power to easily reverse-engineer, analyze, and optimize existing databases. ER SIG June 9th,

3 ER/Studio Data Architect Reverse-engineer relational models from XSD Generate XSDs from LDM or PDM, using Meta Integration tools XSD generation wizard allows content to be tailored Quick Launch files allow process to be repeated Mapping from relational to XSD cannot be interrogated Supports XSD, XDR and DTD XSD scope is a model or submodel Generation from multiple XML namespaces not supported ER SIG June 9th,

4 ER/Studio workspace LDM LDM (Logical Data Model) Relational PDM Dimensional PDM PDM (Physical Data Model) ER SIG June 9th,

5 Namespaces in ER/Studio Logical Data Model The model is the namespace Physical Data Model The model is the default namespace Can further qualify with database user name Duplicates resolved when XSD generated. For example: becomes ER SIG June 9th,

6 Namespaces in ER/Studio The URI of a DTD or XML schema that defines any new elements and attributes created in the XML instance The URI of a DTD or XML schema that implicitly defines any element within the XML schema that is not explicitly defined, with the prefix of another namespace ER SIG June 9th,

7 Full LDM in ER/Studio ER SIG June 9th,

8 Schema A - Waiting Members ER SIG June 9th,

9 Two options 1. Generate XML Model using the MetaWizard export, from selected tables, and tinker with the XML afterwards 2. Use XML Builder to design and generate almost exactly what is required, and then tinker the XML model ER SIG June 9th,

10 You decide what to generate from, and configure the rules, then generate the XML Model. Then you can customise the model, or reference it as a type library. ER SIG June 9th,

11 Generating XML Schema Starting Open the model that you want to generate from In the File menu, select Export File ER SIG June 9th,

12 Generating XML Model Specify Output path and File name That s all there is to it - finished ER SIG June 9th,

13 Generating XML Model the Output ER SIG June 9th,

14 I ve generated a type library From the whole model "let the service people design the schemas" no structure manual control of re-use in schemas no impact analysis across schemas may be the only acceptable first step straightforward to generate ER SIG June 9th,

15 Generating XML Model the Output One Element, from the model One Complex Type per Entity With attributes One Simple Type per Domain No enumerations Annotations created from descriptions ER SIG June 9th,

16 Generating XML Model the Output Keyrefs derived from the PKs and linked to the Elements ER SIG June 9th,

17 You decide what to generate from, configure the rules, design the schema, and THEN generate the XML Schema. ER SIG June 9th,

18 XML Schema Generator- Start Right-click model or sub-model, select XML Schema Generation Record of previous generation, can be re-used ER SIG June 9th,

19 Add Namespace Information Options re. Use of namespace qualification ER SIG June 9th,

20 Set Generation options ER SIG June 9th,

21 Now... Design your schema! ER SIG June 9th,

22 Create root Drag Waiting Member onto Elements, and it s added to the schema ER SIG June 9th,

23 Add Waiting Member attributes Drag and drop Left to right, onto the complextype Then select and delete HasherId and SponsoringMemberId ER SIG June 9th,

24 Add an Element for the Sponsor Drag and drop Left to right ER SIG June 9th,

25 Rename and Revise Element Change name to Sponsor Alter nillable, minoccurs and maxoccurs ER SIG June 9th,

26 Convert HackHandle Element to an Attribute Drag the attribute onto the complextype node ER SIG June 9th,

27 Revise Attributes //////////////////////// //////////////////////// ////////////////////////////////////// Drag from Hasher ER SIG June 9th,

28 Include Required Simple Types These are not added for you, you need to know which ones you need ER SIG June 9th,

29 Save Settings ER SIG June 9th,

30 Now we ve finished Click on Finish and generate the schema ER SIG June 9th,

31 The Finished Schema it only contains what the message actually needs ER SIG June 9th,

32 Generating Individual Schemas all types can be local no need to 'include' or 'import' a base schema the 'standard' types are used to generate the schema, rather than being referred to by the schema The standard types are in the canonical data model potential for impact analysis can choose when to update each individual schema ER SIG June 9th,

33 ER SIG June 9th,

34 A more complex XSD Run Participants The LDM: ER SIG June 9th,

35 Run Participants Building the Schema ER SIG June 9th,

36 Add Simple Types Drag all the domains across All enumerations automatically included ER SIG June 9th,

37 The Finished Schema ER SIG June 9th,

38 HTML Reporting (from LDM) ER SIG June 9th,

39 Please Remember I ve used the default process all the way ER SIG June 9th,

40 ER SIG June 9th,

41 Data Type Conversions ER SIG June 9th,

42 Name Conversion ER SIG June 9th,

43 ER SIG June 9th,

44 Repeating the Process All element selections, the target file path and name, options, name and data-type conversions, can be saved as Quick-Launch settings These can be stored in the model, or as an external file They allow the process to be repeated exactly, or with minor variations ER SIG June 9th,