Greetings: I was hoping someone would be able to help me with moving my SCE databases from one remote SQL server to another. The existing database server is full version SQL 2005 Standard, however, the hardware is underpowered as it handles other functions besides the SCE databases. So I now have a more high-powered 64-bit SQL 2005 server available and want to move the SCE databases from the old database server to new one. As recommended/required, SQL reporting services is installed locally on my SCE server, however, it's backend database is also on the original 32-bit SQL server. I would like to move this database as well, but that is not absolutely necessary if I can get the "SUSDB", "OperationsManager", and "OperationsManagerDW"databases moved from the 32-bit server to the 64-bit server. Does anyone know of any KB articles, blogs, online docs, or other sources that walk through (or at least outline) the process of moving SCE databases from one remote server to the other? I am reasonably confident I can actually move the databases themselves on my own (though if anyone know of any issues when porting from 32-bit to 64-bit, please feeel free to bring them to my attention!!).... what I am clueless about is how to modify the configuration of SCE to point to the new database locations. Thanks in advance for any help provided! Keith Jakobs

Hi Keith, Thanks for your update. In this scenario, I am sorry to sayit is the supported architecture by design and may not upgrade currently. As a work around, you can install 64-bit SCE or 32-bit remote SQL server. Thanks for your understanding.

Hello Jie-Feng, I am sorry, but that is not a "workaround." That is just another way of saying Microsoft will not support the configuration, contrary to published documentation. 64-bit SCE is not an option. For one, as I mentioned, I only have one 64-bit physical system, which is dedicated to supporting database functionality. It will not be co-mingled with other services - this is my current problem. The second issue, as I stated, is that my SCE is a virtual system, and Microsoft Virtual Server does not support 64-bit OS. Microsoft really needs to get a clue here. I feel like I am dealing with a third party when it comes to support for System Center products. Documentation is inconsistent and erroneous. Microsoft refuses to follow through on stated support configurations. Most installation documentation is based on 'test' scenarios, and as soon as you start trying to follow best practices in a production environment, everything starts breaking, such as: - Lack of support for AGLP group membership models - Lack of support for dedicated remote SQL servers unless specific unpublished configurations are followed, including duplicate drive letters on SCE servers, and manual registration of SPN's. - and now this cross-platform support issue is just a bunch of flack telling me Microsoft really doesnt care about makin usable products anymore. The amount of resources this product consumes is staggering, yet the ability to distribute those resources is appalingly restricted. Guess it is time to go back to SiteScope and Nagios. -claims of support for reduced prvilege functionality are espoused everywhere, but there are so many exceptions depending on which O/S you are monitoring, or which MP you are using, that the practical truth is you really needfull domain admin permissions for most of your SCE/SCOM accounts, unless you have a pristine environment - which no one has. Plus it took months for MS to even support the products in the Partner forums!!! I cannot relate how many times the 'Operations Manager' newsgroup refused to even answer questions about SCOM 2007, months after it was released!!! The end result - the unofficial blog sites wind up being the best resource for information. Way to go MS! It's bad enough we have to wait for people on the other side of the world to reply to newsgroup posts (even in Partner Newsgroups) - why not just start making consumers look elsewhere for their help... while they're at it - maybe they will embrace a new O/S vendor. Sorry Microsoft.... this (and Operations Manager 2007) has to be the most pitiful product release fiasco I have seen MS execute. I think this is an excellent example of how the 64-bit architecture will be the beginning of the end for Microsoft. Keith Jakobs