I HAVE to be missing something really simple here!
I have a database in my development environment called Project. I have a database in my test environment called Project_UAT.
I’ve created an SSIS package that successfully copied my database from Project to Project_UAT. I’m pretty sure this eliminates most permission and configuration issues.
Now, I want to re-create the package and this time allow it to overwrite the destination, which is Project_UAT. This is simply because from time to time I want to click a button in the Microsoft SQL Management Studio that pushes the new database schema, data, users, and everything, out to my testing environment. I WANT to overwrite the data.
So I create the package just like I did before, but this time I specify the already-existing database name as the ‘Destination database’ and I select the radio button called ‘Drop any database on the destination server with the same name, then continue with the database transfer, overwriting existing database files.’
I click Next, and what does it tell me?
‘Database name already exists at destination’
Well, I KNOW! I just told you I want to overwrite it!
How do I make this work?
Not sure if I am missing the point but why do you not use a task to drop/delete the existing database prior to your deployment step?
Perhaps you could qualify the SSIS Component Tasks you are using within your SSIS package.
Cheers, John