ER/Studio Data Architect - Recent changes [en]

Template:Warning

Nadja.pollard — Wed, 12 Aug 2026 22:32:38 GMT

← Older revision		Revision as of 22:32, 12 August 2026
Line 1:		Line 1:

	[[Image:Warning.gif\|30px]] '''WARNING:''' {{{1}}}		[[Image:Warning.gif\|30px\|link=]] '''WARNING:''' {{{1}}}

Template:Caution

Nadja.pollard — Wed, 12 Aug 2026 22:32:18 GMT

← Older revision		Revision as of 22:32, 12 August 2026
Line 1:		Line 1:
	[[Image:Caution.png\|30px]]'''Important:''' {{{1}}}		[[Image:Caution.png\|30px\|link=]]'''Important:''' {{{1}}}

Template:Tip

Nadja.pollard — Wed, 12 Aug 2026 22:32:00 GMT

← Older revision		Revision as of 22:32, 12 August 2026
Line 1:		Line 1:
	[[Image:Magic_Wand_Icon.png\|30px]]'''Tip:''' {{{1}}}		[[Image:Magic_Wand_Icon.png\|30px\|link=]]'''Tip:''' {{{1}}}

Template:Note

Nadja.pollard — Wed, 12 Aug 2026 22:31:41 GMT

← Older revision		Revision as of 22:31, 12 August 2026
Line 1:		Line 1:
	[[Image:Notepad_blue_icon_2.png\|30px]]'''Note:''' {{{1}}}		[[Image:Notepad_blue_icon_2.png\|30px\|link=]]'''Note:''' {{{1}}}

Upgrading From Previous Versions

Nadja.pollard — Thu, 06 Aug 2026 17:33:21 GMT

Upgrade Checklist

← Older revision		Revision as of 17:33, 6 August 2026
Line 6:		Line 6:

	* Download the latest version of ER/Studio. To download the most current release, go to the [https://license.embarcadero.com/edn/#login Registered Products Portal].		* Download the latest version of ER/Studio. To download the most current release, go to the [https://license.embarcadero.com/edn/#login Registered Products Portal].
	* Review the ER/Studio ReadMe. For the most current installation and usage information, see the [~~http://docs.embarcadero.com/products/er_studio/ERDA200/ReadMe.htm online version~~].		* Review the ER/Studio ReadMe. For the most current installation and usage information, see the Read Me files located on the [[Main_Page\|Main page]] of the wiki.
	* In case you need to upgrade Team Server/Repository to match the features available in your version of {{Product}}, see [[ts_en:Upgrading_Team_Server_and_Repository\|Upgrading Team Server and Repository]].		* In case you need to upgrade Team Server/Repository to match the features available in your version of {{Product}}, see [[ts_en:Upgrading_Team_Server_and_Repository\|Upgrading Team Server and Repository]].

	~~{{Note\|Beginning with v18.5, {{Product}} retains settings from previous versions.}}~~
	{{Warning\|If you plan to use the sample macros, first make a copy of the samples, and then store the copy in a folder separate from the ER/Studio installation folder to avoid overwriting your custom macros when upgrading to later versions of ER/Studio. Make sure that you make changes only to the copy of the sample macros.}}		{{Warning\|If you plan to use the sample macros, first make a copy of the samples, and then store the copy in a folder separate from the ER/Studio installation folder to avoid overwriting your custom macros when upgrading to later versions of ER/Studio. Make sure that you make changes only to the copy of the sample macros.}}

Containment Relationships

Nadja.pollard — Tue, 04 Aug 2026 22:22:36 GMT

Changing Classes in Nested Object hierarchies

← Older revision		Revision as of 22:22, 4 August 2026
(2 intermediate revisions by the same user not shown)
Line 52:		Line 52:
	In the '''Expanded''' view, you can view Nested Objects and Containment Relationships individually. This view is useful to see which objects are shared across other tree branches.		In the '''Expanded''' view, you can view Nested Objects and Containment Relationships individually. This view is useful to see which objects are shared across other tree branches.

	~~<<NADJA - INSERT "EXPANDED VIEW~~.png"		[[File:Expanded_View.png\|900px]]

	==Changing Classes in Nested Object hierarchies==		==Changing Classes in Nested Object hierarchies==

	~~You may want~~ to change the nature of how data is implemented in your physical models that support hybrid hierarchies. You may decide that what was an embedded or nested object should be promoted to being a top level object such as a Table or Collection. Likewise, you may wish to change the relationships between nested objects and top level objects from referencing to containment relationships and vice versa~~. We have provided tools to do this~~.		ER/Studio Data Architect allows you to change the nature of how data is implemented in your physical models that support hybrid hierarchies. You may decide that what was an embedded or nested object should be promoted to being a top-level object such as a Table or Collection. Likewise, you may wish to change the relationships between nested objects and top-level objects from referencing to containment relationships and vice versa.

	Users can easily change a relationship type for containment relationships. While viewing a containment relationship that you want to change the relationship type, click '''Switch Relationship Class''' in the ribbon bar. The following actions occur:		Users can easily change a relationship type for containment relationships. While viewing a containment relationship that you want to change the relationship type, click '''Switch Relationship Class''' in the ribbon bar. The following actions occur:

File:Expanded View.png

Nadja.pollard — Tue, 04 Aug 2026 22:19:25 GMT

Nadja.pollard uploaded File:Expanded View.png

New page

Containment Relationships

Nadja.pollard — Tue, 04 Aug 2026 21:58:02 GMT

Visualizing Hierarchical Structures

← Older revision		Revision as of 21:58, 4 August 2026
Line 48:		Line 48:
	In the '''Rolled Up''' view, Nested Objects are rolled up into the top-level object.		In the '''Rolled Up''' view, Nested Objects are rolled up into the top-level object.

	~~<<NADJA - INSERT "ROLLED UP VIEW~~.png"		[[File:Rolled_up_view.png\|700px]]

	In the '''Expanded''' view, you can view Nested Objects and Containment Relationships individually. This view is useful to see which objects are shared across other tree branches.		In the '''Expanded''' view, you can view Nested Objects and Containment Relationships individually. This view is useful to see which objects are shared across other tree branches.

File:Rolled up view.png

Nadja.pollard — Tue, 04 Aug 2026 20:56:21 GMT

Nadja.pollard uploaded File:Rolled up view.png

New page

Containment Relationships

Nadja.pollard — Tue, 04 Aug 2026 20:54:22 GMT

Visualizing Hierarchical Structures

← Older revision		Revision as of 20:54, 4 August 2026
Line 44:		Line 44:
	You can switch between these views using the '''Diagram and Display Options''' in the ribbon bar [[File:DiagramObject Display.png\|50px]].		You can switch between these views using the '''Diagram and Display Options''' in the ribbon bar [[File:DiagramObject Display.png\|50px]].

	[[File:~~DiagramObject Display~~.png\|~~50px~~]]		[[File:Diagram_and_Display_Options_for_Rolled_Up_View.png\|500px]]

	In the '''Rolled Up''' view, Nested Objects are rolled up into the top-level object.		In the '''Rolled Up''' view, Nested Objects are rolled up into the top-level object.

File:Diagram and Display Options for Rolled Up View.png

Nadja.pollard — Tue, 04 Aug 2026 20:53:49 GMT

Nadja.pollard uploaded File:Diagram and Display Options for Rolled Up View.png

New page

Containment Relationships

Nadja.pollard — Tue, 04 Aug 2026 20:53:27 GMT

Visualizing Hierarchical Structures

← Older revision		Revision as of 20:53, 4 August 2026
(11 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	{{Parent\|Creating and Editing Relationships}}		{{Parent\|Creating and Editing Relationships}}

	A containment ~~relationship is used~~ in physical models ~~that~~ support hierarchies such as JSON, MongoDB, Google BigQuery, Databricks, and ~~now~~ traditional platforms that allow embedded JSON. These structures include nested objects which can be contained in top level objects such as tables or collections or other nested objects. Nested objects and containment relationships ~~will be~~ created		Use containment relationships in physical models to support hierarchies such as JSON, MongoDB, Google BigQuery, Databricks, and traditional platforms that allow embedded JSON. These structures include nested objects which can be contained in top-level objects such as tables or collections or other nested objects.
	* ~~Manually~~ within physical models
	* ~~During~~ the reverse engineering of such hierarchical platforms		Nested objects and containment relationships are created:
	* By the user during generation of physical objects from logical models that have relationships with the "Containment" flag set		* manually within physical models.
			* during the reverse engineering of such hierarchical platforms.
			* by the user during generation of physical objects from logical models that have relationships with the '''Containment''' flag set.

	== Manually Creating Containment Relationships in Physical Models ==		== Manually Creating Containment Relationships in Physical Models ==
	To create a new containment relationship
			'''To create a new containment relationship'''

	#On the Data Model Explorer, click the Data Model tab.		#On the Data Model Explorer, click the Data Model tab.
	#Choose {{Menu\|Insert > Relationships > Containment Relationship}}~~, this~~ changes the cursor icon and ~~allow~~ you to select the objects in the main window ~~with which~~ to create the relationship.		#Choose {{Menu\|Insert > Relationships > Containment Relationship}}. This step changes the cursor icon and allows you to select the objects in the main window used to create the relationship.
	#Click on the object containing the other object.		#Click the object containing the other object.
	#Click on the object contained within the previously clicked object.		#Click the object contained within the previously-clicked object.
	Double clicking on the relationship line ~~will open~~ the Containment Relationship Editor where you can edit settings		Double clicking on the relationship line opens the Containment Relationship Editor where you can edit settings.

	[[Image:Containment_Relationship.png\|250px]]		[[Image:Containment_Relationship.png\|250px]]

	The '''1''' indicates a single nested object; '''*''' indicates an array.		The '''1''' indicates a single nested object while '''*''' indicates an array.

	== During the reverse engineering of such hierarchical platforms ==		== During the reverse engineering of such hierarchical platforms ==
	When you reverse engineer a physical platform that natively supports hierarchical structures such as JSON, MongoDB, Google BigQuery, Databricks, Data Architect ~~will create~~ nested objects linked via containment relationships.		When you reverse engineer a physical platform that natively supports hierarchical structures such as JSON, MongoDB, Google BigQuery, and Databricks, Data Architect creates nested objects linked via containment relationships.

	~~For~~ the following platforms that support embedded JSON:		There is an option in the Reverse Engineer Wizard for columns of specified data types to identify records that contain valid JSON data and parse the contents to create nested objects. This is a powerful way to document previously hidden data, improving documentation and governance. This feature is available only for the following platforms that support embedded JSON:
	* MS SQL Server 2019 & 2022
	* Azure SQL DB		* Azure SQL DB
	* Azure Synapse Analytics		* Azure Synapse Analytics
	* Oracle 19c ~~and~~ Oracle 23ai		* MS SQL Server 2019, 2022
			* Oracle 19c, Oracle 23ai
			* PostgreSQL
	* Snowflake		* Snowflake
	* PostgreSQL
	there is an option in the Reverse Engineer Wizard for columns of specified data types to identify records that contain valid JSON data and parse the contents to create nested objects. This is a powerful way to document previously hidden data, improving documentation and governance.

	== Generating physical objects from logical models that have relationships with the "Containment" flag set ==		== Generating physical objects from logical models that have relationships with the "Containment" flag set ==
	Relationships in logical models ~~have~~ properties to indicate whether the relationship is containing and ~~its~~ direction of containment. For platforms that support hierarchical structures there is a setting in the Generate Physical Model ~~Wizard~~ and in Compare/Merge that determines how entities and relationships are transformed into objects in the physical model. If the option "Create All As Tables Unless Contained" is selected in the Generate Database ~~Wizard~~ or "Consider all as Tables unless Contained" is selected in Compare/Merge ~~Wizard~~, ~~Data Architect will create~~ containment relationships for every relationship in the logical marked as "Containing". Entities that are contained by another ~~will~~ become nested objects~~. Entities~~ that are not contained by any other ~~will~~ become top level objects appropriate for that platform such as Tables or Collections.
			Relationships in logical models include properties that indicate whether the relationship is containing and the direction of containment. For platforms that support hierarchical structures there is a setting in the Generate Physical Model wizard and in Compare/Merge that determines how entities and relationships are transformed into objects in the physical model.

			If the option '''Create All As Tables Unless Contained''' is selected in the Generate Database wizard or if '''Consider all as Tables unless Contained''' is selected in the Compare/Merge wizard, ERDA creates containment relationships for every relationship in the logical marked as "Containing". Entities that are contained by another become nested objects and entities that are not contained by any other become top-level objects appropriate for that platform, such as Tables or Collections.

	== Visualizing Hierarchical Structures ==		== Visualizing Hierarchical Structures ==
	The hierarchical model containing Nested Objects linked via containment relationships can be visualized in ~~two different ways~~:		The hierarchical model containing Nested Objects linked via containment relationships can be visualized in either rolled up or expanded views.

			You can switch between these views using the '''Diagram and Display Options''' in the ribbon bar [[File:DiagramObject Display.png\|50px]].

			[[File:DiagramObject Display.png\|50px]]

	~~===~~ Rolled Up ~~===~~		In the '''Rolled Up''' view, Nested Objects are rolled up into the top-level object.
	~~Here~~ Nested Objects are rolled up into the top level object.

	<<NADJA - INSERT "ROLLED UP VIEW.png"		<<NADJA - INSERT "ROLLED UP VIEW.png"

	~~===~~ Expanded ~~===~~		In the '''Expanded''' view, you can view Nested Objects and Containment Relationships individually. This view is useful to see which objects are shared across other tree branches.
	~~Here~~ you can ~~see the~~ Nested Objects and Containment Relationships individually. This is useful to see which objects are shared across other tree branches.

	<<NADJA - INSERT "EXPANDED VIEW.png"		<<NADJA - INSERT "EXPANDED VIEW.png"

	~~Changing Between these Views~~

	~~You can switch between these views using the ribbon bar feature Diagram and Display Options~~

	~~<<NADJA - INSERT Diagram and Display Options for Rolled Up View.png>>~~

	==Changing Classes in Nested Object hierarchies==		==Changing Classes in Nested Object hierarchies==

Exporting a Data Model to XML

Nadja.pollard — Thu, 23 Jul 2026 21:47:37 GMT

← Older revision		Revision as of 21:47, 23 July 2026
(2 intermediate revisions by the same user not shown)
Line 5:		Line 5:
	{{Product}} allows you to generate the following XML-type files:		{{Product}} allows you to generate the following XML-type files:

	* '''XML Metadata Interchange (XMI)''': The XMI file format was designed primarily to allow the exchange of data between data modeling applications. Based on the XML format, XMI allows data modelers using Unified Modeling Language (UML) and programmers using different languages and development tools to exchange information about the model metadata, what a set of data consists of and how it is organized.		* '''XML Metadata Interchange (XMI)'''. The XMI file format was designed primarily to allow the exchange of data between data modeling applications. Based on the XML format, XMI allows data modelers using Unified Modeling Language (UML) and programmers using different languages and development tools to exchange information about the model metadata, what a set of data consists of and how it is organized. Using the MetaData Export Wizard, you can export the entire.dm1 file or an individual model to an.xsd or an.xmi file. This function makes assumptions about how the model elements map to the xsd elements but gives you some control over the export parameters. For more information, see [[Exporting Metadata for a Particular Model]] and [[Exporting Metadata for all Models and Submodels]].

	Using the MetaData Export Wizard, you can export the entire.dm1 file or an individual model to an.xsd or an.xmi file. This function makes assumptions about how the model elements map to the xsd elements but gives you some control over the export parameters. For more information, see [[Exporting Metadata for a Particular Model]] and [[Exporting Metadata for all Models and Submodels]].

	* '''XML Schema Generation (XML)''': The XML Schema Generation Wizard creates schemas that can be based on a logical or physical model, a submodel, or even specific components only of a model or submodel. The XML Schema Generation Wizard allows you to customize the XML schema structure by clicking the desired options and dragging the available objects from the database design into a tree representing the XML schema. This wizard provides advanced options to transform relational entities and attributes into complex types, elements and attributes, define naming standards and datatype mapping, and incorporates the Quicklaunch system used in other wizards to save previous settings and streamline repetitive operations. For more information, see [[Generating a Customized XML Schema]].

	~~You can use XML editing applications such as Microsoft XML Notepad, Eclipse, Visual Studio, and Altova XML Spy to view and edit the schema~~.

			* '''XML Schema Generation (XML)'''. The XML Schema Generation Wizard creates schemas that can be based on a logical or physical model, a submodel, or even specific components only of a model or submodel. The XML Schema Generation Wizard allows you to customize the XML schema structure by clicking the desired options and dragging the available objects from the database design into a tree representing the XML schema. This wizard provides advanced options to transform relational entities and attributes into complex types, elements and attributes, define naming standards and datatype mapping, and incorporates the Quicklaunch system used in other wizards to save previous settings and streamline repetitive operations. For more information, see [[Generating a Customized XML Schema]]. You can use XML editing applications such as Microsoft XML Notepad, Eclipse, Visual Studio, and Altova XML Spy to view and edit the schema.

	==See Also==		==See Also==

Exporting Metadata for a Particular Model

Nadja.pollard — Thu, 23 Jul 2026 21:32:07 GMT

← Older revision		Revision as of 21:32, 23 July 2026
Line 16:		Line 16:
	'''Page 1'''		'''Page 1'''

	'''Type'''. From the list, select the MIR Bridge that you want to use to generate a file that you then can import into the third-party application supported by the selected bridge type.		*'''Type'''. From the list, select the MIR Bridge that you want to use to generate a file that you then can import into the third-party application supported by the selected bridge type.

	'''Page 3'''		'''Page 3'''

Exporting Metadata for all Models and Submodels

Nadja.pollard — Thu, 23 Jul 2026 21:30:18 GMT

← Older revision		Revision as of 21:30, 23 July 2026
(One intermediate revision by the same user not shown)
Line 7:		Line 7:
	'''To export model metadata'''		'''To export model metadata'''

	# Click {{Menu\|File > Export File > Export Model Metadata}}.		# Click {{Menu\|File > Export File > Export Model Metadata}} OR on the Data Model Explorer, right-click the model or submodel you want to export, and then select '''Export Model Metadata'''.
	# Complete the Export Model Metadata dialog ~~as required~~.		# Complete the Export Model Metadata dialog.
	# Click the field ~~beside~~ the option name to either enter a value or select a value from the list. Help text for each option appears in the area at the bottom of the page.		# Click the field next to the option name to either enter a value or select a value from the list. Help text for each option appears in the area at the bottom of the page.
	# If you want to save or print the log, choose ''Save to File'' or '' Print''.		# If you want to save or print the log, choose '''Save to File''' or '''Print'''.

	The following ~~describe~~ options ~~that require additional explanation:~~		The following descriptions include additional information for some of the options available during this process.

	'''Page 1'''		'''Page 1'''

	''Type'': From the list, select the MIR Bridge you want to use to ~~generates~~ a file that can ~~be imported~~ into the third-party application supported by the selected bridge type.		*'''Type'''. From the list, select the MIR Bridge that you want to use to generate a file that you then can import into the third-party application supported by the selected bridge type.

	'''Page 2'''		'''Page 2'''

	''Model selection''~~: Choose~~ to export the logical model, physical model, or all models. If you ~~choose~~ to export the physical model, because there ~~can~~ be numerous physical models in an {{Product}} file ~~you must enter the name of the model in the Physical model name field~~.		*'''Model selection'''. Use to export the logical model, physical model, or all models. If you want to export the physical model, you must enter the name of the model in the '''Physical Model Name''' field because there may be numerous physical models in an {{Product}} file.

	'''Page 3'''		'''Page 3'''

	This page displays informational and warning messages describing successful and unsuccessful exports ~~respectively~~.		This page displays informational and warning messages describing successful and unsuccessful exports.

	==See Also==		==See Also==

Exporting Metadata for a Particular Model

Nadja.pollard — Thu, 23 Jul 2026 21:22:21 GMT

← Older revision		Revision as of 21:22, 23 July 2026
(One intermediate revision by the same user not shown)
Line 7:		Line 7:
	'''To export model metadata'''		'''To export model metadata'''

	# On the Data Model Explorer, right-click the model or submodel you want to export.		# Click {{Menu\|File > Export File > Export Model Metadata}} '''OR''' on the Data Model Explorer, right-click the model or submodel you want to export, and then select '''Export Model Metadata'''.
	~~# Click~~ '''Export Model Metadata'''.
	# Complete the Export Model Metadata dialog.		# Complete the Export Model Metadata dialog.
	# Click the field next to the option name to either enter a value or select a value from the list. Help text for each option appears in the area at the bottom of the page.		# Click the field next to the option name to either enter a value or select a value from the list. Help text for each option appears in the area at the bottom of the page.

Exporting Metadata for all Models and Submodels

Nadja.pollard — Thu, 23 Jul 2026 21:18:44 GMT

← Older revision		Revision as of 21:18, 23 July 2026
Line 3:		Line 3:
	{{Note\|You need a separate license to access the MetaData Export bridges. See the About ER/Studio dialog for a list of the modules you are licensed to use.}}		{{Note\|You need a separate license to access the MetaData Export bridges. See the About ER/Studio dialog for a list of the modules you are licensed to use.}}

	~~Using~~ the MetaData Export Wizard~~, you can~~ export your diagrams in formats compatible with a wide-variety of industry-standard tools. For a current list of supported platforms and bridges available, see [[ER/Studio MetaWizard Import/Export Bridges]].		Use the MetaData Export Wizard to export your diagrams in formats compatible with a wide-variety of industry-standard tools. For a current list of supported platforms and bridges available, see [[ER/Studio MetaWizard Import/Export Bridges]].

	'''To export model metadata'''		'''To export model metadata'''

Exporting Metadata for a Particular Model

Nadja.pollard — Thu, 23 Jul 2026 21:17:14 GMT

← Older revision		Revision as of 21:17, 23 July 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	{{Parent\|Exporting the Data Model}}		{{Parent\|Exporting the Data Model}}

	{{Note\|You need a separate license to access the MetaData Export bridges. See the About ~~ERStudio~~ dialog for a list of the modules you are licensed to use.}}		{{Note\|You need a separate license to access the MetaData Export bridges. See the About ER/Studio dialog for a list of the modules you are licensed to use.}}

	~~Using~~ the MetaData Export Wizard~~, you can~~ export your diagrams in formats compatible with a wide-variety of industry-standard tools. For a current list of supported platforms and bridges available, see [[ER/Studio MetaWizard Import/Export Bridges]].		Use the MetaData Export Wizard to export your diagrams in formats compatible with a wide-variety of industry-standard tools. For a current list of supported platforms and bridges available, see [[ER/Studio MetaWizard Import/Export Bridges]].

	'''To export model metadata'''		'''To export model metadata'''

Exporting Metadata for all Models and Submodels

Nadja.pollard — Thu, 23 Jul 2026 21:16:26 GMT

← Older revision		Revision as of 21:16, 23 July 2026
Line 1:		Line 1:
	{{Parent\|Exporting the Data Model}}		{{Parent\|Exporting the Data Model}}

	* You need a separate license to access the MetaData Export bridges. See the '' About ~~ERStudio''~~ dialog for a list of the modules you are licensed to use.		{{Note\|You need a separate license to access the MetaData Export bridges. See the About ER/Studio dialog for a list of the modules you are licensed to use.}}

	Using the MetaData Export Wizard, you can export your diagrams in formats compatible with a wide-variety of industry-standard tools. For a current list of supported platforms and bridges available, see [[ER/Studio MetaWizard Import/Export Bridges]].		Using the MetaData Export Wizard, you can export your diagrams in formats compatible with a wide-variety of industry-standard tools. For a current list of supported platforms and bridges available, see [[ER/Studio MetaWizard Import/Export Bridges]].
Line 8:		Line 8:

	# Click {{Menu\|File > Export File > Export Model Metadata}}.		# Click {{Menu\|File > Export File > Export Model Metadata}}.
	# Complete the '' Export Model Metadata'' dialog as required.		# Complete the Export Model Metadata dialog as required.
	# Click the field beside the option name to either enter a value or select a value from the list. Help text for each option appears in the area at the bottom of the page.		# Click the field beside the option name to either enter a value or select a value from the list. Help text for each option appears in the area at the bottom of the page.
	# If you want to save or print the log, choose ''Save to File'' or '' Print''.		# If you want to save or print the log, choose ''Save to File'' or '' Print''.

Exporting the Data Model

Nadja.pollard — Thu, 23 Jul 2026 21:14:43 GMT

← Older revision		Revision as of 21:14, 23 July 2026
Line 3:		Line 3:
	You can export the logical or physical data model to a variety of different formats and platforms, allowing you to collaborate with other database users, communicate your database design, create SQL from your data model to create a physical database, and create an XSD Schema you can share with application developers who can use this schema.		You can export the logical or physical data model to a variety of different formats and platforms, allowing you to collaborate with other database users, communicate your database design, create SQL from your data model to create a physical database, and create an XSD Schema you can share with application developers who can use this schema.

	Click ~~a link below~~ for information on exporting data models:		Click one of the following links for information on exporting data models:

	* [[Exporting Metadata for a Particular Model]]		* [[Exporting Metadata for a Particular Model]]

Exporting Metadata for a Particular Model

Nadja.pollard — Thu, 23 Jul 2026 21:12:56 GMT

← Older revision		Revision as of 21:12, 23 July 2026
Line 1:		Line 1:
	{{Parent\|Exporting the Data Model}}		{{Parent\|Exporting the Data Model}}

	* You need a separate license to access the MetaData Export bridges. See the About ERStudio dialog for a list of the modules you are licensed to use.		{{Note\|You need a separate license to access the MetaData Export bridges. See the About ERStudio dialog for a list of the modules you are licensed to use.}}

	Using the MetaData Export Wizard, you can export your diagrams in formats compatible with a wide-variety of industry-standard tools. For a current list of supported platforms and bridges available, see [[ER/Studio MetaWizard Import/Export Bridges]].		Using the MetaData Export Wizard, you can export your diagrams in formats compatible with a wide-variety of industry-standard tools. For a current list of supported platforms and bridges available, see [[ER/Studio MetaWizard Import/Export Bridges]].
Line 8:		Line 8:

	# On the Data Model Explorer, right-click the model or submodel you want to export.		# On the Data Model Explorer, right-click the model or submodel you want to export.
	# Click Export Model Metadata.		# Click '''Export Model Metadata'''.
	# Complete the ''Export Model Metadata'' dialog ~~as required~~.		# Complete the Export Model Metadata dialog.
	# Click the field ~~beside~~ the option name to either enter a value or select a value from the list. Help text for each option appears in the area at the bottom of the page.		# Click the field next to the option name to either enter a value or select a value from the list. Help text for each option appears in the area at the bottom of the page.
	# If you want to save or print the log, click ''Save to File'' or ''Print''.		# If you want to save or print the log, click '''Save to File''' or '''Print'''.

	The following ~~describe~~ options ~~that require additional explanation~~.		The following descriptions include additional information for some of the options available during this process.

	'''Page 1'''		'''Page 1'''

	''Type'': From the list, select the MIR Bridge you want to use to ~~generates~~ a file that can ~~be imported~~ into the third-party application supported by the selected bridge type.		'''Type'''. From the list, select the MIR Bridge that you want to use to generate a file that you then can import into the third-party application supported by the selected bridge type.

	'''Page 3'''		'''Page 3'''

	This page displays informational and warning messages describing successful and unsuccessful exports ~~respectively~~.		This page displays informational and warning messages describing successful and unsuccessful exports.

	==See Also==		==See Also==