The reason for this is that the deployment center runs with the currently logged on user (on the machine running the DC), but if the database is hosted on a different machine or domain this user usually does not exist there, and the deployment center gives you an error message like: "Login failed for user ''. The user is not associated with a trusted SQL Server connection.".

The best solution I have found is to:

  1. either create the same user on the database server if possible, or
  2. move the database to the same machine running the deployment center (or a machine in the same domain).

This is quite an annoying bug, and it would be nice if the deployment center would default run the database job with the user defined in the web site connection string - or even better: present the opportunity to specify the user on which to run with.

Maybee in the next version of Deployment center....   :-)