Consider you need to install a new Cumulative Update or Service Pack on your current SQL Server, but you don’t know what’s the current update level that already installed in your environment!!
In this article, we will explain
How to detect the current Cumulative Update / Service Pack that was installed on SQL Server.
Detect the Current Cumulative Update / Service Pack Installed
You can use the ServerProperty as a system defined function to return the SQL Server Instance information like the ProductLevel and ProductUpdateLevel
The ProductLevel returns the version level of the SQL Server instance as the following.
- ‘RTM‘ = Original release version
- ‘SPn‘ = Service pack version
- ‘CTPn‘, = Community Technology Preview version
select SERVERPROPERTY('ProductLevel') as 'Product Level'
Continue reading “SQL Server: How to get the current installed update level”
In this article, I will explain
- How to create LOG_BACKUP Maintenance Plan in SQL Server?
- How to restore LOG_BACKUP that have already taken via Maintenance Plan?
Keep in mind
Before you getting started, you should be aware of Continue reading “Create a LOG_BACKUP Maintenance Plan in SQL Server”
One of the annoying issues that you may experience when you work with SharePoint Databases is
The rapid growth of the SharePoint Config Database transaction log (Full).
So you should regularly maintain the SharePoint_Config Database by taking a backup of the log files frequently to avoid the below-encountered error:
The transaction log for database ‘SharePoint_Config’ is full due to ‘LOG_BACKUP’ (Microsoft SQL Server, Error : 9002)
Note: When The transaction log for database ‘SharePoint_Config’ is full due to ‘LOG_BACKUP’ error is encountered. No transaction or backup action can be performed on ‘SharePoint_Config’ database.
In this article, I’ll show How to avoid falling into this issue (SharePoint_Config Database log file is Full) by following the below steps:
- Take a Full database backup.
- Shrink the log file to reduce the physical file size (Only in exceptional circumstances).
- Create a LOG_BACKUP.
- Create a LOG_BACKUP Maintenance Plan.
As I have mentioned, if you already got this error “The transaction log for database ‘SharePoint_Config’ is full due to ‘LOG_BACKUP’” you will not be able to perform any transaction or backup action on ‘SharePoint_Config’ database.
In this case, you will not be able to take a backup, and you should start from step 2 (Shrink the log file to reduce the physical file size) then go back to get a full database backup as a prerequisite for performing LOG_BACKUP.
Continue reading “The transaction log for database ‘SharePoint_Config’ is full due to LOG_BACKUP”