Recently, I needed to use dbcreatewizard.exe to install a datawarehouse on a SQL 2008 R2 cluster on windows 2008 R2 SP1. The SQL server is using mountpoints for its datafile locations. I ran into 2 issues:
When starting dbcreatewizard.exe, when you click on next, the tool tries to enumerate all local drives. While trying this, I received the error that he couldn’t find the X-drive:
This was quite logical, as the X-drive is located on another instance on another node. To solve this issue, I had to failover all SQL instances to the same node and restart dbcreatewizard.exe. But be careful: a lot of applications don’t like it when you failover an instance: do an impact analysis before you do it and ensure everyone involved knows about what you are doing! Also, once the installation succeeds, ensure the instances are relocated on the original nodes.
Once I fixed the issue with the X-drive, I select the installing the datawarehouse as well as the right instance. I click on next and finish and encounter another error:
This message is a lot more cryptic than the one before:
Note: The following information was gathered when the operation was attempted. The information may appear cryptic but provides context for the error. The application will continue to run.
System.InvalidOperationException: An error occurred while trying to create the database on your SQL Server. Check your logs for more information.
I skipped back to the configuration of the database, and what do I see?
Apparently, when selecting another instance in the dropbox, the data file path and log file path aren’t updated. For me, this default setting was incorrect (though correct for another existing instance). I changed the settings to reflect the real file locations and the database created just fine. What’s the lesson here? Always check carefully what you do ;).