Hello All,

I have two installations.  (Wise Installation Studio 7.0)

The first installs a 331MB sample SQL Server MDF file and runs an attach script at the end to attach it.
The second installs the same sample SQL Server MDF file 430Mb (with encrypted store procedures) and runs an attach script at the end to attach it.
Both installation routines work well and the databases are attached to the selection SQL Server during the installation.

The problem we are having though is with the encrypted SQL Server database install and the fact it appears that the MDF file that gets installed differs to the MDF file that is used in the source.
When we use the installed MDF file we receive SQL errors in our application stored procedures, however if we use the source file that the MSI is built from we do not.
We have run several different tests and this is definitely the case.

We did further testing extracting the MDF file out of the MSI (using the below statement) and performing a binary comparison it to the source file.
It confirms that the MDF file in the MSI file is different to the source file of the installation.

msiexec.exe /a "D:\Develop\Support\Tencia Support Database.msi" /qb TARGETDIR=D:\Develop\Support\MSI

Now I wouldnt have a problem with the fact the file structure is changing in the process of a compile but we did the same comparisions with the first install that installs an unencrypted MDF file.
The file in the MSI in this case is a 100% exact binary match to the source file.

So why in this case when I compile an MDF file that contains encrypted stored procedured do we find that the source MDF file is altered when compiled into the MSI ?

Any help much appreciated.