Installing vendor databases on SQL Server is usually pretty straight forward. Not many DBA's like the process, but the proliferation of 3rd party products that use SQL Server is continuing to grow.
Recently this particular vendor, of course insisting their product was 64 bit and SQL Server 2005 compatible, ran into problems for me. It's only compatible after you manually add registry entries that make the installshield program think there is a 32 bit instance of MSDE ! Yah, that's compatible (oh by the way, those registry entries also break the sql browser service so you whole instance becomes unavailable unless it is accessed directly through a port number). NICE !
Getting through the above process was painful enough, than the installshield installer errors out with a SQL Server error on creating a view, indicating that a dependent object is missing.
Technical support, while helpful is clueless. "Never seen that before!" After 3 days of issues, i'm basically troubleshooting for them, taking traces from our lab environment and comparing them. Finally we stumble on to the fact that installshield is creating a _setup directory where it is putting the SQL Server scripts. This folder (_setup), happens to be under the data directory where the MDF's are being created (NICE). This data directory happens to be a mount point!
Ahhh, for whatever reason, Installshield runs the scripts differently from a mount point vs. a drive letter. We think it's either a bug in Installshield or an issue with the permissions on the mount point. We were not able to find any differences in permissions, but sure enough when we changed the location of the data files (which changes the location of the _setup directory), objects in the database were created in the correct order. 3 days of my life gone.
This vendor could have done many things differently. Providing some type of manual work around, scripts to create the database (this was not an option so I was screwed), backups to manually restore, something, someway to escape the installshield install (which was like version 5 !).
And this was not a small dippy vendor, this is compliance software used by many of the big banking and financial institutions. No wonder so many found them selves in danger of collapse !
Watch those mount points.