Showing posts with label SQL. Show all posts
Showing posts with label SQL. Show all posts

Saturday, February 22, 2014

The collation of the site database does not match the collation of the parent site's database

I had SQL error at the Prerequisite Check page regarding the required SQL Server Collation:

"The collation of the site database does not match the collation of the parent site's database.  All sites in a hierarchy must use the same database collation.in SCCM 2012"


Configuration Manager required that you configure your SQL Server instance and Configuration Manager Site database (if already present) to use the SQL_Latin1_General_CP1_CI_AScollation,





The server collation is specified during SQL Server installation.  So this means that you need to re-install the SQL server or rebuild your database.  The server collation acts as the default collation for all system databases that are installed with the instance of SQL Server, and also any newly created user databases.
It is highly recommend to do this only on a SQL which is not in use by any other application!
Navigate to your SQL setup folder or DVD where the setup.exe is located and execute the underneath command:
Setup.exe /QUIET /ACTION=REBUILDDATABASE  /SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=BUILTIN\Administrators


Friday, January 31, 2014

Improve SCCM console performance

We can improve SCCM 2012 Console performance by using of SQL server, we will have to configure a setting known as Maximum Degree of Parallelism or MAXDOP for short. When SQL Server runs on a computer with more than one CPU, it detects the best degree of parallelism, the number of processors employed to run a single statement, for each parallel plan execution. This means that multiple queries may be executed. Setting the MAXDOP setting to the optimal setting can help improve performance by setting the limit to the number of physical processors.


We will use SQL to configure this value by using SQL Management Studio using the following steps:
1) In the object explorer, right click a server and select Properties.



 2)      Click the Advanced node.








      3) In the Max Degree of Parallelism box, select the maximum number of processors to use in parallel plan execution.
The default value of 0 uses all available processors. Set max degree of parallelism to 1 to suppress parallel plan generation. Set the value to a number greater than 1 to restrict the maximum number of processors used by a single parallel query execution. If a value greater than the number of available processors is specified, the actual number of available processors is used. If the computer has only one processor, the max degree of parallelism value is ignored.

Friday, November 8, 2013

Installation Prerequisite Check for ConfigMgr 2012

One day I was installing SCCM 2012 secondary site, I had installed SQL express on local machine because from CM12 primary site it install on C drive,
Error when doing the Prerequisite installation checks Likewise “Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup cannot continue.”
And “The logon account for the SQL Server service cannot be a local user account or LOCAL SERVICE. You must configure the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM;”
 
 
Both errors were normal but I was sure I have configured correct domain account for local service, and installation account was configured as the sysadmin server roles in SQL.
After that I did, went to services and again I have reconfigured the same domain account and did stop the service and start the service of SQL server,
And SQL Agent service was by default disabled, I made this enable and automatic.
Then again I did the Prerequisite installation checks and now this time all went pass.

PXE Issue after SCCM CB 1806 upgrade

Recently i had upgraded my SCCM environment 1806 and after upgrade suddenly all PXE servers stopped working. While initiating the PXE ...