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

Similar Messages

In place upgrade Windows 2008 and SQL 2008

Hi all,
We are planning to upgrade to Windows 2012 and SQL 2012 , can we take this in-place upgrade path in the following order ?
Setup 1 Host with 2 VM's running Windows 2008 R2 on Host and Windows 2008 R2/sqL 2008 on VM's.
1. Host1(running 2 VM's) - In-place upgrade windows 2008 R2 to windows 2012 R2
2. VM1 on host1 - In place upgrade windows 2008 R2 to Windows 2012 R2
3. VM2 on host1 - In place upgrade windows 2008 R2 to Windows 2012 R2 (AD Server)
4. SQL running VM1 - In place upgrade SQL 2008 with DB/reporting services to SQL 2012 DB/reporting services
All Servers ( including Host and VM's) are stand alone in a workgroup setup.( except one VM a stand alone AD server by itself).
Thanks for your help.

Hi,
If you want migrate from windows 2008r2 to windows 2012r2, you must install windows server 2008r2 sp1.
http://technet.microsoft.com/en-us/library/dn303416.aspx
For the host 1 upgrade, please refer to the following:
http://blog.powerbiz.net.au/server-2012/in-place-upgrade-from-windows-server-2008-r2-to-windows-server-2012/
For the SQL in-place upgrade, i think you may need to ask in SQL forums:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlservermigration
Hope this helps.
Regards.
Vivian Wang

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

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

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.

Side effect of SQl server upgrade from 2008 R2 to Server 2012, logical name of log file changed for one database

I came to know that name has changed when I tried to shrink the file. Here is the error message I got:
Shrink failed for LogFile "Tfs_TESTTFS_Log'. (Microsoft.SqlServer.Smo)
Additonal information
An exception occured while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.COnnectionInfo)
Could not locate file 'Tfs_TESTTFS_Log' for database 'Tfs_TESTTFS' in sys.database_files. The file
either does not exist, or was dropped. (Microsoft Sql Server, Error: 8995)
This is test environment upgrade and I checked on production environment which is still on SQL 2008R2, shrink works fine.
Please help.

I did in place Upgrade.
Before Upgrade
Logical Names
Database Name: Tfs_TESTTFS
Database Log: Tfs_TESTTFS_Log
After Upgrade
Logical Names
Database Name: Tfs_TESTTFS
Database Log: TfsVersionControl_Log
Thx

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.

Upgrading a DC in place from Server 2008 R2 to Server 2012 R2

This is not a question but more of an information post. I've found lots of posts regarding the upgrade of a DC and most say that you should do a clean install and migrate services and then decommission the old server. But I was more interested in an in-place
upgrade of a DC. I only found one post on here that said it was possible, so I gave it a try and it worked perfectly.
Here's what I've got and what I did:
Server 2008 R2 Std (Virtual Server using VMWare)
AD, DHCP, DNS, Certificate Services, Office KMS Host
I did the whole adprep /forestprep /domainprep routine and then installed Server 2012 R2. I selected the upgrade option and then sat back and watched the process. It took about 30 minutes to complete. Once it had installed, I logged in and the only issue
I noticed was that one service hadn't started, and this was just due to the OS waiting to be activated. Once I had done that there were no more errors/issues.
For the Office KMS server I then had to install the new version of KMS host as this has changed for 2012, and this is quite a simple task too. The only issue I have is waiting for the minimum of 5 PC's to activate...

Yes. That is of course a different situation. however, I would still not do it for acouple of reasons, which may or may not apply to you.
I work in a controlled environment (regulatory requirements) and for any change we need QA approval. Allowed downtime is very low. preparing a new DC and then swapping it out means far less downtime and much easier to manage from a QA perspective. Especially
since you can do a lot of acceptance testing up front.
Upgrades always carry the risk of certain things being reset, or changed unknowningly. Scratch installs are always the same. The possibility that after the QA release something may not work as expected can create a huge problem for me. We always prepare
and test installation procedures up front.
That's why we always try to follow best practices and procedures that allow as much pre-configuration as possible, and which allows us to fall back to existing configuration. Timeslots for downtime come around only once per year. And if it causes more than
a couple of hours downtime, only once every couple of years. the amount of sitewide effort involved and the financial risks are massive.
Basically it all boils down to this: is it a problem for you if somethign unexpected happens, do you have the possibility (time) to do much troubleshooting or the time needed to restore backups, and how acceptable is the risk of not being able to finalize
the proposed changes.
When there are millions of $$ on the line and a schedule slip could cost further hundreds of thousands of dollars ... , and aborting the site upgrade would be a huge failure for the site ... you want stability, predictability, and as few changes
as possible where you don't know the success in advance.

In-Place upgrade of 2008 R2 SP1 server to 2012 - 0x80070490

I'm trying to upgrade one of our fileservers to 2012 from 2008 R2 SP1. It already failed once and I was
forced to rollback to the previous version of Windows. Now, when I try I am continually getting the "Windows Setup cannot find a location to store temporary installation files. To install Windows, make sure that a partition on your boot disk has at least
1198 megabytes of free space".
The C drive has 55GB free, D drive 78GB free and E drive 255GB free.
I've tried running the setup from the command line and using the /tempdrive:<drive> switch to specify
the location the setup should place the temporary installation files but, no matter which drive I choose, I get the same error.
The only other partition is the System Reserved partition which has less than the required space. I
had a look inside this partition (by adding a drive letter to it on a temporary basis) and there is a $WINDOWS.~BT folder which contains the temporary installation files.
Is it safe to run a disk cleanup on the system reserved partition as I suspect that might allow the setup to run?

Hi,
You can perform a disk cleanup check first to see if any temp file will be listed. By default it will only list Recycle Bin in Disk Cleanup result.
If you have any feedback on our support, please send to [email protected]

SCCM 2012 moving site Database server from SQL 2008 R2 cluster to 2012 cluster

Hello,<o:p></o:p>
Using the SCCM 2012 setup, I get
the following errors and then it eventually fails……I’ve been uninstalled and
installed SQL native client .....still unable to move SQL database,i get this error:<o:p></o:p>
*** Failed to connect to the SQL Server, connection type: SMS ACCESS. Configuration Manager Setup 25/02/2015 21:01:03 8624 (0x21B0)
INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure Configuration Manager Setup 25/02/2015 21:01:03 8624 (0x21B0)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted. Configuration Manager Setup 25/02/2015 21:01:07 8624 (0x21B0)
*** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection Configuration Manager Setup 25/02/2015 21:01:07 8624 (0x21B0)
I know that the problem is related to a certificat issue but i didn't arrived to resolve it.

Have a look at this post (pay special attention to the comments):
http://blogs.technet.com/b/configurationmgr/archive/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server.aspx
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

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.

In-place upgrade Windows 2008 to 2008R2 and effects on SharePoint

I have a SharePoint farm, with a WFE running on Windows 2008 64 bit. THe APP and SQL server both use 2008R2. It's a complicated setup, with many custom applications. Rather than a fresh install, we would prefer to maintain our current applications and configuration.
Can I perform an in-place 2008R2 upgrade? Will it affect SharePoint? The Farm?
Backup strategies?
Thanks,
Scott

Hi Scott,
Operating System in place upgrade is NOT supported with SharePoint 2010. It is recommended that building a new Win2008 R2 and restoring a backup of your SharePoint 2010.
For more information, you can have a look at the blogs:
https://social.technet.microsoft.com/Forums/en-US/8c638ca6-0edf-4d5d-a443-3841cb64f673/inplace-upgrade-from-windows-2008-to-2008-r2-breaks-sharepoint-2010?forum=sharepointadminprevious
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

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

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 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.

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

Similar Messages

Maybe you are looking for