SQL Server Performance Forum – Threads Archive
x32 to x64 and Extended Stored ProceduresIn some days we are getting a new sql server and we are upgrading from x32 to x64, We are going to use a Itanium 2 1.6GHz 6MB cpu and 4GB ram with a raid (0+1) system. Whit the use of the site I have been able to solve a lot of the problems. But I#%92m still a bit concern about systems â€œextended store proceduresâ€. I understand that we have to recompile the code with the new x64, can somebody point me I the right direction? Are the any concerns? Problem?
I don’t think you need any special treatment on extended SPs, BTW do you have any user-defined ext.SPs on your database. Satya SKJ
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.
hmm i don’t understand what you mean? We have user-defined funtions that calls extended store procedures yes.
thx<img src=’/community/emoticons/emotion-7.gif’ alt=’:s’ /> Kalle for the email. Provid parts of the mail.<br /><From microsoft:<br /><For databases that are migrating from SQL Server 2000 32-bit to SQL Server 2000 64-bit, the 32-bit extended stored procedures will <not work with SQL Server 2000 (64-bit). The Microsoft Windows on Windows 64 (WOW) environment in 64-bit Microsoft Windows will not <run 32-bit SQL Server extended stored procedures (.dlls). The 32-bit extended stored procedures must be recompiled with a 64-bit <compiler to obtain the 64-bit .dlls. <br /><br /><1: Srv.h. You must use the 32-bit version that is available in SQL Server 2000.<br /><2: Opends60.dll. This file is available with SQL Server 2000 (64-bit). Opends60.dll is located in the MssqlBinn folder.<br /><3: Opends60.lib. This file is available with SQL Server 2000 (64-bit). Opends60.lib is located at the root of the media.<br /><br /><br />