Migrating SQL 2008 DB to SQL 2012 for SharePoint Farm

Our SharePoint 2013 Farm runs on ISCSI Disk on Windows 20008 R2 Standard SP1 Platform with SQL 2008 R2 Standard SP2.
Now we are planning to move this ISCSI Disk to another SQL 2012 Standard Platform and then upgrade the SQL 2008 Databse to SQL 2012. Can some one please let me know what challenges we might face during this implementation.

http://technet.microsoft.com/en-us/library/cc512723(v=office.14).aspx
It depends if you want to move all, or just some, of your databases to the new server. If you need to move all of them that link describes the process but in short;
Backup and restore all databases to the new server
Configure the server roles and logins for the SharePoint accounts on SQL
Create (or modify) your SQL alias to point to the new server

Similar Messages

Migrate SQL 2008 Analysis database to 2012 AS database along with data level security defined in current production cube

I want to migrate Analysis Services 2008 database to 2012 AS database along with data level security defined in current production cube
Note: Only Production environment have security, while no security is defined in development environment
Potential Approach:
1 - Using Synchronization Wizard: Gives me error : "The OLAP element at line1 can not appear under envelope......" and this is because Synchrinzation works only for same version
and in my case, there are different versions of SQL (SQL 2008 and 2012)
2 - Using Visual studio conversion wizard - Convert SQL 2008 AS project to 2012 and then process cube, so I can get the cube working but then how can I get data level security since 100's of data level security is defined in production Cube, so how can I
migrate that across
3 - Script out XMLA and deploy cube - But then again having issues with how can i script SSAS security
4 - Would taking backup of SSAS 2008 database and restore to SSAS 2012 will help ?
Any suggestions would be appreciated
Thanks,
Mihir

Hi Mihir,
According to your description, you want to migrate the SQL Server Analysis Services (SSAS) 2008 database which have some security setting with it to SSAS 2012, right? We can migrate existing Analysis Services databases either during Setup, by upgrading an
existing instance of Analysis Services, or after Setup, by running the Migration Wizard. Generally, when migrating a database to another server, all the setting will be migrated. So in your scenario, you can refer to the steps on the links below to migrate
your SSAS database.
How to: Migrate Analysis Services Databases
Migrating Existing Analysis Services Databases
Regards,
Charlie Liao
TechNet Community Support

MIgrate SQL 2008 R2 to SQLExpress 2012

I have a website with a 2008 R @ database. I am trying to move from that host to another host. The new host has 2012 databases. I have a copy of my 2008 database on my local machine that I restore with back-ups from my production DB.
I am having problems migrating the 2008 DB to the 2012. The host had me download SQL Server Express and its Tools. I have a backup file from my local machine but when I try to use it get an error. If I try to copy the database from the 2008 DB
to the 2012, I get an error "
TITLE: Copy Database Wizard
The destination server cannot be a SQL Server 2005 or later Express instance.
But if I try to restore it ot a blank database on the 2012 I get another error_"
TITLE: Microsoft SQL Server Management Studio
Restore of database 'UMDB' failed. (Microsoft.SqlServer.Management.RelationalEngineTasks)
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: The backup set holds a backup of a database other than the existing 'UMDB' database. (Microsoft.SqlServer.SmoExtended)
Can this be done?

Hi Dave,
From your description, you fail to restore a SQL Server 2008 R2 database to SQL Server 2012 Express. I test the scenario as yours, I restore the database from ‘BDUC3.bak’ on ‘UMDB’ database via SQL Server Management Studio (SSMS) and T-SQL in
SQL Server 2012 Express. Everything works as expected.
The error "The process cannot access the file because it is being used by another process" can be caused by several factors. Please make sure that the backup file is not used by other processes. I recommend you copy the ‘BDUC3.bak’ file to SQL
Server 2012 Express backup folder such as C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Backup. In addition, please remove process which are accessing the UMDB database.
With SSMS 2012 GUI, you can perform the steps which are shown in below screenshots.
With T-SQL, you can directly execute the following scripts in SQL Server 2012 Express. Then check if you can restore the database successfully.
USE master;
GO
RESTORE FILELISTONLY
FROM DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Backup\BDUC3.bak'
RESTORE DATABASE UMDB
FROM DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Backup\BDUC3.bak'
WITH replace,
RECOVERY,
MOVE 'BDUC3' TO 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\UMDB.mdf',
MOVE 'BDUC3_log' TO 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\UMDB_log.ldf';
GO
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.

SQL 2008 SP1 to SQL 2008 R2 Upgrade

I have a SQL server running SQL 2008 SP1 and am trying to upgrade to SQL 2008 R2. The server has an installation of SCOM 2007 R2 with CU4 on it with reporting services and SCOM data warehouse
The SQL upgrade advisor runs and tells me that Custom report items were detected on the report server and 3x Custom extensions or assemblies were detected on the report server
If I actually try to run the upgrade I get a 2 failures in the Upgrade Rules check:
No Custom Security Extensions and No Custom Authentication Extensions
I can see that the file rsreportserver.config has the custom entries relating to the scom data warehouse user so it is possible to change this file back to the original config file that was present before installing scom data warehouse and then run the sql
upgrade and then put the config file back?

Hi Mickpell,
Me too facing the same issue while upgrading from SQL 2008 SP1 to SQL 2008 R2. Getting below error:
No Custom Security Extensions and No Custom Authentication Extensions
Did u follow the steps you mentioned and it is Success???. Could you please confirm. If it was success, I can proceed with the same steps. Thanks in advance!!! I am
using SCOM 2007 R2 CU5. Should I download latest Hotfix Utility or CU2 utility is enough???
Regards, Suresh

Reporting Services 2012 for SharePoint and SQL Server Agent "Subscriptions and Alerts"

After installing Reporting Services for SharePoint (Denali) in my test farm, I'm trying to configure the "SQL Server Agent" access for Reporting Services. From Central Admin I'm going to the Reporting Service applicaiton configuration screen and selecting
"Provision Subscriptions and Alerts". I've tried both options on this screen. I've manually executed the "download sql script" in SQL Server, as well as entering a user with SQL sys admin rights on the SQL server into the login fields on the screen.
The role and permissions have been created for the application pool service account, but Reporting Services is still trying to connect with the annonymous login because I'm getting the following alert each time I open the "Provision Subscriptions and Alerts"
screen:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
The "status" on the screen still shows "SQL Server Agent State cannot be determined". Has anyone else seen this?
Thanks!!

Thanks for your reply!
1) Looks like the new Reporting Services does not run as a Windows Service so it's not listed in the "Configure Service Accounts" pulldown. As a result, I don't see how to set the service account. It's only assigned to an application pool.
I installed it into an existing application pool and that application pool "is" in the list and has a domain service account already assigned.
2) Which users need to be in here in order to configure the "Provision Subscriptions and Alerts" screen? I already have the farm admin account which is the account I use when running Central Admin.
3) As mentioned in #1, I've installed Reporting Services into an existing application pool with other service apps.
4) This link is for Reporting Services 2008 R2 which is very different install process. But I did follow the SQL Server Reporting Services 2012 RC0 installation instructions and the Reporting Services is functioning correctly with no errors.
I'm just not able to configure the sceduling the alerting with interfaces with the SQL Server Agent.
Thanks!

Upgrading SQL 2008 R2 to SQL 2012 SP1

Hi everyone,
We are testing some upgrades in a lab environment. We have upgraded to SCCM 2012 R2 and are now looking at upgrading to SQL 2012 SP1 from SQL 2008 R2. Both SCCM and SQL are on one server. (The next step is to split SCCM and SQL but that's another topic)
The question we are asking is, what should be our process for the upgrade? Do we need to stop SCCM services before doing the SQL upgrade? If, so, which ones?

Hi,
You need to stop all Configuration Manager services at the site.
For the process of the upgrade, you could check the following document.
http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigUpgradeDBSrv
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Upgrade FIM 2010 R2 Sp1 Databases from SQL 2008 R2 to SQL 2012

Hi,
I want to upgrade my SQL from 2008 R2 to SQL 2012.
FIM Databases
1) FIMService Database
2) FIMSynchronizationService Database
Mentioned above are my FIM databases running on SQL server 2008 R2 . Now I was looking for some article which could tell me if SQL can be upgraded without affecting my existing databases of FIM or if i can move these databases to a new server having SQL
2012
Activity I want to perform : Create a fresh Server of SQL 2012 and move my FIM 2010 databases over it by restoring the backups. but as per the link below it seems not possible!
http://social.technet.microsoft.com/wiki/contents/articles/5465.fimilm-how-to-move-the-backend-sql-server-synchronization-service-database.aspx

Hi Shivam,
Please take a look here: Release Notes for Forefront Identity Manager 2010 R2 SP1.
In the table you have tasks to upgrade SQL for FIMService and FIMSych.
FIM Service:
Upgrade FIM Service servers to FIM 2010 R2 SP1
Stop FIM Service on all servers
Backup Database [in case rollback needed]
Upgrade SQL to SQL Server 2012
Start FIM Service on all servers
FIM Synch:
Upgrade FIM Sync to FIM 2010 R2 SP1
Stop FIM Sync
Backup Database [in case rollback needed]
Upgrade SQL to SQL Server 2012
Start FIM Sync
If you are not making in-place upgrade, I would do something like here:
Stop FIM Services
Backup the databases at SQL 2008
Restore backed up databases on SQL 2012
Make sure SQL Agent Jobs are moved (FIMService)
Make sure Broker is enabled on FIMService database
On FIM machines create SQL alias using cliconfg utility. Alias should have the name of "old(sql2008) SQL" and point to new name/instance.
Start FIM Services - they would use "old" name to connect, but it would be translated to new location. So they would start.
If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

Linked Server from SQL 2008 to Connect to 2012 read only replica never works

I have two Production Database Servers
1. SQLServer2008 (2 Nodes Cluster)
2. SQLServer2012 with 2 read only replica (3 Nodes Cluster)
I would like to draw a line here, We have routing table and URL working perfectly fine.
We have tested LINKED Server from 2012 Box to production Server by Specifying APPLICATIONINTENT = ReadOnly; it works perfectly fine, the routing is being used.
When we create linked server from SQL Server 2008 Box (Please note we have installed SQL Server 2012 Client tools on this box and Restarted the Servers) using the below script
USE [master]
EXEC master.dbo.sp_dropserver @server=N'AGL1', @droplogins='droplogins'
GO
EXEC master.dbo.sp_addlinkedserver @server = N'AGL1'
,@datasrc='AGL1'
,@provider='SQLNCLI11'
,@provstr='ApplicationIntent=ReadOnly;Database=AdventureWorks2012'
Linked Server is created, Now when I run the Query
exec ('select @@servername') at AGL1
It always brings the Primary READ/WRITE node name only, after lots of research I found that, this linked Server is always using SQL Native Client 10.0 only, even after creating Linked Server using SNC 11, That is the reason it is not going to routing
table. Its always connecting to Primary node.
Below is the way I found it, on 2012 Production Server I executed below Query
SELECT session_id, protocol_type, driver_version =
CASE SUBSTRING(CAST(protocol_version AS BINARY(4)), 1,1)
WHEN 0x70 THEN 'SQL Server 7.0'
WHEN 0x71 THEN 'SQL Server 2000'
WHEN 0x72 THEN 'SQL Server 2005'
WHEN 0x73 THEN 'SQL Server 2008'
ELSE 'SQL Server 2012'
END,client_net_address ,client_tcp_port,local_tcp_port ,T.text
FROM sys.dm_exec_connections
CROSS APPLY sys.dm_exec_sql_text(most_recent_sql_handle) AS T
The help is taken from msdn (Link Provided below) for the above Query
https://msdn.microsoft.com/en-us/library/dd339982.aspx
and I found it always uses SQL Server 2008 SNC.
My Question is, is there a way to force SQL Server to use SQL Server Native Client 11.
Has anyone tried this setup?
Thank you in advance.

Unfortunately no, there is no other way of forcing it without restart. The SQL Server stack has no idea of the existing Native Client as it booted prior its installation. And you cannot force "DLL reload" without proper service restart.
Ivan Donev MCT and MCSE Data Platform

Adding a custom rendering extension to SQL Server Reporting Services 2012 for SharePoint 2010 integrated mode

We are attempting to add OfficeWriter report rendering extensions for SSRS 2012 in SharePoint (2010) integrated mode through powershell. The documentation for “New-SPRSExtension” is rather
sparse and we have not found any clear examples on the internet. With SSRS 2012 in native mode, we make the following two changes to the config files:
We add the following report rendering extension declaration to
RSReportServer.config:
<Configuration>
    <Extensions>
<Render>
<Extension Name="XLTemplate" Type="SoftArtisans.OfficeWriter.ReportingServices.ExcelTemplateRenderer,
SoftArtisans.OfficeWriter.RS2008"/>
<Extension Name="WordTemplate" Type="SoftArtisans.OfficeWriter.ReportingServices.WordTemplateRenderer,
SoftArtisans.OfficeWriter.RS2008"/>
</Render>
    </Extensions>
</Configuration>
We add the following security trust codegroup to
RSSvrPolicy.config:
<configuration>
    <mscorlib>
<security>
<policy>
<PolicyLevel version="1">
  <CodeGroup version="1" PermissionSetName="Nothing">
  <CodeGroup
                          version="*"
                          PermissionSetName="FullTrust"
                          Name="SoftArtisans_OfficeWriter_Strong_Name"
                          Description="This
code group grants SoftArtisans OfficeWriter code full trust.">
                      <IMembershipCondition
                          class="StrongNameMembershipCondition"
      version="*"
      PublicKeyBlob="00240000048000009400000006020000002400005253413100040000010001004779CB207F11
      5E86EF9DD3233F9F130F8891911345176650F72330F84CA3F54C96DEB08439680660F02872EEF5DA3955
      A14C63F96E57DFB71B1535280C37DA2CB5BA37D78A9882414DB11F67FD66DEBC4AD93DD34F4A587D34D
      B4D23D9C6AF83431D88A7EF42BB01082913F3560DCB50129C5BBA7ECA0DE8BC286DA74F58FADE"/>
</CodeGroup>
</CodeGroup>
</PolicyLevel>
    </policy>
</security>
</mscorlib>
</configuration>
What would be the equivalent syntax for “New-SPRSExtension” to do the above for SSRS 2012 in SharePoint (2010) integrated mode?
Alison Bird SoftArtisans Technical Services www.softartisans.com

Hi Alison,
Unlike the deployment of other custom extensions such as custom delivery extension and data processing extension, it is not necessary to add a code group for the custom assembly that grants FullTrust permission for the extension during the deployment of
custom rendering extension. If you have copy the custom assembly to the %ProgramFiles%\Microsoft SQL Server\MSRS11.<InstanceName>\Reporting Services\ReportServer\Bin folder, and modify the RSreportserver.config file to add the extention entry properly,
please open the SSRS Service Application created on the SharePoint and verify that your extension is included in the list of available export types for a report.
Reference:
Deploying a Rendering Extension
Regards,
Mike Yin
TechNet Community Support

SCOM 2012 R2 database in-place upgrade SQL 2008 R2 to SQL 2012

Hello,
I intend to upgrade my SCOM SQL 2008 R2 environment to SQL 2012. I have (of course) an OPS, DWH and Reporting Services instances/databases.
When I run the Update Advisor I run in to several issues.
Has someone had experience with an in-place SQL update?
Help would be appreciated.
Greetings,
Pim
SCOM Administrator

have a read at this detailed post by one of the MVPs
http://thoughtsonopsmgr.blogspot.sg/2013/01/om12-sp1-upgrading-sql-server-2008-sp1.html
Blog: http://theinfraguys.com
Follow me at Facebook
The Infra Guys Facebook Page
Please remember to click Mark as Answer on the answer if it helps you in anyway

SQL Server Reporting Services Add-In for SharePoint not installing properly

Environment: Windows Server 2008R2, SQL Server 2012, SharePoint 2013 Enterprise
When I run the install for SQL Server 2012 Reporting Services Add-in for SharePoint it SHOULD install to c:\program files\common files\Microsoft Shared\Web Server Extensions\14 AND 15. Specifically it should drop a mess of ASPx pages for admin to the \templates\Admin\ReportServer
folder. In this environment it only pushes them to the 14 folder and not the 15. Any ideas on why this would happen? I have not ever seen this before and it is hosing the install completely.

Hi Gouranga,
According to your description, when you install the SQL Server 2012 Reporting Services Add-in for SharePoint 2013, you find the files are installed into the folder for sharepoint 2010(..../14). Right?
In Reporting Services, Not all features are supported in all combinations of report server, Reporting Services add-in for SharePoint, and SharePoint Products. Please see the linke below:
Supported Combinations of SharePoint and Reporting Services Server and Add-in (SQL Server 2012)
As you can see in the link, the SQL Server 2012 Reporting Services Add-in is only for Sharepoint 2010. This the reason why it's installed into the file for sharepoint 2010.
Reference:
Where to find the Reporting Services add-in for SharePoint Products (SharePoint 2010 and SharePoint 2013)
Install or Uninstall the Reporting Services Add-in for SharePoint
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

SQL 2008 R2 error: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified

after some year work with SQL server 2005,i decide change to SQL server 2008 R2.
When i completed install SQL 2008 R2,i can't connected to SQL server due to this following error
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (.Net SqlClient Data Provider)
And when i click to technical details,i take some thing like this
===================================
Cannot connect to HUY-PC\SQLEXPRESS.
===================================
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
Error Number: -1
Severity: 20
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
Please!!!Some body help me solve this problem(except format my computer),i really really need your advice.

Hi huydaibang,
The older version SQL Server 2005 could be installed with SQL Server 2008 R2 side-by-side. It could not be the problem.
The reason that we get this error message is the client stack could not receive SSRP response UDP packet from SQL Browser.
Here are the steps:
1) Make sure your server name is correct, e.g., no typo on the name.
2) Make sure your instance name is correct and there is actually such an instance on your target machine.
3) Make sure the server machine is reachable, e.g, DNS can be resolve correctly, you are able to ping the server (not always true).
4) Make sure SQL Browser service is running on the server.
5) If firewall is enabled on the server, you need to put sqlbrowser.exe and/or UDP port 1434 into exception.
For more information, please refer to
http://blogs.msdn.com/b/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx.
Thanks,
Maggie
Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

How to install sql 2008 r2 in sql 2008

Hi,
I have DB stored in sql 2008. i need to install sql 2008 r2 without db deletion in sql2008. please let me know which option i should choose and clear solution to me.
Thanks,

Hi,
You can install SQl Server 2008 r2 side by side to SQL Server 2008 Microsoft supports this scenario. I would like you to read
This article before proceeding .
If you just want to move database from SQL server 2008 to SQL server 2008 r2 backup the database from 2008 and restore it on 2008 r2. Make sure you map orphaned users to logins
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

SQL Server for SharePoint farm

Hi All,
As per the best practice to setup the farm, SQL Server shouldn't be a physical machine instead of Virtual. I am wondering what is the reason behind it?
If we do setup the farm in Azure then will it be ok to use the VM for SQL Server since SharePoint doesn't support Azure SQL Server?
Regards Restless Spirit

Generally, for On-Premise, many organizations do not support or allow IT departments to virtualize database servers. This policy is typical in organizations that have dedicated database teams that tightly manage and maintain SQL Server. In these controlled
deployments, the database team has to create all databases. Virtualizing SQL Server is not an option
In Azure IASS, SQL VMs are supported
http://download.microsoft.com/download/8/7/6/876E7EBF-47ED-488D-A861-13A020EB40BD/SharePoint%202013%20on%20Windows%20Azure%20Infrastructure_v1.pdf
Please mark the replies as answers if they help or unmark if not.

IP addresses are going to be changed for SharePoint farm servers(App, WFE, DB)

Hello,
We had multiple SharePoint Farms, and we would like to changes the IP address of all the servers in farm(because of changing the Datacenter). will I get any issues, if, how can I take it forward. Need suggestions.
Thank You
NARLA

As Vivek says it won't break anything, as long as you fix DNS.
SharePoint checks the database server by server name or alias, which both use the computer name, so no IP addresses are directly used there.
So these should be the steps:
1. Change your DNS records to point to the new IP address for all Web Applications
2. Change the IP addresses for the SQL Server and SharePoint
3. Check IIS on your SharePoint Server(s) to see if the new IP address is correctly configured for all Web Applications on all the servers in your farm.
4. Test everything :)
Happy SharePointing!
Nico Martens
SharePoint/Office365/Azure Consultant

Migrating SQL 2008 DB to SQL 2012 for SharePoint Farm

Similar Messages

Maybe you are looking for