Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mwaters1
Starting Member
1 Post |
 Posted - 2007-03-07 : 12:17:51
|
| Are there any known issues\gotchas with running SQL 2000 EE (SP4) on X64 Windows 2003? I already ran into the problem of installing the software and figured it out before ever finding any information using searches with every combination of words I could think of!I am currently receiving an error saying "The specified Network Name is No longer available" when trying to setup a Proxy Agent Account. I have no problem doing this same task with the same ID on a 32 OS system. Both sql servers are 2000 EE version 8.00.2187 and part of separate clusters. The OS is Windows Server 2003 SR1; X64 on the one that doesn't work and 32 on the one that does work. On the X64 machine, client connections to the sql server work fine, applications appear to work fine, and replication works fine. I can ping both the phyisical and virtual names fine and isql local works.Any help\information would be greatly appreciated!mwaters |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2007-03-07 : 12:33:27
|
| I don't know what a proxy agent account is, so I can't really address that issue.anyway, we run SQL2K 32bit on x64 win2k3 in a cluster environment. It runs pretty well with 1 exception. You cannot monitor the SQL Server counters using any 3rd party monitoring tool because of the way Microsoft separates 32bit stuff from 64bit stuff in the registry. In fact, the issue is bigger than just a monitoring problem, but that is typically where you see an issue arise because of the separation that exists.Nutshell: you won't be able to monitor your 32bit SQL server perfmon counters (buffer cache hit ratio, target server memory, etc.) using MOM, netiq, etc.-ec |
 |
|
|
|
|
|
SQL 2000 on X64 Windows 2003