Introduction

Previous  Index  Next  How To Use

( Enterprise Edition )

 

The Enterprise Edition of Database Workbench comes with the TeamServer feature, offering the following:

a additional shared repository with registered servers and databases
non-local workspace, use the same workspace on different client machines
team based to-do list
shared SQL & Code catalogs
built in Version Control System

 

The Database Workbench TeamServer service needs to be installed on a machine that's always on so that Database Workbench Enterprise clients can connect to it. In the case you're sure this connection cannot be made, for example, when you're out of the office, you can start Database Workbench Enterprise with the -noteamserver command line switch, you can do this by editing the shortcut you use to open Database Workbench.

 

Before you can use the TeamServer features, you need to set up the Database Workbench TeamServer, using the console, which is installed together with the TeamServer service itself.

 

Database Workbench Enterprise clients will connect using a specific user name and password, specified in each clients settings.

 

Database Workbench TeamServer and clients

 

Once Database Workbench Enterprise clients can connect to the TeamServer, the above mentioned features will be added to the user interface.

 

To be able to do certain things, like register a server for the shared repository, or delete shared catalog items, you need privileges for it. These can be administered using the Console.