Product: Microsoft SQL Server Browser – Update Service Pack 1 for Microsoft SQL Server Browser (KB-NUMBER)’ could not be installed. Error code 1639.

Root Cause

I was not able to find any reason behind this error because I had followed all prerequisites before starting this installation. I went to some forums to get a root cause of this error 1639 or solution to fix it and what i found is described in this article.

This issue (Error 1639) comes when there is a blank space between your SQL Server setup folder directories. As I found my setup files were placed under a directory named “SQL Server 2012”. You can see there are two blank space between this directory name. This was the main reason or cause behind getting this SQL Server installation error. Read next section to fix this issue and install SQL Server successfully on your database server.

Resolution

To fix this issue, we have decided to first uninstall SQL Server instance that was failed to install. I have uninstalled it from “Add and Remove Programs” and deleted all SQL Server folders that was created during the installation. Once failed installation of SQL Server was uninstalled from database server, we have rebooted the machine to proceed with fresh installation.

As I mentioned above, issue was due to blank space between the parent directory of SQL Server setup files. You can see the name of directory in below screenshot.

Now I have removed the blank space between the words of this folder name and changed it to “SQLServer2012”. You can see the below screenshot of this change.

That’s all to fix this issue. Now go ahead and start the installation again for your work.

Once this directory was renamed, I have started the SQL Server installation process. I had launched setup file and proceed for installation. You can also right click on setup file and choose “Run as Administrator” to start the installation. Follow all windows and processes of installation process as you did last time to install it. This time your SQL Server instance will be installed without any issue.

The key takeaway from this issue is to never keep any bank space between files or folders otherwise you will be end up with similar issues.

I hope you like this article. Please Like, Share, Comment & Subscribe to this website to get all new articles directly to your index. You can also follow our Facebook page and Twitter handle to get latest updates.

Read More:

• SQL Server Interview Questions & Answers on Architecture
• SQL Server Interview Questions & Answers on Indexes
• Microsoft SQL Server DBA Interview Questions & Answers
• SQL Server Interview Questions & Answers on Backup & Recovery

The post How to Fix SQL Server Installation Error 1639? appeared first on Techyaz.com.

Related Articles:

• Read UNION vs UNION ALL
• Logon Trigger to Restrict sysadmin logins
• Why rou count showing incorrect value in sys.partitions?

Types of Joins

 There are four types of Joins and each type is having separate ways to retrieve data.

• Inner Join
• Right Join
• Left Join
• Full Join

We will use two tables Employees and Leavesdetails to explain you each type of Joins with example. The details of both tables are given below.

Table Employees:

Table LeavesDetails:

 We will apply all types of Joins between these two tables to show you how they work. Let’s start with Inner Join. 

Inner Join 

Inner join will show data that is matched between both joined tables. This is default join where result is based upon where clause and matched value from all rows fetch data. The visual representation of inner join will look like below image. You can see the coloured area that is common between both tables and that will be output of INNER JOIN.

As per above image, both tables Employees and Leavesdetails have been joined together to get output details for rows that are matched to each other.

SELECT *
FROM EMPLOYEES
INNER JOIN [dbo].[LeavesDetails]
ON [LeaveDetails].[Employeeid]=[Employees].[Employeeid]

Right Join

When we use Right Join keyword, it will return all rows from table 2 that is placed right side of RIGHT JOIN keyword and matched rows from table 1 that is mentioned just left to the RIGHT JOIN keyword in SQL statement. In right join, if rows do not match with table 1 it will return null value. Sometimes, we call it as Right Outer Join as well. The visual diagram of Right Join is given below.

Example

We can see Employees table is mentioned as table 2 and placed just right after keyword RIGHT JOIN and Leavesdetails table has been mentioned as table 1 that is just left to the keyword RIGHT JOIN.

SELECT * FROM Leavesdetails
RIGHT JOIN Employees
ON [Employees].[Employeeid]=[Leavesdetails].[Employeeid]

You can see all values have been displayed from table Employees  along with corresponding details from table 2 Leavesdetails whereas there is one null value row from table Leavesdetails because there is no matched entry for this row from Employees table.

Left Join

When we use LEFT JOIN keyword, it will return all rows from table 1 that is placed just before or left side to the LEFT JOIN keyword and matched rows from table 2 that is mentioned just right side to the LEFT JOIN keyword in SQL statement. In left join, if rows do not match with table 2 it will return null value. Left Join is also known as left outer join. You can see the visual representation of Left Join in below image.

Example

you can see, now Employee table is mentioned left side of LEFT JOIN keyword and Leavesdetails table is mentioned in right side of this keyword so Employee table will work as table 1 and Leavesdetails will work as table 2.

SELECT *
FROM Employees
LEFT JOIN Leavesdetails
ON [Leavesdetails].[Employeeid]=[Employees].[Employeeid]

We can see all records from Employees table along with its corresponding details from table 2 Leavesdetails whereas one null values from table2 that is Leavesdetails because it’s matching with the data presented in table 1 Employees table. As highlighted record does not exist in table 2 it is showing null value.

Full Join

When we use FULL JOIN, it fetches results from both tables when there is a match in either in left or right table. We can also say it is kind of combination of left and right join.

Example

As visual representation shows, it will show all records from Employees table and Leavesdetails table. You can see in below result set Employee Manvendra has not any leaves detail and same way Employee ID 108 has not any record in Employees table but both rows are showing their values.

SELECT *
FROM EMPLOYEES
FULL JOIN [dbo].[Leavesdetails] on [Leavesdetails].[Employeeid]=[Employees].[Employeeid]

I hope you like this article. Please follow our Facebook page and Twitter handle to get latest updates.

The post Understanding Different Types of SQL JOINs with Examples appeared first on Techyaz.com.

Read attached article if you want to upgrade your SQL Server Evaluation Edition to Standard, Enterprise or Developer Edition. You can also activate your SQL Server Instance if its evaluation period has been expired using same article.

Note: – Take proper Full backup of your all databases before starting this activity. Make sure to create script of all Logins and SQL Server Agent Jobs etc. You can also Rename your Data folder where you have placed your database files to secure the databases during this process post stopping SQL Server services .

Read More:

• SQL Server Architecture Interview Questions & Answers
• What should be best value for fill factor in SQL Server?
• Why Should You Always Turn Off Database Auto Shrink Property?
• How to Improve Bulk Data Load Performance?

Change SQL Server License key

Step 1- First step is to stop all SQL Server services. Launch SQL Server Configuration Manager and shutdown all services.

Step 2-  Copy SQL Server Enterprise/Standard edition setup to your server where you want to change the SQL Server product key. Run Setup.Exe with an Administrator account. SQL Server Installation Center will appear on your screen to proceed. Click on Maintenance tab from left side pane. You can see multiple options in right side pane. Select first option Edition Upgrade as shown in below image and click Next.

Step3- SQL Server will check all required rules, once all rules will be passed next button will enable to proceed. Click on Next button here.

Step 4- Once you click on Next button of above screen, next window will come to enter the License Key or product Key of SQL Server Instance. Enter your Product Key or if EXE has a valid license key to cross verify then proceed for Next button with the same License key. Make sure that License key is not for MSDN or from any invalid source.

Step 5- Accept License Term and Condition and Click on Next button to proceed.

Step 6- Select MS SQL Server Instance for which you are going to change license key if you have multiple instances.

Step 7- Click on Next button of above screen, it will check all rules for edition upgrade. If all rules shows as Passed you are good to go ahead. If your are getting any warning or error verify and try to fix it before going with the next step.

Step 8- Below will be the final window that prompt for Ready to upgrade the edition. Click on Upgrade button if all looks ok.

Step 9- Once License will be updated below window will prompt with succeeded status.

Now you MSDN license has been changed to valid SQL Server Enterprise License. License will change based on the SQL Server setup you used for edition upgrade.

You might face Access Denied error during this edition upgrade, here is the solution to fix this error. You may get access denied error on SQL Server License.rtf file for that you need to uncheck read only attribute from file name.

If you have renamed your Data folder before starting this process as suggested in Note section, you can rename back it to Data folder again and then start the SQL Server services. Now, start MS SQL services which you have stopped initially before starting upgrade activity and check SQL Server Instance version and license type . You can see our output looks like below details.

Microsoft SQL Server 2012 (SP3) (KB#######) - 11.0.6020.0 (X64)
Date and time
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 <X64>
(Build 9600: ) (Hypervisor)

I hope you like this article. Please follow us on our facebook page and on Twitter handle to get latest updates.

The post How to update License Key or Product Key of SQL Server Instance appeared first on Techyaz.com.

Logon trigger Overview

Logon Triggers fire in response to a LOGON event. It fires after the authentication phase of logging in finishes, but before the user session is actually established. Logon Triggers are very useful in tracking and restricting login events.

Sometimes few applications require sysadmin privilege to run and if you downgrade this access, application stops working. So, we cannot restrict sysadmin logins of such applications. There is always a scope of security breach if another login has sysadmin access except DBAs on SQL Server Instance.

To fix this issue, I have created a logon trigger that will restrict access of such application logins who are sysadmin on your SQL Server Instance.  We can restrict them to access SQL Server directly through SSMS or any other medium. You need to pass that medium into code just like I have passed Management studio.

Logon Trigger T-SQL Code

Below is the Logon Trigger T-SQL code which will be used to restrict any login for given time frame.

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO

CREATE trigger [logon_rest]
on all server for logon
as begin
declare @Program varchar(128)
declare @systemname varchar(128)
select @Program =PROGRAM_NAME,@systemname=HOST_NAME from sys.dm_exec_sessions as A
where a.session_id=@@SPID
if ORIGINAL_LOGIN() in('sa') /**Login For Which Access Need to restricted **/
and @Program like'%Management%studio' /** Program via access restricted **/
and
(GETDATE()>(dateadd(day, datediff(day, 0, getdate()), 0) + '18:00') /**Last time till access allowed **/
or
GETDATE()<(dateadd(day, datediff(day, 0, getdate()), 0) + '09:00')) /**Start time from access allowed **/
begin
Raiserror ('This is out of office hour',1,1)
rollback;
end
end;
GO
SET ANSI_NULLS OFF
GO
SET QUOTED_IDENTIFIER OFF
GO
ENABLE TRIGGER [logon_rest] ON ALL SERVER
GO

Testing

For the testing purpose, I have taken sa account as a potential application login. You can use your identified login which are running with sysadmin rights. Even we can restrict such logins to connect to SQL Server during given time frame.

Here we have disabled sa server level login to connect through SSMS Before 9:00 AM and Post 6:00 PM. That means server login sa cannot connect to SQL Server Instance between given time slot. You can alter the time slot as per your convenience.

Just for example we have tried to login on SQL server through SSMS between given time frame and here you can see the output. I am not able to connect to SQL Server anymore. You can see this in below screenshot. But at the same time you can login to the same SQL Server Instance using other sysadmin or normal login accounts which is available in sys.syslogins.

Even we can track the failed login attempt made on this SQL Server Instance once you can make a database connection using another login. You can check the SQL Server error logs or you can just run sp_readerrorlog stored procedure to display errors. You can see our test login attempt is showing in below screenshot on the server.

Read more about SQL Server Login Issue related Articles:

• How to fix Error 15173: Revoke the permissions before dropping the login.
• Fix error 15138 & Error 3729: DROP login failed
• How to fix error 15434: Could not drop login as the user is currently logged in
• Fixing error 15170: Login owns one or more SQL Agent Jobs

I hope you like this article. Please follow us on our facebook page and on Twitter handle to get latest updates.

The post Create a Logon Trigger to Restrict sysadmin logins to connect to SQL Server for given Time Interval appeared first on Techyaz.com.