We just implemented a new scenario for SYNONYM use (at our location). We use the Ektron content management system. Ektron has a product, eSync, that copies Ektron content from one server to another. We have our content in SQL Server databases. To eSync between servers, the Ektron database for each server has to have a different name (totally annoying). We have processes that need to peek into the Ektron databases. Thus, a stored procedure on one server that references the Ektron database will need to use a different database name than the same stored procedure on a different server, unless, of course, one uses a SYNONYM. So, in each of our databases that reference the Ektron database we create a SYNONYM to each referenced Ektron object, with the server-specific database name, and then we can deploy the identical stored procedures to each our database on each server. Problem solved!