In discussions with a client, the option of placing a development copy of the database on the same server which will later be used for the production database. This is not the first choice, but does merit consideration as an option, I think. The reason for doing so would be to avoid the cost of a second license for SS on a development server.
However, before we consider that, we'd like to know what the potential dangers might be. One that was raised is that somehow a failure in the app using the development database could cause it to corrupt and, in turn, cause the server itself to crash, removing the server from service for the organization.
My questions are
A) how realistic is it to be afraid that a total corruption in one database (the dev version) would cause the loss of service in all other databases on that same server?
B) are there other reasons to avoid putting dev and production databases on the same server?
DOn't be afraid to tell me this is a bad idea if it is. I am just trying to consider all options on the table.