Same here, done this before. Switch off your SharePoint server, detach DBs, move them to the new server and attach them, fix up account security on new SQL Server, attach databases and create a SQL client alias on your SharePoint server. It can take a few hours, depends how big your DB files are and how long it takes to copy them all to the new server, ask for an entire system outage for a few hours as you work through this. Yes it renders the old SQL Server inaccessible from your SharePoint server, which might be fine in *most* cases. You could maybe try creating yet another new SQL Alias to your old server to make it accessible, which will be messy and confuse the hell out of anyone, and could potentially lead to hilarious consequences :)
Sezai. 2011/6/1 Joshua Haebets <jos...@beyondurban.com> > I have done the SQL Aliasing method several time. Really easy and very > quick. Only concern is if the original SQL server is still being used and > you need to access DB's on it using BDC / BCS for example. > > > > Cheers > > > > Josh > > > > > > *From:* ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] *On > Behalf Of *James Boman > *Sent:* Wednesday, 1 June 2011 3:04 PM > > *To:* ozMOSS > *Subject:* RE: moving dbs > > > > I have used the STSADM -o renameserver method with some success, because > from what I remember you can't use the SQL alias method if you are using the > default instance of a SQL Server. I though you had to have installed > against a named instance to be able to create the SQL alias properly. > > > > Thus for installations already using the default instance of a SQL Server > the STSADM -o renameserver was the best approach. > > > > My memory is a bit rusty on this - so am happy to be corrected if wrong. > > > > Cheers, > > James. > > > ------------------------------ > > James Boman ■ Telephone: +61 (08) 7200 1100 ■ Mobile: +61 (0) 417 857 298 > ■ Web: http://www.ipmo.com.au || http://www.projectserver.com.au > > > > *From:* ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] *On > Behalf Of *Jason Taylor > *Sent:* Wednesday, 1 June 2011 1:47 PM > *To:* ozMOSS > *Subject:* RE: moving dbs > > > > Not a DNS alias, a SQL Server alias. You configure this using the program: > cliconfg.exe. Just copy this into the Windows Run box then "Alias" tab to > configure using a TCP connection. > > > > *From:* ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] *On > Behalf Of *Chris Grist > *Sent:* Wednesday, 1 June 2011 1:43 PM > *To:* 'ozMOSS' > *Subject:* RE: moving dbs > > > > So this would just be a DNS Alias? > > > > *From:* ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] *On > Behalf Of *Jason Taylor > *Sent:* Wednesday, 1 June 2011 12:30 PM > *To:* ozMOSS > *Subject:* RE: moving dbs > > > > A while ago we had this situation of moving to another server. We ended up > using a more simple approach and just created a SQL Server database alias > using the old server as the alia name and the new server as the server name. > Since then we install SharePoint using a database alias so we never have to > deal with this again. > > > > *From:* ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] *On > Behalf Of *Chris Grist > *Sent:* Wednesday, 1 June 2011 12:15 PM > *To:* ozMOSS > *Subject:* moving dbs > > > > Hi All, > > Has anyone been through this process: > http://technet.microsoft.com/en-us/library/cc512725.aspx > > How long did it take you and any thing to be aware of? > > > > *Chris Grist > *MCITP, MCTS, VCP > > Senior Technical Consultant > > *[image: Description: > http://lftzm01.loftusit.local:80/home/chr...@zimbra.loftusit.com.au/Briefcase/image001.gif] > * > Ground Level > 175 Fullarton Rd > Dulwich SA 5065 > > t: (08) 8304 8888 > f: (08) 8364 2910 > m: 0432 898 500 > > NOTE: This email and any files transmitted with it are confidential and may > contain information intended only for the addressee(s). If you have received > this communication in error, you must not copy or distribute any part of it > or otherwise disclose its contents to anyone - please notify Loftus IT > immediately. Loftus IT does not accept liability for any errors or omissions > in the information provided herein. No representation is made that email and > any files transmitted with it are virus-free - virus scanning is the > responsibility of the recipient and is recommended. > > > > > SAGE is the first and only Australian company certified to the global > benchmark standards of the Control Systems Integration Association. To see > how this benefits you, simply visit www.controlsys.org > ------------------------------ > > Disclaimer: The information contained in this e-mail is intended only for > the use of the person(s) to whom it is addressed and may be confidential or > contain legally privileged information. If you are not the intended > recipient you are hereby notified that any perusal, use, distribution, > copying, modification or disclosure is strictly prohibited. If you have > received this e-mail in error please immediately advise us by return e-mail > and delete the document without making a copy. No warranty is made that any > attachments are free from viruses. It is the recipient's responsibility to > establish its own protection against viruses and other damage. > > > SAGE is the first and only Australian company certified to the global > benchmark standards of the Control Systems Integration Association. To see > how this benefits you, simply visit www.controlsys.org > ------------------------------ > > Disclaimer: The information contained in this e-mail is intended only for > the use of the person(s) to whom it is addressed and may be confidential or > contain legally privileged information. If you are not the intended > recipient you are hereby notified that any perusal, use, distribution, > copying, modification or disclosure is strictly prohibited. If you have > received this e-mail in error please immediately advise us by return e-mail > and delete the document without making a copy. No warranty is made that any > attachments are free from viruses. It is the recipient's responsibility to > establish its own protection against viruses and other damage. > > _______________________________________________ > ozmoss mailing list > ozmoss@ozmoss.com > http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss > >
<<image001.gif>>
_______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
