A server profile contains settings that are associated with the corresponding database connection. These settings are used when you deploy or bind database artifacts, such as stored procedures or SQL statements, to the database server. When you create a connection to a database, the workbench uses database defaults and applicable global preferences to automatically generate a server profile for the connection. In the Server Profile Manager view, generated server profiles are indicated with "(generated)" appended to the name.
One of the benefits of deployment groups is that you can manage the deployment of multiple artifacts to multiple databases with one action. This action is more efficient than deploying each artifact individually to each database.
Deploying a routine for development | Deploying routines for production |
---|---|
You deploy from the Data Project Explorer view. | You deploy from the Deployment Group Manager view. |
You can deploy only a single routine to a single database at a time. | You can deploy multiple routines to multiple databases with one action. |
After deployment, the icon next to the routine in the Data Project Explorer view has a wrench on it to indicate that the routine is deployed for development | After deployment, the icon next to the routines in the Data Project Explorer view is unchanged. |
If you enable debugging, you can start debugging a deployed routine either from the Data Project Explorer view or from the Data Source Explorer view. | If you enable debugging, you can start debugging a deployed routine only from the Data Source Explorer view. |
You can run a deployed routine either from the Data Project Explorer view or from the Data Source Explorer view. | You can run a deployed routine only from the Data Source Explorer view. |
To deploy the stored procedure by using a deployment group:
The deployment results are displayed in the SQL Results view. A snapshot of the deployment information is shown in the Deployment Results folder under the deployment group in the Deployment Manager view.
Because the Enable debugging when applicable option was selected in the GSDB4tutorial Profile server profile, the stored procedure is automatically enabled for debugging from the Data Source Explorer.