Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
With Connection Clustering, you no longer need to register a separate server per database. Simply register your server, open a Query Analyzer and swap between all of that server's available databases with ease. The Schema Browser will also show you all of the databases on a server and allow you to expand their nodes, not just the one you indicated in the server connection properties. We've added this feature to all database servers that had this limitation including PostgreSQL, Teradata Aster, Greenplum, Netezza, ParAccel and SQL Database (Azure).
For those more technically inclined, PostgreSQL and its ilk have the model of a single connection per database. Once a connection is established to a specific database, the connection cannot be changed to refer to another database. To get around this limitation, Connection Clustering automatically allocates a new connection when the user switches databases, giving the user a streamlined user experience. If the user switches back to a database for which a connection has already been allocated, then that connection is reused.
With Connection Clustering, if you expand a PostgreSQL server connection you can see all of its databases and expand them all. No more need to have one connection per database to explore the contents of your whole server.
Database Context can be changed with the Database Dropdown at the top of the Query Analyzer so that you can execute queries you've already run on another database on the same server. There's no more need for a separate connection on each DB.