Hi, Need more coffee this morning... I always use named instances of SQL and is is the local alias not the AD one as I was think about something else at the time..
>From http://technet.microsoft.com/en-us/library/cc512725.aspx · If you are using a named instance of SQL Server, you must create a SQL Server connection alias that can be used by all servers (including the front-end Web servers and application servers) to connect to the instance of SQL Server. A connection alias is an alternative name that you can use to make a connection to an instance of SQL Server. Note: The first link is a cached page as the site is down. http://cc.msnscache.com/cache.aspx?q=%22http+thomasvochten+be+blog+post+2009+03+19+using+sql+aliases+with+sharepoint+aspx%22&d=75913118951083&mkt=en-AU&setlang=en-AU&w=7ae3a2f8,3cacf4fe http://codeprostitute.com/2009/01/23/using-sql-alias-for-failover-with-sharepoint-sps-2007/ http://dirkvandenberghe.com/archive/2009/03/23/using-sql-aliases-with-sharepoint-by-thomas-vochten.aspx Regards Jon Bullen From: [email protected] [mailto:[email protected]] On Behalf Of Noja, Fadi Sent: Wednesday, 29 April 2009 10:37 AM To: [email protected] Subject: RE: Moving databases to a new SQL server [SEC=UNCLASSIFIED] Yes, it does contain the SQL SID. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Brown Sent: Wednesday, 29 April 2009 10:31 AM To: [email protected] Subject: RE: Moving databases to a new SQL server [SEC=UNCLASSIFIED] Uh, doesn't the database contain the server name, SID, etc of the actual DB serve? Simply making a the server name in AD/DNS to point to the new one wont really make it work correctly and has the potential to cause some issues? From: [email protected] [mailto:[email protected]] On Behalf Of Jon Bullen Sent: Wednesday, 29 April 2009 9:52 AM To: [email protected] Subject: RE: Moving databases to a new SQL server [SEC=UNCLASSIFIED] May I recommend that you make a alias in AD for the server and use that instead. That way and future DR or server moves involve updating the alias and not having to rename the server in SharePoint. Regards Jon Bullen | Senior Consultant | Microsoft Services [cid:[email protected]] È +61 4 1048 0197 Canberra, Australia | www.microsoft.com/services<http://www.microsoft.com/services> MSN IM: [email protected]<mailto:[email protected]> This email is intended solely for the use of the addressee and may contain information that is confidential or subject to legal professional privilege. If you receive this email in error please immediately notify the sender and delete the email. Please consider the environmental impact before printing this email. From: [email protected] [mailto:[email protected]] On Behalf Of Noja, Fadi Sent: Wednesday, 29 April 2009 9:34 AM To: [email protected] Subject: RE: Moving databases to a new SQL server [SEC=UNCLASSIFIED] Here's how to do it http://technet.microsoft.com/en-us/library/cc288554.aspx Fadi ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Zelda Leung Sent: Wednesday, 29 April 2009 8:45 AM To: [email protected] Subject: Moving databases to a new SQL server Hi all, We've recently acquired a new SQL Server for our SharePoint databases, and now need to move those databases for our development site from the old SQL server to the new SQL server. The process seems to be fairly simple on face value, but does anyone have a website/list of "must do"s and "should know"s? Thanks, Zelda Zelda Leung Principal Developer | IT Services | Legal Aid Queensland p 3238 3626 | 44 Herschel Street DISCLAIMER: The contents of this email (including any attachments) are confidential and privileged and are intended only for the addressee. Any confidentiality or privilege is not waived or lost because this email has been sent to you by mistake. Any unauthorised use of the contents of this email is expressly prohibited. If you receive this email in error, please contact us, then delete the email. Emails may be interfered with, may contain computer viruses or other defects and may not be successfully replicated on other systems. We give no warranties in relation to these matters. If you have any doubts about the authenticity of an email purportedly sent by us, please contact us immediately. ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists -------------------------------------------------------------------------------- Support procedure: http://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
<<inline: image001.gif>>
