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 |
|
coolerbob
Aged Yak Warrior
841 Posts |
Posted - 2005-06-16 : 05:50:18
|
| We are thinking of buying a 32 bit OLTP server (Windows server Enterprise 2003 32 bit + SQL Server 2000 Enterprise) & a 64 bit OLAP Server (Windows Server Enterprise 2003 64 bit + SQL Server 2000 Enterprise + Analysis Services 64 bit) Would there be any compatibility issues between 32 and 64 bit as we use replication from the 32 server to the 64 bit server? Or any other compatibility issues? |
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2005-06-16 : 11:25:23
|
quote: Originally posted by coolerbob We are thinking of buying a 32 bit OLTP server (Windows server Enterprise 2003 32 bit + SQL Server 2000 Enterprise) & a 64 bit OLAP Server (Windows Server Enterprise 2003 64 bit + SQL Server 2000 Enterprise + Analysis Services 64 bit) Would there be any compatibility issues between 32 and 64 bit as we use replication from the 32 server to the 64 bit server? Or any other compatibility issues?
I'd say the best bet would be to call the hardware vendor. If both servers will be Dell the call Dell, ect...I don't know of any issues with replication between 32 and 64 bit machines. The major difference with 64 bit is it allows you to run more than 4gb of RAM without having to run AWE. I don't think there should be any issues but certainly can't garantee that there wouldn't be any.DanielSQL Server DBA |
 |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-06-16 : 11:59:09
|
| For the 64bit I would avoid the itanium (IA64) based hardware. This hardware is really at the end of it's life (atleast for windows). I would look at an Opteron or Xeon 64 bit solution (x64) instead. This is the direction that all the software vendors are going. The problem though is that Microsoft doesn't have a fully 64bit version of SQL 2K or Analysis Services for the x64 platform. They only have a full 64bit for IA64. SP4 for SQL2K improves things greatly for x64 based systems running SQL2K but it still isn't native 64bit code. You would need to wait until SQL2K5 is available for full 64bit support for the database. As for replication there would be no compatibility issues at either way you go (IA64 or x64). Also, why bother getting a 32bit environment at all? Why not get two 64bit environments?-ec |
 |
|
|
coolerbob
Aged Yak Warrior
841 Posts |
Posted - 2005-06-17 : 06:38:39
|
| Thanks, that was brilliant.We are looking into a full 64 bit environment nowthanks |
 |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2005-06-17 : 07:24:44
|
| I not only agree with eyechart, I'll go so far as to say if you're really serious about 64-bit, wait until SQL 2005 is released in November. 64-bit is better implemented in that version, it was essentially tacked-on in 2000. You're going to feel a tug towards 2005 anyway because of the significant enhancements, and instead of setting up a solution now that you will probably have to redesign later, just hang on a few months. You can start now with the June CTP release of SQL Server 2005:http://www.microsoft.com/sql/ |
 |
|
|
coolerbob
Aged Yak Warrior
841 Posts |
Posted - 2005-09-27 : 11:52:16
|
| Ok, we are going the 64 Bit SQL 2005 on Windows 2003 Server route.One Question: If our 64 bit server (Win2003, SQL2005) goes down, can we restore our DB's to a 32 bit server (Win2003, SQL2005)?I'm thinking yes, but I just want to double-check. |
 |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-09-27 : 12:30:29
|
quote: Originally posted by coolerbob Ok, we are going the 64 Bit SQL 2005 on Windows 2003 Server route.One Question: If our 64 bit server (Win2003, SQL2005) goes down, can we restore our DB's to a 32 bit server (Win2003, SQL2005)?I'm thinking yes, but I just want to double-check.
atleast with SQL 2000 the datafiles are the same. You can detach/attach and move the databases between 32bit and 64bit. I am not sure about SQL2K5, but I think it would be strange for microsoft to remove a feature like that.-ec |
 |
|
|
|
|
|
|
|