I have SQL Express 2008 installed and would like to use it instead of SQL Express 2005.
How do I configure the installation of Lookout such that it skips the installation of SQL Express 2005?
Are there any other steps that need to be taken in order for Lookout to properly work with SQL Express 2008?
Solved! Go to Solution.
Install Lookout first, then do an Instance Upgrade on the Citadel database. 2008 vs 2005 is not a dramatic difference as far as the Citadel functions can use. Performance is not much different.
SQL Express 2005 seems to be incompatible with Vista-64bit and Windows7-64bit, therefore, the installation may not be successful.
Are there other options (i.e. modifying the Lookout setup.ini file, etc. to use SQL 2008)?
The 'Instance Upgrade' method: is that a function in Lookout, MAX, SQL 2008 Setup, or SQL 2008 Configuration/Management tools?
I have installed it onto Vista x64 and Server 2008 x64.
SQL 2008 setup.
Ok - it worked.
However, for 64-bit installations, I had to use the WOW versions of SQL Express 2008, because, Citadel is a 32bit database and the native 64-bit installation versions would not allow an Instance Upgrade of Citadel.
I have a similar (but not the same) issues with CITIDAL/SQL Server with version 6.6.
We often image our computer with lookout preinstalled because of the time it takes to configure one machine if we were to install one by one.
The problem we run into has to do with the CITADAL database with the base image. When the machine name is changed, the Dabase behaves abnormally. When I try to delete the old database I was not successfully at it. It gets worse as I change the machine name, etc in the default database setting.
What I would like to find out is if there is a specific sequence when it comes to installing SQL 2005 or SQL 2008 Express with Lookout 6.6. And also what needs to happen when I am deploying a machine with an image, what can be done before the SID/Machine name change and what to do after SID/Machine name is changed to location specific.