April 12, 2007 at 10:05 am
We just took possession of a terrific new test box, 4-Xeon CPUs, lot of RAM. It came configured with Windows Server 2003 64-bit (x64), and with Windows 2000 (32-bit) sp4 installed on it. The purpose of this box is to support testing of existing SQL2000 applications.
Our prod SQL2K SQL Servers are similar, but the hitch is that they are all on 32-bit Windows.
Re-installing everything to get back to a 32-bit OS is going to cost us precious time.
Other than fact that it's simply different than production, can anyone think of a specific reason why we'd need to send this back and have the OS re-installed as 32-bit OS? Or do you think we could safely proceed with 32-bit SQL2000 on a 64-bit OS?
Alternatively, has anyone here got experience (good or bad) running 32-bit SQL2000 on a 64-bit OS?
Thanks in advance,
Mike Good
April 12, 2007 at 10:22 am
Mike:
We're runnning the same configuration in a high volume OLTP system for more than 8 months. Everything seems fine. The issues that we are running into centers around perf monitor. I had a hard time getting the sql perf counter to show up. We use perf mon all the time. You have to use the 32 bit version of perf mon to get SQL perf counter to work. However, when we log the counters to a file the SQL perf counter do not get saved. I have not resolved this issue, all the non SQl counter work fine. Another issue is that we have 16 gigs of ram but SQL Server only recognizes 8 gigs. We're running SQL Server EE sp 4 on Windows Server 2003 64-bit (x64).
I have not had any issues with Profiler, query analyzer, Enterprise or SQL server itself. We do not use DTS or replication. Clustering works fine too.
I hope this insight helps.
Dan Pitta
April 12, 2007 at 11:11 am
Thanks, Dan! That's kind of thing I was hoping to hear. I'm sorry to hear about the perfmon, but I don't think that's enough to force us to rebuild this box.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply