SCCM 2012 on SQL 2008 R2 cluster

Looking Positive and negative for SCCM 2012 SQL cluster configuration. I am looking for configuration for sql 2008 cluster.
can you any configured ? is yes please step by step configuration and preservative

positive: obviously, the SQL could have high availability and will auto fail over to another box if one of the boxes is down.
Juke Chou
TechNet Community Support

Similar Messages

SCCM 2012 - Migrating SQL components to cluster including Reporting Services

Current SCCM 2012 environment:
- CAS with database on remote SQL (non-cluster) server in a named instance - SQLSRV\CASINST
- SQL Reporting Services in also installed in the SQLSRV\CASINST instance
- The SCCM Reporting Services Point role is installed on the SQLSRV\CASINST instance
- Primary server with database on the same remote SQL (non-cluster) server in a different named instance - SQLSRV\PRIINST
Now I would like to move all of the database stuff to an existing SQL 2008 R2 cluster (SQLCLUSTER) and decommission the SQLSRV server. SQLCLUSTER already exists and the default instance is already in use (for other applications) for both database engine
services and reporting services.
From my understanding:
- SQL 2008 R2 Reporting Services cannot be clustered
- Best practise is to install Reporting Services Point on a remote site server rather than a CAS server
- SSRS can be installed on nodes in SQL cluster as standalone installs - with the caviat that they don't use instance names already in use
So I plan to:
- Move CAS database to new named instance on cluster eg SQLCLUSTER\CASINST
- Move primary database to new named instance on cluster eg SQLCLUSTER\PRIINST
- Install SQL Reporting Services on one of the cluster nodes (unclustered) using a named SSRS instance eg SQLCLUSTERNODE1\SCCMREPORTING
- This article points out some interesting results of not have a default instance - http://magalhaesv.wordpress.com/2012/05/24/system-center-configuration-manager-x-sql-server-reporting-services-x-wmi-english-version/
- Move Reporting Services Point from SQLSRV\CASINST to the cluster node eg SQLCLUSTERNODE1\SCCMREPORTING
I have read on some forums (eg
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/40ad0cb4-a464-4576-b824-957ed6e1b2e2) things like '' If you have an app like SCCM that requires a default instance of SSRS, you are out of luck if your cluster already has a default
instance of the database engine.", but I cannot find this anywhere in Microsoft documentation. From the MS documentation (http://technet.microsoft.com/en-us/library/7fd0d4f5-14e0-4ec7-b2e6-3b67487df555#BKMK_InstallReportingServicesPoint)
I understand that as long the current user has read access to WMI on the remote site server where SQL Reporting Services is installed, you should be able to use a named instance for SQL Reporting Services and successfully install the Reporting Services Point
on it.
So a 2 part question:
- Anybody see any obvious flaws in my high level plan?
- Anybody care to comment on the SCCM requiring a default instance of SSRS?
My Microsoft Core Infrastructure & Systems Management blog -
blog.danovich.com.au

Yes, I know this is an old post, I’m trying to clean them up, Did you figure this out, if so how?
http://www.enhansoft.com/
Hi Garth,
Yes we moved the DBs and RS as outlined above. As expected, we needed to have a default instance of RS because otherwise the SCCM console doesn't see the Reporting Services instance when you try to deploy the Reporting Services site role.
So the above plan worked.
My Microsoft Core Infrastructure & Systems Management blog -
blog.danovich.com.au

SCCM 2012 and SQL 2008 R2 Sync problems

Hi
I installed 2 servers for SCCM 2012:
-1 with SCCM 2012, FEP, WSUS console admin
-1 with SQL Server 2008 R2 complete install, WSUS complete install
When I made or the system mades the synchronization, it shows this error in SMS_WSUS_SYNC_MANAGER:
Error 6703:
WSUS Synchronization failed.
Message: Failed to sync some of the updates.
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates.
And in the wsyncmgr.log appears:
sync: SMS synchronizing updates, processed 3336 out of 3368 items (99%), ETA in 00:00:06 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:14:11.663+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3360 out of 3392 items (99%), ETA in 00:00:06 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:15:11.669+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3383 out of 3415 items (99%), ETA in 00:00:07 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:16:13.206+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3412 out of 3444 items (99%), ETA in 00:00:07 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:17:14.152+300><thread=4640 (0x1220)>
Synchronized update 3a572bd0-5976-4abc-b2d8-955008c5466f - Definition Update for Microsoft Security Essentials - KB972696 (Definition 1.131.558.0). $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:17:18.227+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3446 out of 3463 items (99%), ETA in 00:00:04 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:18:14.400+300><thread=4640 (0x1220)>
Synchronized update 3eeb75c2-81aa-4cc0-9b7a-237a6a0bf737 - Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.131.574.0). $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:18:47.964+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3482 out of 3484 items (99%), ETA in 00:00:00 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:19:15.587+300><thread=4640 (0x1220)>
Synchronized update 74e86346-9384-4304-9625-2c865738c552 - Definition Update for Microsoft Endpoint Protection - KB2461484 (Definition 1.131.574.0). $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.659+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3508 out of 3508 items (100%) $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.662+300><thread=4640 (0x1220)>
Sync failures summary: $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.664+300><thread=4640 (0x1220)>
Failed to sync update 1ba2d28f-75fe-49d7-9cb4-cd39b8706f48. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate $$<SMS_WSUS_SYNC_MANAGER><07-24-2012
09:20:05.666+300><thread=4640 (0x1220)>
Failed to sync update 8a042978-e6d7-4ae6-b3ab-687d8f9bcd9c. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate $$<SMS_WSUS_SYNC_MANAGER><07-24-2012
09:20:05.669+300><thread=4640 (0x1220)>
Failed to sync update a3aff37b-ad3b-4dde-9464-767a516c76e5. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate $$<SMS_WSUS_SYNC_MANAGER><07-24-2012
09:20:05.671+300><thread=4640 (0x1220)>
Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.421+300><thread=3536 (0xDD0)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=GDVSCCM1.gdar.local SITE=CRP PID=1908 TID=3536 GMTDATE=mar jul 24 14:20:06.423 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates"
ISTR1="Failed to sync some of the updates" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.425+300><thread=3536 (0xDD0)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.501+300><thread=3536 (0xDD0)>
Setting sync alert to active state on site CRP $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.503+300><thread=3536 (0xDD0)>
Updated 173 items in SMS database, new update source content version is 36 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.526+300><thread=3536 (0xDD0)>
Set content version of update source {6A4B4446-1B80-4CF4-838D-405D3847A8E3} for site CRP to 36 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.572+300><thread=3536 (0xDD0)>
Sync time: 0d00h19m46s $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.575+300><thread=3536 (0xDD0)>
Wakeup by SCF change $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 10:00:06.651+300><thread=3536 (0xDD0)>
Next scheduled sync is a retry sync at 24/07/2012 10:20:06 a.m. $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 10:00:11.940+300><thread=3536 (0xDD0)>
Why is this behavior?
Thanks
Doc MX

Hi
Today I think I discovered what was the problem:
I used an user in the domain for deploying the role of SUP, but I forgot to put that user in the group of SQL Admins of the SQL Server.
I done that and after reseting the servers, the error for sync with SQL didn't appear again, al least from this morning until now, before this change every hour showed the error 6703.
Thanks to all for your comments.
Doc MX

How to add a new instance to a 2 node SQL 2008 R2 Cluster under the same networkname

Hello All,
I'm fairly new to sql and have just deployed a new 2 node SQL 2008 R2 cluster.
During installation, I created a networkname SQLCLU and a named instance I01.
I now would like to add another Instance (I02) under the same networkname.
What is the proper procedure to do this?
I don't believe that I should do this using the action: "New SQL Server failover cluster" from the setup menu, but rather using the action "New Installation or add features to an existing installation"
With the second option, I'm however not sure how I should make this instance clustered..
Should I also execute the "New Installation or add features to an existing installation" action on the 2nd node in the cluster?
Many thanks for your advice!
Filip

You cannot use the same network name for 2 instances. You need to use a different network name for the second instance I02
A failover cluster instance contains:
A combination of one or more disks in a Microsoft Cluster Service (MSCS) cluster group, also known as a resource group. Each resource group can contain at most one instance of SQL Server.
A network name for the failover cluster instance.
One or more IP addresses assigned to the failover cluster instance.
One instance of SQL Server that includes SQL Server, SQL Server Agent, the Full-text Search (FTS) service, and Replication. You can install a failover cluster with SQL Server only, Analysis Services
only, or SQL Server and Analysis Services
http://msdn.microsoft.com/en-in/library/ms179410(v=sql.105).aspx

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

Sql 2008 r2 cluster side by side with sql 2012 cluster on Windows 2008 R2

We have a SQL 2008R2 active/passive SQL cluster running on Windows 2008 R2 cluster.
I would like to add a SQL 2012 clustered instance to the same Winows 2008 R2 cluster.
Are there any issues involved having a SQL 2008 R2 clustered instance running side by side with a SQL 2012 instance in same Windows 2008 R2 cluster?
Are there any pitfalls/"gotchas" to watch for with SQL 2012 cluster install?
Thank you so much!

Hello,
Two instances, one SQL Server 2008 and the other SQL Server 2012, side-by-side, is fully supported.
I would like to recommend you to assign a different port (not port 1433) to the non-default instance
to avoid an IP address conflict between both instances.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

XML errors when running specific reports in SCCM 2012, using SQL Server 2008 R2 Reporting Services

I've posted this to the SCCM 2012 forum and only received one response so far that states that this is a known issue that has been discussed before and isn't easy to fix; I was not given any actual solution either. Since this involves SSRS I
thought I would try my luck here as well.
I'm having almost exactly the same problem as is referenced in this article: http://social.msdn.microsoft.com/Forums/uk/sqlreportingservices/thread/587a3319-bc54-4d30-bb3f-bb90a0c6ec50.  When
I try to run either of these reports (Computers with specific software registered in Add Remove Programs; Count of instances of specific software registered with Add or Remove Programs) I receive the XML error shown in the attached screenshot. I'm fairly
sure the problem is the same as the other admin was experiencing and I just need to remove the unprintable characters (of the application name) from the dbo.v_Add_Remove_Program column.
The error references 0xFFFF but I could not find what that exactly translates too, other than it appears to be at the end of the spectrum for Unicode characters. I used the following sql query to search for the 0xFFFF entry, but no results were found:
use CM_UV2
Select distinct
CHARINDEX(cast(0xFFFF as varchar(1)),DisplayName0),
DisplayName0
from
dbo.v_Add_Remove_Programs
Where
CHARINDEX(cast(0xFFFF as varchar(1)),DisplayName0) > 0
When I used the original hex value of 0x28 I get plenty of results returned with "(" in them so the query seems sound. One of the articles I was searching mentioned running the query manually using the Management Studio and looking for strange characters
there but I'm not sure how to do that.
Basically I just need help finding the offending character and removing it. I also need to be able to replicate this for other strings as this looks like an error that will reoccur whenever any new software appears that has weird encoding in the title.
Thank you in advance for any help given.
Über Random

Hi Uber,
This is a known issue that error occurs when running report "Count of instances of specific software registered with Add or Remove Programs" due to non-printable characters for XML. Based on internal research, the hotfix for this issue will be
included in the System Center 2012 Configuration Manager Service Pack 1.
As a workaround, you can remove the nonprintable character populated into the report parameter by referring to the following KB article:
http://support.microsoft.com/KB/914159
Hope this helps.
Regards,
Mike Yin
Mike Yin
TechNet Community Support

Install SQL 2012 sp1 Named Instance on SQL 2008 r2 Cluster

I am attempting to add a 2012 instance to my 2008r2 cluster, but at 'cluster node configuration' step, the drop down for sql server instance name is empty

Hi,
Seems you have worked it out. You can mark the answers accordingly. It will be nice to let thread stay there so other
community members
can benefit from it.
Please let us know if you would like further assistance.
Thanks.
Tracy Cai
TechNet Community Support

SCCm 2012 : Move SQL Database

Hi
I have root domain (domain A) and child domain (B).
I install SCCM 2012 in domain A and use SQL 2012 cluster on domain B. I have a problem with a firewall. I install a new cluster SQL 2012 in root domain (Domain A).
My SCCM use: MP, DP, SUP, WSUS, Deployment Application, Deployment packages, Deploy Hotfix.
My question: It's possible to move SQL 2012 database (SCCM and WSUS) in domain B to domain A? and reconnect SCCM 2012 to database.
Thanks

As long as the computer account is a local admin of the SQL server (of every node as you're talking about a cluster) it should move just fine, especially considering you are moving OUT of the trusted domain and into the same domain.
Simply move the database then re-run SCCM setup. When you do one of the first options you'll get is if you're installing into a new site or "perform site maintenance". Within in that category should be an option to connect SCCM to a
new database, which will do all the work for you.
Quick warning: in the past when using that option I've seen cases where roles have re-installed after I changed the site database, usually the MPs (I'm guessing because they need to reconnect?). So hop into monitoring and watch your logs after
doing this to make sure everything "Settles down".

Moving SCCM 2012 R2 SQL 2014 Database to New Server

Greetings,
I have a SCCM 2012 R2 server with SQL 2014 installed which has been upgraded from SQL 2008 R2. My goal is to separate the SCCM and SQL servers. I am aware that SCCM only supports SQL 2014 if it has been upgraded on new installs, but after installing
SQL 2014 on a new server and importing the database I get an error from the Configuration Manager Setup stating that I must upgrade the SQL server before I can modify the SQL Server configuration.
Does this mean I need to install SQL 2008 or 2012 on the new DB server and from there upgrade to SQL 2014?

Thank you for your reply. We have been having several issues with our current server, and have had performance issues with SQL and SCCM installed on the same server mainly during OSD deployments to several machines at the same time. These servers
wouldn't necessarily need to be separated since we can allocate more resources, but the overall goal is to move our primary site server to a new server running Server 2012 R2 (current server is 2008 R2).
I have tried the site recovery option in the installer where you run the SCCM backup and restore maintenance task and I have renamed the new server to the name of the old server. If I understand correctly, this is the correct method of switching out
a site server machine? I experience the same error as my original post when trying this, but I will try the hotfix Torsten provided as this seems to be the issue I'm having.
Thank you.

SCCM 2012 R2 SQL Database Upgrade Fails : Setup cannot upgrade the ConfigMgr database. Contact your SQL administrator.

Hi Friends,
We have planned to upgrade our SCCM 2012 SP1 infrastructure to SCCM 2012 R2 so we have setup test environment to test SQL database upgrade before doing same in production.
But while testing SQL database upgrade on test machine, it is getting failed with below error.
ConfigMgrSetupWizard.log
ConfigMgrSetupWizard Verbose: 1 : Scripted setup failure handling callback called. Failure: 29.
ConfigMgrSetupWizard Verbose: 1 : Received error [Setup cannot upgrade the ConfigMgr database. Contact your SQL administrator.] from native code.
ConfigMgrSetup.log
ERROR: SQL Server error: [23000][2627][Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of PRIMARY KEY constraint 'ContentDistribution_PK'. Cannot insert duplicate key in object 'dbo.ContentDistribution'. The duplicate key value is (921). :
tr_ContentDistributionNotification_insert
ERROR: Failed to execute SQL Server command: ~-- ~-- Rebuild ContentDistribution tables ~-- ~IF (EXISTS(SELECT TOP 1 1 FROM dbo.SMSData WHERE SMSBuildNumber <= 7900) AND dbo.fnIsSecondary() != 1) ~BEGIN ~ exec spRebuildContentDistribution
@TruncateTables=0 ~END
Failed to create process of SetupWpf.exe.
Can anyone please help to get this resolved.
Thanks.

We found out that there were duplicate entries in the PkgStatus_G and the PkgServers_G tables in the SCCM DB. We identified them, deleted them , and then we were able to run the /TESTDBUPGRADE command and it went through fine. We performed
all of this on a COPY of the PROD DB and then moved the changes in PROD. Hope this helps someone.
- Dave

SQL 2008 R2 Cluster | change Cluster Disks

Hello,
We have a SQL cluster (for SharePoint 2010) consists of two nodes Windows server 2008 R2 & SQL 2008 r2.
The SQL cluster have MSDTC (Clustered) & SQL services, with total four disks:
Quorum Disk
MSDTC Disk
Databases disk
Logs disk.
Now the old SAN will be decommissioned and new LUNs have added to replace the our disks above. I managed to change Quorum & MSDTC. I used the below robocopy command to copy databases and logs with the same folder structure and permissions:
robocopy t:\ l:\ /E /MIR /SEC /COPYALL /V
I stopped SQL services then swapped drive letters , when I start SQL services it starts without problems (using the new Disks).
But the issue is when I connect to SQL management studio, all databases are in suspect mode. I know there some SQL query to be run against each database , but this a production environment and I don't want to mess with it.
Is there any other way to change cluster disks of SQL cluster? or use the above method without getting into suspect mode?
Thanks, Shehatovich

Hello, Shehatovich
I you have copied the files while there were still online, that might have been the cause 'suspect' state of your databases.
I would suggest you to follow the steps:
Add the new disks to cluster, with validation in every single Cluster node (then cluster will be able to get the signature of the disks)
Stop SQL Server service.
Copy the MDF and LDF to the new disks,
use the Detach and attach Method. (http://msdn.microsoft.com/en-us/library/ms187858.aspx)
After check tha your databases are online and consistent.
Stop SQL Server service again and remove the disks
Hope it may help you...
Regards,
Edvaldo Castro
Edvaldo Castro http://edvaldocastro.com MCITP Database Administrator on SQL Server® 2008 MCITP Database Administrator on SQL Server® 2005 MCTS: SQL Server® 2008 MCTS: SQL Server® 2005 MCT: Microsoft Certified Trainer MTA: Microsoft Technology Associate
MTAC – Microsoft Technical Audience Contributor CCSQLA – Cambridge Certified SQL Associate TOEIC – Test of English for International Communication

Error Adding Node to SQL 2008 R2 Cluster

Windows Server 2008 R2 64bit. SQL 2008 R2 64bit.
The Windows Failover cluster is installed with 2 nodes. SQL Cluster was installed successfully on node 1. Ran SQL setup to add a SQL node 2. Made it to the service accounts screen. The SQL Server Agent service account name box is grayed out and nothing can
be entered. If I hit next I get the following error. I can't get past this. I looked for any cumulitive updates for R2, but there aren't any. Does anyone have a work around? If not I will have to scrap the install and go back to the non R2 version of SQL.
[Error Message]
The credentials you provided for the SQL Server Agent service are invalid. To continue, provide a valid account and password for the SQL Server Agent service.
[Details]
Microsoft.SqlServer.Configuration.Agent.InputValidationException: The credentials you provided for the SQL Server Agent service are invalid. To continue, provide a valid account and password for the SQL Server Agent service.
================================================================================

After searching around on the Net and reading a few other people with the same problem, it has to be a bug in the GUI.
Run the command line to initiate the setup and it will add the account settings automatically when you come to that page.
setup.exe /ACTION=AddNode /INSTANCENAME="<Insert Instance Name>" /SQLSVCACCOUNT="<SQL account used on other nodes>" /SQLSVCPASSWORD="<password for SQL account>" /AGTSVCACCOUNT="<SQL Server Agent account used on other nodes>"
/AGTSVCPASSWORD="<SQL Server Agent account password>"

SCCM 2012 R2 SQL Migration

Hi,
I have SCCM 2012 R2 and SQL Server 2012 SP1 Enterprise edition on the same server.
The SQL server has two instances.
1. default instance for SCCM db
2. instance named WSUS for WSUS
For licensing purpose, we want to change SQL enterprise edition to standard edition. I know that we cannot change edition without uninstalling SQL enterprise edition and installing SQL standard eition.
I want to know the steps I should follow to successfully migrate SQL to standard edition without breaking SCCM and WSUS DBs
Mashhour Faraj

For licensing purpose, we want to change SQL enterprise edition to standard edition. I know that we cannot change edition without uninstalling SQL enterprise edition and installing SQL standard eition.
I'm afraid to tell you that there is more to it than just uninstalling SQL and reinstall SQL. Because you are using enterprise edition, you might have to uninstall CM12 too and start over. This is due to SQL partitioning which CM12 will use but is not
available within SQL standard.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2012 SP1 SQL License Question!!

I have SCCM 2012 SP1 running on one server with the DB running on another server within SQL 2012 SP1. This was running grand for 5+ months green across the board.
Recently I lost SCCM access. I have discovered this is due to the trial of SQL having expired! I have performed quite a bit of research and see that SQL use is granted with the purchase of SCCM 2012 license. i.e. no SQL license is need.
My questions:
Why has my trial expired if SQL is supposedly free with SCCM 2012 license?
Do I need to upgrade to full version and use SCCM license to activate SQL?
Possible cause:
I have two instances running on my SQL server: SCCM DB and WSUS DB, is the expirey because of the WSUS DB and will I need to either remove this WSUS DB and, or, use a SQL 2012 license up?
Quick responses appreciated Thanks!
MichaelSpaulding

Hi,
There is no license key provided for SQL server with the SQL User Rights that is included in the System Center license. So you need to get the SQL server keys/media from volume licensing site. There is no relation between the WSUS DB and the fact that the
SQL trial version has expired.
If you downloaded the SQL Standard media from Volume licensing here is a guide for upgrading SQL server
http://www.mssqlgirl.com/upgrading-from-sql-server-2012-evaluation-edition.html
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

SCCM 2012 on SQL 2008 R2 cluster

Similar Messages

Maybe you are looking for