![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi all: I have use Asp.net and Reporting Services as the font end reporting tool and Analysiss Services as the back end Data Cube. All of the applications are save on the same machine. If I want to mirgate to SQL Server 2000 64-bit server, anything I need to watch out? Do I need to recoding all the source code in Asp.net and Reporting Services Thanks |
#3
| |||
| |||
|
|
You might want to double check, but I don't thing Reporting Services is supported on the 64-bit platform in the 2000 edition (2005 is) I think the same thing applies to ASP.NET, I don't think there is a 64- bit version of the 1.1 frame work, you would have to use version 2.0 of the framework. But apart from this I have apps running against AS2k on 64-bit servers and it behaves the same as the 32-bit version (apart from some early memory leak issues which the latest SP seemed to address) -- Regards Darren Gosbell [MCSD] Blog: http://www.geekswithblogs.net/darrengosbell In article <51DD60F9-A99E-412B-A9E9-919595280EDF (AT) microsoft (DOT) com>, kentkent (AT) discussions (DOT) microsoft.com says... Hi all: I have use Asp.net and Reporting Services as the font end reporting tool and Analysiss Services as the back end Data Cube. All of the applications are save on the same machine. If I want to mirgate to SQL Server 2000 64-bit server, anything I need to watch out? Do I need to recoding all the source code in Asp.net and Reporting Services Thanks |
![]() |
| Thread Tools | |
| Display Modes | |
| |