1. Skip to Menu
  2. Skip to Content
  3. Skip to Footer>

Expert Sessions!

SQL Server Installation, an instance with the same name is already installed on this computer,

Friday, 20 April 2018 01:08

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.

 

{fcomment} {flike}

Share

 

 

SQL Server Installation, an instance with the same name is already installed on this computer,

Configure Database Mail, sp_send_dbmail

Friday, 20 April 2018 01:08

 

Here are the steps to configure Database Mail in Microsoft SQL Server, please note that these steps are only valid to Microsoft SQL Server 2005.  Please refer to article http://basisondemand.com/mss/script_to_monitor_transaction_log_space_and_alert_dbcc_sqlperflogspace to understand, how this functionality can be used in a stored procedure/scripts.

 

 

Read more...

Script to monitor Transaction Log Space and Alert

Friday, 20 April 2018 01:08

 

Here is a script that can help you to monitor the used transaction log space and alert by email when it reaches the threshold value.

 

Step 1 : Create a stored procedure that will be called from Step 2 to send out the alert email

 

Read more...

Security Bulletin - MSSQL - GDR / QFE / SP

Friday, 20 April 2018 01:08

 

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.

 

 

Read more...

Never Delete files from c:\windows\installer directory

Friday, 20 April 2018 01:08

 

The reason for preserving files from installer directory is that Windows keeps all the necessary .msi/.msp files in that directory for the subsequent service pack upgrades, for example, if you install SQL 2005, windows will keep an .msi file in installer directory. Similarly when you apply service packs, windows will keep an .msp file into installer directory, if you apply 4 different service packs (SP2, SP3, SP4, SP5), then you will be able to see 4 different .msp file and one .msi (original installation) file in the installer directory. If you need to upgrade to SP6, then you will need all these .msi / .msp file in installer directory, even if you miss a single file in the whole chain, your service pack upgrade will fail for sure with the below message.

 

Read more...

MSSQL