I am aware that this issue has been discussed before. However I have not found a satisfactory answer. I occasionally run into this issue: I have a deployed SSAS database on the server from a project in SSDT. I open the project again at a later time in SSDT, make some changes such as adding a new attribute to a dimension and deploy with the same name. I get a metadata engine error "Errors in the metadata manager. The database with the name of 'XYZ' already exists in the 'SERVER' server.".
Please note that unlike commonly discussed scenarios, I have not renamed anything. The Database Name property in SSDT matches exactly both the Name and ID properties on the server, and the Deploy Changes Only property is set in SSDT. Why doesn't it see that I want to overwrite, or at least ask me whether I want to overwrite? Since the ID and Name properties on the server are derived from the Database Name property in SSDT, it is clear I want to overwrite?
I know I can delete the database on the server and deploy successfully, but I don't want to do this. The only way I found of deploying successfully without deleting the database on the server is to change the Database Name property in SSDT (e.g. by adding a 2 to the original name) then deploy, rename back to the original name then deploy with overwriting, then delete the renamed one from the server.
The fact that I can circumvent the error in this way surely proves the current functionality is a bug?
Charles
Charles Kangai, MCT