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 |
|
divinyl
Starting Member
4 Posts |
 Posted - 2008-02-13 : 08:11:55
|
| Hi thereOur developers want to implement a new system but rather than buy new db servers for the purpose, they'd like to use existing kit - as consolidation seems to be the direction our company is going in. We are in the process of purchasing new servers which host 64-bit windows 2003 and 64-bit sql 2005.The developers don't really have a requirement as to whether the db servers are 32-bit or 64-bit, but as they want to make use of our kit, their new system will potentially be hosted on 64-bit os/sql 2005. As they haven't done the reseacrh into potential issues, we'll have to do that for them - is there anything we need to worry about? I know there are some issues with SSIS, such as no 64 bit support for Jet Engine data sources, etc. Is there anything else we need to be aware of?Any tips would be appreciated!Thanks,Di |
|
|
gedwards
Starting Member
19 Posts |
Posted - 2008-02-13 : 16:17:26
|
Assuming you are going from 32 bit SQL 2005 to x64 bit -the development environment we use is 32 bit. we have both drivers loaded on the server.If hosting SSAS on the same server - be sure to watch memory usage and try to adjust. Can be battle of the Titans if both are fighting for it. RS works on x64 bit, but be aware that IIS runs in only one mode.SP2 cumulative release 3 works with partitioned cubes. SP2 alone does not. Think they're up to release 5 or so now.Make sure you test - especially with load.Since it can address more memory, see what your options are. I think on the OS side some is related to your version of W2003.Good Luck!Greg EGreg E |
 |
|
|
|
|
|
64-bit SQL 2005 - any gotchas?