Using the Datasource Navigator
Go Up to Datasource and Server Management
The Datasource Navigator provides a visual method for browsing, accessing, and manipulating objects. The Datasource Navigator contains a hierarchy consisting of groups, datasources, object type, and object nodes. Higher level nodes in the hierarchy have an associated Expand/Collapse icon, letting you drill down through the hierarchy to expose lower level nodes and objects.
- Groups organize the available data sources. A default set of groups corresponds to the supported DBMS platforms. You can also create custom groups to organize your data sources. For more information, see Categorizing Datasources using Color-coding and Labeling.
- Inside these groups are the data sources on your network that you have registered. You must register data sources in order to work against them. For more information, see Registering Datasources and Connecting to Datasources.
- With the exceptions of the Filters node, nodes below the datasource level correspond to the object types supported on the DBMS platform. For more information on the Filters node, see Filtering in the Navigator.
- At the lowest level, are the individual database objects on the data source. For a listing of object types by DBMS platform and detailed support summaries for each type, see Supported Objects.
For information on opening and closing the Navigator, Hiding and Displaying the Datasource Navigator
Bookmarks provide another means to quickly navigate to specific Navigator object nodes. For details, see Working with Bookmarks.
You can also initiate object type-specific actions and open object editors from the Navigator. For details, see Initiating Object Actions in the Navigator.
A number of viewing and organization options are available. They let you optimize the Navigator for your own purposes. These include:
- Basic viewing options that let you toggle between type-based or owner-based display, one-step expansion and collapse of hierarchy elements, hiding or display of system objects, saving of view option settings.
- Creating custom datasource groups to provide a deeper level of organization.
- Categorizing datasources using color-coding and labeling to quickly distinguish between datasources used for different purposes in your organization.
- Filtering the Navigator tree to display only selected nodes and objects. You can filter by name, schema or object type,
Connected to Team Server 2016
When Rapid SQL is connected to Team Server 2016 some other features are added to the Datasource Navigator and also, the Datasource Navigator displays datasources on Team Server 2016 and lets you work with relationships to local datasources.
Information about the basics of Team Server 2016 datasource support is in Working with Team Server 2016 Datasources.
To connect to Team Server 2016, ensure that Team Server 2016 usage is enabled and that you are logged in. For details, see Setting up and Connecting to Team Server 2016.
When Rapid SQL is connected to Team Server 2016, a node is added:
- Saved Searches: This node contains search definitions that you created using the advanced search feature. For details, see Searching Team Server 2016 for Datasources.
When Rapid SQL is connected to Team Server 2016, you can:
- Create a local datasource from a definition on the repository: register a local datasource as you would do for any static datasource, but use the Relate Team Server Source control to attach the local definition to a specified Team Server 2016 datasource definition. For more information, see Manually Registering or Editing Datasources.
- Detach a currently attached local datasource definition so that it is no longer syncronized with the Team Server 2016 definition: right-click the attached Datasource Navigator and select Unrelate Team Server Data Source and select Yes when prompted to verify.
- Refresh/View Related ER Models: Right-click an attached datasource and select either Refresh Related ER Models or View Related ER Models.
- Work with multiple local and Team Server 2016 datasources. For details, see Reconciling Local and Team Server 2016 Datasources.