Microsoft releases security patches on a regular basis, it is imperative for every database administrator to check the Microsoft security bulletin
Microsoft releases security patches on a regular basis, it is imperative for every database administrator to check the Microsoft security bulletin once a month and apply the security patches applicable (on a regular interval) to the product used in your landscape. This blog is about outlining the information like finding the latest applicable security patch and the way forward.
Step 1 : Check the latest available security patches
Select the product/technology and “Search Microsoft Security Bulletins” and click on “Go”
This will list down all the security patches applicable to “SQL Server 2005” Product.
Click on the latest security patch, in our case, “Vulnerability in the Microsoft XML Editor Could Allow Information Disclosure (2543893): MS11-049”
Read through the Executive Summary carefully, then scroll down to check the Affected and Non-Affected Release and locate “SQL Server”
As a next step, expand the Frequently Asked Question section to understand which pack is applicable to your release. For SQL , Microsoft releases both GDR and QFE updates offered for every version, hence it is important for you to understand which one should be applied for your release.
GDR : General Distribution – In simple terms, this pack contains only the security related bug fixes related to SQL Server 2005 product
QFE : Quick Fix Engineering –In contrast to GDR, QFE will contain security patches + functionality changes to the product.
You can check your sql release using -> SQL Studio -> New Query -> Select @@version (This will return the numbers like 9.00.5000), another method is to open explorer and locate sqlserver.exe, right click -> Properties - > Version (it will also return numbers like 9.00.5000) using which you can understand the current patch version)
Applying GDR (or) QFE depends upon your situation and requirement, applying one of them should arrest the security vulnerabilities. As an alternate, you can also apply the service pack which may contain the security patches, you can find the same under :
Before applying the patches, please read through the KB Article mentioned in each of the patches to get to know further information on the fixes.
Step 2 : Create the below script to monitor the trlog space and invoke stored procedure mentioned in step to send out the alerts
drop table msdb..TRLOGSP create table msdb..TRLOGSP ( DbName varchar(20), LogSizeMB varchar(20), LogPerc real, Status int )
insert msdb..TRLOGSP EXEC('DBCC SQLPERF (LOGSPACE)') select LogPerc from msdb..TRLOGSP where DbName='DUM' if (select LogPerc from msdb..TRLOGSP where DbName='DUM') >= 70 begin create table msdb..TRLOGRESULT ( DbName varchar(20), LogSizeMB varchar(20), LogPerc real, Status int ) insert into msdb..TRLOGRESULT(DbName, LogSizeMB, LogPerc, Status) (select DbName, LogSizeMB, LogPerc, Status from msdb..TRLOGSP where DbName='DUM') EXEC msdb..Mail_Used_TrLog_PCT_AN_Basis drop table msdb..TRLOGRESULT end else begin select * from msdb..TRLOGSP end
During SQL Server Installation, you may get an error saying “An instance with the same name is already installed on this computer. To proceed wit
During SQL Server Installation, you may get an error saying “An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.” Below suggestions may help you take necessary steps to overcome the mentioned error.
Below are the few reasons and solutions which can help you with the above mentioned error
Reason # 1: An instance is already installed
Solution : Install a Named Instance with Unique Name
Reason # 2: Previous uninstallation was not successful
Solution : Use the Windows Installer Cleanup Utility (MSICUU2.EXE) / MS KB 290301 to cleanly uninstall the SQL Server Software (then proceed with the installation)
Reason # 3 : Previous installation was successful, but the registry entries are not cleaned even after running the Cleanup Utility
Solution : regedit, HKLM -> Software -> Wow6432Node -> Microsoft -> Rename/delete Microsoft SQL Server Entries, then start with the installation.
Today I had to deal with many number of issues those occurred while performing SQL Service Pack 4 Upgrade in MSCS environment, the issues were abso
Today I had to deal with many number of issues those occurred while performing SQL Service Pack 4 Upgrade in MSCS environment, the issues were absolutely strange (at least to me), there were no structural solution given either by SAP / Microsoft, hence I had to go with my own way of identifying the root cause. I have listed down all of the issues and the possible solutions below, I am sure this will help you one or the other day when you attempt to implement SQL Service Packs in MSCS environment.
Issue # 1 : Unable to install windows installer MSP file
Solution : Stop the installation process, kill all the hotfix.exe and related processes (msiexec) those are running in both the nodes. If needed, restart both the nodes to clear the hanging installation processes.
Issue # 2 : Installation in Passive Node gets stuck and runs for a very long time, below kind of message can be seen in the log, but nothing more.
Solution : Killed msiexec process on the passive node (when the installation is running), then it will be alright (believe me, it worked very well for me)
Issue # 3 : MSP Error 29512, SQL Server Setup was unable add user to local group
Solution : Check the user which is used to run the SQL services is added to the cluster group mentioned in the error message, if not add the user to the user group related to the cluster. If that is something not doable, then change the service to run with the user that is maintained in the cluster group mentioned in the error (the same should be done using the configuration manager and not directly in the services.msc)
Issue # 4 : sqlsrvres.dll is being held in use by the following process name : resrcmon
Solution : You may ignore the error message as this is just a warning, this is really not something to be worried about, if you still think that there is a problem due to the file being blocked, then uncheck the “Run this resource in a separate resource monitor” in the cluster configuration for the services related to SQL server.