Hello, One of my customer run into th

Written by Jerome Duquene. Posted in Comments

Hello, One of my customer run into the same issue today. As the OLAP database is stored on a shared server I wanted to avoid the need to stop the service (database was not droppable). What I did is: - Delete the database datafolder (some file were locked and not deleted) - Drop the ..db.xml file from the SSAS data root directory - Open ProcMon and search for handle containing the name of the database folder to be dropped (at this point I got a lot of handles making the tool hung - My idea was to close the handles) And the magic comes in - Not sure what happen, I suspect SSAS to review the files to be kept locked and as the .xml file was removed, unlock all the specific DB files. - Reopen ProcMon and search for handle containing the name of the database folder to be dropped (at this point I got no more files) - Remove the remaining files from the database folder - Delete the database via SSMS (it was still shown as on the server) - Restore the DB It allows me to restore the DB without any downtime for the other customers sharing the same SSAS instance. I would like to validate this approach so feel free to share if the solution helps you.