What files are changed when upgrading eval version of SQL 2005 to full version?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Paul Landry - 31 Jul 2008 17:03 GMT

Hi All,

We deployed a SQL Server 2005 Standard eval version to a customer as an
Proof-of-concept.
They decided to buy our product, and we purchased Volume License Keys for
SQL Server 2005 Standard.
We then went through the "Upgrade" process to convert the Eval version to
the Volume License version, without any problems.
The customer's IT department want to know which files were changed
by upgrade.
I am assuming that there is a time-bombed DLL that was replaced.
I haven't been able to find any documentation on this, though.
Can anyone help me out here?
Thanks,

Paul

Reply to this Message

mike.mcneer@gmail.com - 31 Jul 2008 18:50 GMT

Paul,
There is nothing for them to worry about. The codebase and files
between the EVAL and the licensed edition are exactly the same, the
keys just "unlock" the software. Other than that what is their main
concern?
Mike

On Jul 31, 11:03 am, "Paul Landry" <plan...@centricsoftware.com>
wrote:

> Hi All,
>
[quoted text clipped - 12 lines]
>
> Paul

Reply to this Message

Paul Landry - 31 Jul 2008 19:54 GMT

Hi Mike,
They're doing security audits on the system and IT had installed monitoring
software on the system.
Apparently our customer didn't inform his IT that we were doing the
upgrades, and now IT wants to know what changed so they can determine the
effect on their installed security software.
Thanks for the reply.
I'll forward this on to them.
Paul

Paul,
There is nothing for them to worry about. The codebase and files
between the EVAL and the licensed edition are exactly the same, the
keys just "unlock" the software. Other than that what is their main
concern?
Mike

On Jul 31, 11:03 am, "Paul Landry" <plan...@centricsoftware.com>
wrote:

> Hi All,
>
[quoted text clipped - 12 lines]
>
> Paul

Reply to this Message