HI we have mirrored (for testing purposes) our 2007 SP running 64bit live server to another server, however we have disabled all the services and web apps to stop querying the old database(32bit) which is already been queryed by the actual server. My problem is how to detach the new mirror from accessing the old database and restore all the databases on to a new db server with 64 bit OS

I suggest you check out Move all databases (SharePoint Server 2010). "Note that moving databases makes all farm sites and assets unavailable to users until the process is completed." The solution relies on the use of SQL Aliases to "point" your SharePoint servers to your new 64-bit DB server. Let us know if you need further information.Benjamin Athawes MCTS & MCITP SharePoint 2010 Microsoft Community Contributor 2011 Follow me on Twitter SharePoint Blog

hi thanks for the reply, the article points to 2010 SP and ours is 2007 SP, do the rules apply the same way? also i want to only disconnect the test server from live DB and point to a new db server. will the live still be able to query they old db server?

The 2007 article is at http://technet.microsoft.com/en-us/library/cc512725(office.12).aspx. I'm not sure what you were trying to achieve by adding the "test" server to your live farm. If you are planning on scaling out by adding a new SharePoint server AND upgrading the database server my suggestion would be to take a step by step approach rather than doing everything in one go. Personally, I would start by taking this approach to test the database move only: 1. Remove "test" server from production farm using the SharePoint Product and Technologies Configuration Wizard (stopping services isn't enough; you need to remove the server from the farm). 2. Create a new two-server "test" farm so as to match live: 1 SharePoint server and 1 32-bit DB server. 3. Set up a "test" 64-bit DB server. 4. Follow the "Move all databases (Office SharePoint Server 2007)" process linked above to simulate the DB migration. Assuming all goes as planned you can follow the same process to migrate your live databases. You could then take a similar approach to validate further scaling by (for example) adding a second Web server to your "test" farm before deploying the changes to live. Note that you may run into issues moving the SSP to your new DB server. I documented my experience of this procedure on my blog if you are interested: http://mossblogger.blogspot.com/2009/10/migrating-to-new-sql-server-in-moss.html Benjamin Athawes MCTS & MCITP SharePoint 2010 Microsoft Community Contributor 2011 Follow me on Twitter SharePoint Blog

Hi Thanks for all the help. I have one final doubt I have decided to just use alias name feature on my MOSS server to point the MOSS server to the new sql server with no more modifications. however I will just copy all the db's in the live server and restore them on the new server. will this Hack work with no more modifications? i think it should because we are just illusively cheating MOSS to send requests to our new DB server. please help!

Likki, you were given a 2010 article, because this is the 2010 forum. 2007 questions go in the pre-2010 forum, so please use the appropriate forum in the future. I'll move the thread now. As a side note, are you intentionally adding all that white space between paragraphs? Please don't do that - it's wasting a ton of space. Thanks!SharePoint Architect || Microsoft MVP || My Blog Planet Technologies || SharePoint Task Force