Routes appear in the routing table for the database. For outgoing messages, Service Broker determines routing by checking the routing table in the local database. For messages on conversations that originate in another instance, including messages to be forwarded, Service Broker checks the routes in msdb. PowerDesigner models routes as extended objects with a stereotype of <<Route>>.
You can modify an object's properties from its property sheet. To open a route property sheet, double-click its Browser entry.
The following extended attributes are available on the Microsoft tab:
Name |
Description |
---|---|
Owner |
Specifies the owner of the route. Scripting name: Owner |
Remote service |
[v2005] Specifies the name of the remote service to which the route points. Scripting name: Service |
Broker instance |
Specifies the database that hosts the target service. Scripting name: BrokerInstance |
Lifetime |
Specifies the amount of time, in seconds, that SQL Server retains the route in the routing table. Scripting name: Lifetime |
Address |
Specifies the network address for the route. The next_hop_address specifies a TCP/IP address in the following format: TCP://{ dns_name | netbios_name | ip_address } : port_number Scripting name: Address |
Mirror address |
Specifies the network address for a mirrored database with one mirrored database hosted at the next_hop_address. The next_hop_mirror_address specifies a TCP/IP address in the following format: TCP://{ dns_name | netbios_name | ip_address } : port_number Scripting name: MirrorAddress |