Is XPe Studio (SP2) compatible with SQL Server 2005 64 bits

[Guest]

Hello,

sorry if this has been figured-out already but I could not find any hard
evidence about the following question: is XPe Studio (SP2) compatible with
SQL Server 2005 64 bits as its RDBMS back-end ?

The questions lies both in :
1) the technical ability to migrate from (say) SQL Server 2000 SP4 to SQL
server 2005 64 bits (which seems to be OK), as well as ;
2) the compatibility (and correctness of operation) of the client side tools
(TD, CDM) with the new database back-end.

Any feedback about using SQL server 2005 64 bits to host an XPe SP2 database
shall be appreciated.

T.I.A.

 

[Guest]

I tried this and it works...

I was expecting to see significant improvements with this setup, but, it's
not quite what I expected. It appears to be similar in performance (from a
feel only viewpoint) to 32-bit, although I haven't run any comparative
testing as this was a totally different machine with 4 GB RAM, Dual Core 3.0
GHz CPU, RAID 0 stripe drives. I was able to do some preliminary testing to
determine why it was not as fast as I was hoping it to be. One thing that
made a big difference was that I was running NOD-32 anti-virus and although
it was the 64-bit version, it is still basically running in 32-bit mode. The
CPU usage for this app (NOD-32) during TD dependency checks, etc. was
significant and in fact, it was using more CPU than SQL Server or TD. I
disabled the NOD-32 app and things were definitely faster, but as I said, a
bit disappointing given that the hardware was “best†of class.

Joe

 

[Guest]

Joe,

thanks for the info. Have you done extensive testing regarding correctness
of operation?

The reason I was looking into migrating to SQL Server 2005 (64 bits) not
being performance improvements, performance on a par with SQL server 2000 (32
bits) is fine by me.

Nevertheless, have you conducted some kind of extended compatibility testing
in order to make sure that TD/CDM actually operate as they used to operate
with SQL Server 2000?

I would be concerned if switching to SQL server 2005 for the sake of backup
agent software availability (the actual reason) would eventually break XPe
Studio operation.

Regards,

 

[Guest]

I would say that the definition of "extensive compatibility testing" would
vary depending on the situation or the person. I have successfully rebuilt
old images (slx) and worked with the TD, CD and CDM tools with no visible
differences or problems to date. Whether or not that would qualify as
"extensive compatibility testing", I do not know.

 

[Guest]

Thanks Jo,

that is the feedback I was hoping for. Migrating myself then.

Regards,