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

Similar Messages

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

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

How to move SQL database from one location to another location i.e. from C' drive to D' drive

Hi, How to move SQL database from one location to another location i.e. from C' drive to D' drive ? please share some link.
Thanks and Regards, Rangnath Mali

Hi Rangnath,
According to your description, my understanding is that you want to move databased from C drive to D drive.
You can detach Database so that the files become independent, cut and paste the files from source to destination and attach again.
There are two similar posts for your reference:
http://mssqltalks.wordpress.com/2013/02/28/how-to-move-database-files-from-one-drive-to-another-or-from-one-location-to-another-in-sql-server/
http://stackoverflow.com/questions/6584938/move-sql-server-2008-database-files-to-a-new-folder-location
Best Regards,
Wendy
Wendy Li
TechNet Community Support

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 - 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 Moving the Database to Another Drive

Due to space constraints I need to move my SCCM 2012 R2 database to another drive on the same system(server). I will run preinst/stopsite command to stop all sccm services, but wanted to know if I could copy and move the DB and Log files to their
new drive location, instead of performing a SQL backup and restore? We are currently running SCCM 2012 R2 with SQL 2012 SP1 CU4 as our backend database.
Thanks,
-Bern

you may have already seen these posts... worth a quick look:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/3462715c-d1b7-4f1b-b5f2-1f35235e4179/move-sccm-database-to-another-drive?forum=configmgradminconsole
http://support.microsoft.com/kb/2709082
http://damatisystemcenter.com/2013/05/23/moving-sccm-2012-sp1-database-to-new-folder/

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

SCCM 2012 R2 SQL Errors

I am getting following errors in SCCM 2012 R2 console since today!!!
Any ideas:
Microsoft SQL Server reported SQL message 266, severity 16: [25000][266][Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count
= 0. : sp_addrolemember
Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information.

Parvinder,
Check the link in that thread. The resolution being the following:
'Hi guys,
I have just fixed this issue in our environment a few minutes ago. I had exactly the same issue. The problem relates
to the computer record as you described. The line:
<10-27-2009 12:20:45> ***SqlError: [42000][15410][Microsoft][ODBC SQL Server Driver][SQL Server]User or role 'DOMAIN\SERVER1$'
does not exist in this database. : sp_addrolemember
is the give away.
I went in to the SQL Management Studio, opend the SCCM database and removed the 'DOMAIN\SERVER1$' record. In my case
the problem was becasue a Branch DP server had been renamed but the DB login still hadt he old server name. Removing the OLD server login record from the databse and the main SQL security database and readding it using the NEW name resolved the problem.
When you re-add the server name make sure that you give the login the correct database rights, e.g. if it is a PXE Service
Point it will need that database right again. It is best to check the user rights for the computer and note the rights down before you remove and re-add it.
After this I re-ran the SETUP.EXe for SP2 and it went through perfectly.
Hope this helps.
Nathan
NSutton'
Cheers
Paul | sccmentor.wordpress.com

SCCM 2012 R2 Uprade - Database Concerns

I recently completed the R2 upgrade process on my production environment. Everything appeared to complete successfully. No errors, warnings, or issues aside from this RBAC mishap -
SCCM 2012 R2 Reporting error
After some further usage I'm finding some inconsistencies in my reporting data. Here's an example:
A software deployment went out last week to my users. This was a simple application upgrade, moving from 1 version to the next.
On multiple computers I can see the deployment was received and installed successfully. If I open Programs and Features I can see the software version has been updated.
From there I open the ConfigMgr console and fire up resource explorer. On multiple computers I can see a recent software scan has picked up the new software and it is reflected in resource explorer.
Now comes the DB issue - I run a manual DB query using the ADD_REMOVE_PROGRAMS table and it consistently shows me the outdated software version. This table is giving me incorrect data. Here's an example of the query I'm using:
SELECT dbo.v_R_System.Name0, dbo.v_R_System.User_Name0, dbo.v_GS_ADD_REMOVE_PROGRAMS.DisplayName0,
dbo.v_GS_ADD_REMOVE_PROGRAMS.Version0
FROM dbo.v_R_System INNER JOIN
dbo.v_GS_ADD_REMOVE_PROGRAMS ON dbo.v_R_System.ResourceID = dbo.v_GS_ADD_REMOVE_PROGRAMS.ResourceID
WHERE (dbo.v_GS_ADD_REMOVE_PROGRAMS.DisplayName0 LIKE N'%Symantec Enterprise Vault%') AND (dbo.v_R_System.Name0 LIKE N'%testcomputer')
Is there something I'm missing? Why would resource explorer have accurate data and the database be returning outdated info? Appreciate any insight. Thanks!

@Idan
Great point! I checked my last hardware inventory and it was back in December! Yikes! I pulled up my workstation policy and got hit with an ugly error as reported in
this thread. At the moment I'm rebuilding my workstation policy and will see if that resolves hardware inventory.
@ Garth
The application I'm reporting on is 32-bit. This is primarily why I didn't expand to include 64-bit programs.

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

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

How to move SQL database from one host to another ?

Hi,
We need to move the database of P1 7.0 from one host to other.Please advice if there are any documents I can refer for this operation.
I believe if we maintain the same host name for the new system it is just database movement and PI should not even be aware of this operation!!
Thanks & Regards
Mrutyunjay

Hi,
      We have a system R / 3 Enterprise Edition 47x200 running with Microsoft SQL Server 2005.
     Copy the BD in another machine (server), then applied script note 551915 (user_restore.sql) and finally proceeded to install the central instance of SAP (sapinst) with existing database option, but it does not appear that the error attached:
Errors during EMP database check on produccion4; reported errors:
Error by Compatibility level check: Database EMP has wrong compatibility level
Error by Dbo objects check: Database EMP contains user objects belonging to system user dbo
; correct reported errors before continuing with the installation
     hope someone can give us some help on diagnosing the issues, thaks.
Best regards,
Christian Astete.

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 : Move SQL Database

Similar Messages

Maybe you are looking for