SQL Server Native Client Error 50000

Before explaining about SQL native client error 50000, i would like to describe about what is SQL Server native client. As per MSDN “SQL Server Native Client, is a term that has been used interchangeably to refer to ODBC and OLE DB drivers for SQL Server.” 

SQL Server Native Client is a technology that we can use to access data in a SQL Server database. There are several factors you should consider while deciding whether to use SQL Server Native client or some other data access technology. You can read attached article about when to use SQL Server Native Client.

Generally, we get SQL Server native client error 50000 while installing or updating native client software or a software component that uses SQL Server Native Client and your target machine already have this installed previously using some msi file.

You can also get this issue if SQL Server native client file sqlncli.msi has been renamed after its installation and later today when you are trying to update it, you will end up with this SQL error 50000 . If somehow native client installation file has been renamed on your machine, setup will not find its file to update SQL Server native client and through below error.

A network error occurred while attempting to read from the file <Filename>.”

Solution

To fix this error, you should uninstall installed version of SQL Server native client from add/remove program and then you can try to install SQL Server or its component again. This time you will not get any error and your software or native client will be installed. To avoid further issue, you can reboot the machine post uninstalling the native client tool.

If you are installing only SQL Server native client and not SQL Server then you can download it from Microsoft website and then reinstall it again.

You can also prevent this error to not generate in future by not installing it using its msi file sqlncli.msi. If you had installed it using this file, make sure to never rename it as well.

Here, I have shown you how to fix SQL Server Native Client Error 50000, “A network error occurred while attempting to read from the file <Filename>.”  I hope you like this article. Please follow our Facebook page and Twitter handle to get latest updates.

Read More:

• Fix SQL Server Error 5009: One or more files listed in the statement could not be found or could not be initialized
• Fix SQL Server Installation Error: Attributes do not match
• How to Fix SQL Server Installation Error 1639?
• SQL Server DBA Interview Questions & Answers

The post SQL Server Native Client Error 50000: A network error occurred while attempting to read from the file appeared first on Techyaz.com.

There are many ways to check SQL Server installation date on your machine. Here i am going to discuss two popular methods that we can use easily to get install date of SQL Server. Let’s go one by one in step by step process.

Method 1

As we know whenever we install SQL Server, a SQL Server Agent job named “syspolicy_purge_history” got created. The install date of SQL Server instance will be same as the create date of this job because this job was created during SQL Server installation. So, if you need to find when SQL Server was installed on your database server then you can get it by create date info of above job. Follow below steps to get the details.

You can expand SQL Server Agent folder in SSMS and then Jobs folder. Here you can see this job. We can launch Properties window of job “syspolicy_purge_history” or you can query msdb database to get the details of this job. Here, I have launched Properties windows of this job and we can see the create date of this job is below screenshot. It means this SQL Server Instance was installed on 27^th July 2017 as showing as create date of below job.

Method 2

Another method to get SQL Server install date on your database server is by using SQL Server system logins. These system logins get created when we install SQL Server. Some of the system logins are NT SERVICE\SQLWriter, NT Service\MSSQLSERVER, NT AUTHORITY\SYSTEM and NT AUTHORITY\NETWORK SERVICE. You can also see some of the system logins that starts with hash # like ##MS_Policy***** etc. As I said these logins get created during SQL Server installation so to get SQL Server installation date we can check the create date of any such logins.

You can run below commands to check the create date of any of system logins. I have executed below commands to check create date of three system logins.

SELECT name, create_date
FROM sys.server_principals
WHERE name='NT SERVICE\SQLWriter'
GO

SELECT name, create_date
FROM sys.server_principals
WHERE name='NT Service\MSSQLSERVER'
GO

SELECT name, create_date
FROM sys.server_principals
WHERE name='NT AUTHORITY\SYSTEM'
GO

We can see create date of all above SQL Server system logins are same as the create date of system job “syspolicy_purge_history” that is described in method 1. So, SQL Server install date on this database server was 27^th July 2017 as shown in below image.

You can also get SQL Server install date by getting update date of system account sa. As we have disabled sa account as part of SQL Server hardening so last update was captured when we disabled this account. But this does not show correct info always because if anybody has enabled this account and again disabled it then this will give you inaccurate information but you can use this information to compare the update date information with the create date of other logins and jobs. This will help you in identifying the install date of SQL Server in more accurate manner.

SELECT *
FROM syslogins
WHERE name='sa'
GO

SELECT *
FROM sys.server_principals
WHERE name='NT AUTHORITY\SYSTEM'
GO

You can see the update date of sa account and create date of the another system login shows same date that is also the SQL Server Installation date.

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

Read More:

• SQL Server Evaluation Period has Expired and How to Upgrade it?
• Create a Logon Trigger to Restrict sysadmin logins to Connect to SQL Server during a given time Interval
• SQL Server Interview Questions & Answers

The post How to Find When SQL Server was Installed? appeared first on Techyaz.com.

Recently, one of the SQL Server Instance suddenly stopped working and shutdown automatically. We failed to bring its services online. Even we were not able to launch SQL Server Management studio. When we checked windows event viewer, we had seen multiple event ids for SQL Server like Event ID 7024, Event ID 17051 etc. We got this error because SQL Server evaluation period has expired for this instance.

As I said, SQL Server was down and I tried starting it from SQL Server Configuration Manager. It never come online so I decided to check Windows event viewer. I saw event id 7024 that says something wrong with application SQL Server. You can see the screenshot of event id 7024.

We can see error 17051 is captured for SQL Server in above screenshot. When I scrolled next error details I saw below details with event id 17051 that says “SQL Server evaluation period has expired”. When you look into SQL Server error log, you will get below details.

Error: 17051, Severity: 16, State: 1.
SQL Server evaluation period has expired.

Then I decided to check the installed version of SQL Server that clearly says that we had installed SQL Server Evaluation version on this database server. You can get it by launching property window of SQL Server service in SQL Server Configuration Manager. You can see this in below screenshot.

Now we had to upgrade SQL Server evaluation edition to bring it online and make it work as it was working before. To start this, we need SQL Server setup files to perform this upgrade. Follow below steps to activate your expired SQL Server evaluation version to either standard, enterprise or developer edition.

Upgrade SQL Server Evaluation Edition to Enterprise Edition

First decide on which edition you want to upgrade your expired SQL Server evaluation edition instance. Copy identified edition of SQL Server setup files to the target or impacted SQL Server machine. Now we will launch SQL Server Installation Center to run this upgrade. Make sure to run this whole process using sysadmin account.

Double click on Setup.exe file to start the upgrade. You will get SQL Server Installation Center once you run setup.exe file of SQL Server setup. Click at “Maintenance” tab from left side pane as shown in below image and then click on “Edition Upgrade” option from right side pane.

Once you click at Edition upgrade, below image will come to proceed. This screen will come to enter the product key of SQL Server. Verify the correct product key and click on next button to proceed.

Once you click at next button you will get below pop up “Evaluation period has expired”. Click on Ok button to proceed.

Next screen will come to accept the License Terms. Click at Next button after selecting “I accept license terms” checkbox option.

Here, you will get installed components of SQL Server. Verify the SQL Server instance and click on next button to proceed. You can see edition is showing as Evaluation in below screenshot.

Once you will click at Next button, rules will be checked by the setup and you can see the progress bar in below image.

Now it’s time for final window of this upgrade process where you need to recheck and verify the details and if everything looks good then click at “Upgrade” button to start the upgrade process.

Setup will process and end up with new upgraded edition. You have been activated SQL Server to run it on your server and it has been upgraded to your identified edition of SQL Server i.e Enterprise edition.

You can check the upgraded edition by launching property window of SQL Server service in SQL Server Configuration window. We can see now edition is showing as Enterprise Edition. Here, we have upgraded SQL Server evaluation version to Enterprise edition of SQL Server 2014.

Now you can go ahead and launch SQL Server Management Studio and establish database connection to check and verify all details to make sure everything is ok on your database server.
I hope you like this article. Please follow our Facebook page and Twitter handle to get latest updates.

Read More:

• How to update License Key or Product Key of SQL Server?
• Fix SQL Server Installation Error 1639
• SQL Server Interview Questions & Answers

The post SQL Server Evaluation Period has Expired and How to Upgrade it? appeared first on Techyaz.com.

PostgreSQL is for many the best in its area, and it is not the aim of this article to defend or support that theory, what we can say with all certainty is that it is one of the most robust and secure database handlers that exist. As if this were not enough, it has one of the most popular and complete graphical tools to manage it, such as pgAdmin.

As the project website says: “pgAdmin is the most popular and feature rich Open Source administration and development platform for PostgreSQL, the most advanced Open Source database in the world.” And of course we can install it in our preferred GNU/LINUX distribution. In this case we are going to install it in our Debian 9 Stretch a large GNU/LINUX distribution widely used in the server and database area.

Install pgAdmin 4 on Debian 9 Stretch

Note: In this tutorial it is assumed that you have postgreSQL installed, otherwise, we must install it. You can find the way of doing it in below link.

• How to Install PostgreSQL 10.1 on Debian 9 Stretch

Let’s get started. The first thing we have to do is add the postgreSQL apt repository. If you have installed postgreSQL with the tutorial we have attached above, you can skip these steps. Otherwise we must add it.

First we logged in as root user. Write su in your terminal screen along with its password and press enter to connect.

#Connect using root user
su

Now, use below command to create the pgdp.list file in the /etc/apt/source.list.d/ path.

nano /etc/apt/source.list.d/pgdg.list

Here, we will add the next line of code to the terminal screen that will come after executing above command.

deb http://apt.postgresql.org/pub/repos/apt/ stretch-pgdg main

Press ctrl + x to exit and select yes to save the changes.

Now import the repository signing key by running below commands on your terminal screen.

#Import the repository signing key
wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | apt-key add -

And to refresh the repository cache, just run the following command.

#Refresh the repository.
apt update

You can see all packages have been updated in above screenshot. Now we are ready to start installing pgAdmin 4.

Installing Dependencies and Creating the Virtual Environment

We must install the necessary dependencies to handle the package. They are basically Python dependencies that needs to be resolved before installing pgadmin package. Execute below command in your terminal before going to install pgadmin.

#Install Python dependency.
apt install virtualenv python-pip libpq-dev python-dev

Type Y and press enter to install this dependency. The next step will be to create the virtual environment. In this case we will create it on /home/Your_user/. Run below commands to get this done.

#Go to your directory.
cd /home/your_user/

#Create Virtual Environment.
virtualenv pgadmin4

This creates a folder called “pgadmin4“. We must enter it to get in to this folder.

cd pgadmin4

The next step will be to “activate” the virtual environment by running below statement.

#Activate virtual environment.
source bin/activate

Downloading and Installing pgAdmin

Now, we will install pgadmin on this machine. We can download latest version pgAdmin4-2.1 from this link. For this tutorial we will use the python package that is showing in below screenshot.

And finally we will proceed to install pgadmin using pip command as given below.

#Replace <path-where-file-is-located> with your patch followed by file name.
pip install <path-where-file-is-located>

We will be running below command in our case.

#Run below command to install pgadmin.
pip install /home/angelo/Descargas/pgadmin4-2.1-py2.py3-none-any.whl

With this pgAdmin is already installed but we are not finished yet. You need to create a local configuration and run it. Run below command to do this.

#Go to pgadmin4 folder
cd lib/python2.7/site-packages/pgadmin4

#Create config file
touch config_local.py

The “touch” command creates an empty file from the linux terminal, if the file exists it will change the date and time of the modification. In that file we can place the settings we want, if the file is left empty it will take the global settings of python.

We can now execute below command to create the credentials. Once you run below command, it will ask you to enter your email address and password. Those credentials will be the ones we use to access the application from the browser.

python lib/python2.7/site-packages/pgadmin4/pgAdmin4.pyc

Now we have created the credentials as well in above screenshot. At the end, we will be told that we must log in with our favorite browser to 127.0.0.1:5050 to log in and enter the main page of pgAdmin.

Let’s go to our browser and type 127.0.0.1:5050

We put our email address and the password we have previously entered. We can also select the language. Once we will be logged in using given credentials, we can see the main pgAdmin panel that is also showing in below screenshot.

We can test the application by adding a server. In this case it will be a local server. We must click on the “Add new Server” link given in between Quick Link section. We will get below screen to enter details about the server that we want to add.

The name we want to give to the connection is placed in the window. I called it “local.” We’ll leave the rest the same, if we want to.

In the connection tab, we will enter the connection parameters Host name, port, database, username, and password to add the server. You can see this in beow screenshot.

And with this we already have an added server and we can start working with postgreSQL. You can see the server is added in left side pane of pgAdmin panel. You can expand the plus sign to see the details like databases etc.

Conclusion

We have installed pgadmin 4 in debian 9 stretch to manage PostgreSQL databases. Data management is vital to system administration and specialized programs are required to keep data secure and properly structured. Complementing PostgreSQL we have pgAdmin that helps us, with a friendly graphical interface, to manage our databases, to make sentences and to monitor the service.

Installing both is one of the best ways to have and view databases in a way that is appropriate for our applications.

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

The post How to Install PgAdmin 4 in Debian 9 Stretch? appeared first on Techyaz.com.

Installing PostgreSQL in Debian GNU/LINUX is not a major problem, as it is available in the main repositories, but the version that comes with it is not the last one and does not allow us to have the latest updates and security patches that are necessary to ensure data protection.

Read below article if you want to install PostgreSQL administration and development tool pgAdmin on your Debian 9 stretch server.

• How to Install PgAdmin 4 on Debian 9 Stretch

New Features in PostgreSQL 10

PostgreSQL improves with each version, the changes are multiple both in administration and security level. Some important new features of PostgreSQL 10.1 are:

• Improved authentication process. Thanks to the new authentication system SCRAM-SHA-256.
• Many bug fixes for logical replication. Users can now fine-tune replicated data to multiple database clusters and will have the ability to perform zero-time activity updates to larger future versions of PostgreSQL.
• Declaratory partitioning of tables. This means that users no longer need to create triggers for routing data; it’s all handled by the system.
• Improved parallel query execution.
• Fix memory leak over the lifespan of a query when evaluating a set-returning function from the target list in a SELECT.

As has been said, there are many changes at the application level and you can consult them all here.

Install PostgreSQL 10.1 on Debian

Let’s get to work  to install PostgreSQL. We will start with Adding PostgreSQL Apt Repository.

The first thing we must do is to create a new file called pgdg.list in the following path: /etc/apt/sources. list.d/. To do this, we must be logged in as superuser. Run below command to connect using superuser.

--Connect using superuser
su

As you can see in the image, we must enter the password for root access. Then we invoke the nano editor and create the file in question.

nano /etc/apt/sources.list.d/pgdg.list

We further add the below line of code:

deb http://apt.postgresql.org/pub/repos/apt/stretch-pgdg main

Press Ctrl + x to save the changes. We say yes and with this we already have the repository added to our software sources.

The next step is import the repository signing key. After updating the package lists, doing this makes our package manager recognize the repository as a reliable one. Execute below commands in your terminal window to import the repository signing key.

--import the repository signing key
wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | apt-key add -

And to refresh the repository cache, just use the following command

--Update Package Lists
apt-get update 

We are now proceeding to install the latest version PostgreSQL 10.1 in our Debian 9 Stretch.  Write in Terminal:

--Install PostgreSQL Latest Version.
apt install postgresql-10

Above command will download and install the latest version of PostgreSQL on this Debian machine. Type Y and press enter to proceed with the installation. After downloading and installing the packages, we must initialize the postgreSQL service because if it is not running, it is not possible to access or connect with it. We can do it with the following command.

--Start PostgreSQL service.
systemctl start postgresql

We verify that we can make connection with PostgreSQL:

--Connect to PostgreSQL and Verify Installed PostgreSQL version.
su postgres -c psql postgres

And that’s it. That’s all.!!!!!!!!! We already have installed the latest version of this powerful database manager.

Now we can start working, for example, we can show the existing databases in a clean installation of PostgreSQL.

Conclusion

Debian is a large Linux distribution and is among the most popular in the world of system administrators. Known for its high stability and flexibility, but in its main repositories it has older versions of software and in many cases this is often a big problem. However, there are external repositories that facilitate the distribution of the latest versions of these programs.

PostgreSQL in the world of database has a very high reputation that makes it compete for the throne with other free alternatives such as Mysql or SQLite. Upgrading to the latest stable version guarantees us security patches and new features focused on speed, performance is very useful if we have a large database.

I hope you have learnt how to install PostgreSQL on Debian. Please follow our Facebook page and Twitter handle to get latest updates.

Read More:

• How to Install SQL Server 2017 on Ubuntu 16.04?
• Installing SQL Server 2017 on Red Hat Linux Server
• Installing SQL Server on Ubuntu in Offline Mode

The post How to Install PostgreSQL 10.1 in Debian 9 Stretch appeared first on Techyaz.com.

Microsoft.SqlServer.Configuration.Sco.DirectoryAttributesMissmatch: Attributes do not match. Present attributes (Directory, Compressed, NotContentIndexed) , included attributes (0), excluded attributes (Compressed, Encrypted). 

You can get this issue during SQL Server installation or during SQL Server patching activity. Read this article to fix this issue.

Related Articles

• Install SQL Server on Ubuntu running without Internet
• SQL Server Architecture Interview Questions & Answers
• Fix Error 40: A Network-Related or Instance-Specific Error Occurred

Root Cause 

We get this error “Attributes do not match” because one of the drive that we are using to install SQL Server is compressed. As we know, Microsoft does not support compressed drives for SQL Server installation so we’ll search for compressed drives on the database server. Best way to avoid this issue is to make a best practice to check whether any of the drives are compressed or not before starting SQL Server installation. You can also add this as a prerequisite or pre-step for SQL Server installation. 

Solution

Once you get this issue, you can check all drives available on your database server whether they are compressed or not. If any drive is compressed and SQL Server is using that drive during installation then that might be the reason for getting issue Attributes do not match. You need to uncompress all such drives and then start the installation.

In order to uncompress the drive we need to launch property window of that drive. We just need to right click on the identified drive and choose Properties to see the status of compression. I checked the same and found one of our drive was compressed. Please have a look at below screenshot. You can see compress this drive to save disk space option is ticked. Uncheck this option and click on Ok button to apply the change.

Once you validated all drives that none of the drives are compressed then you can start SQL Server installation and this time SQL Server installation will be successful.

You might get this error during SQL Server patching as well if any of the SQL Server folders will be compressed. Remember to make a practice to not compress any SQL Server file or folder. If you get this error during applying SQL Server patches, you need to find the compressed folder and then perform same activity (uncompress the identified folder) for that folder which we performed for drive compression in above screenshot. This way you can fix SQL Server installation issue “Attributes do not match”.

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

The post Fix SQL Server Installation Error: Attributes do not match appeared first on Techyaz.com.

Install SQL Server Agent on Ubuntu Linux

Let’s first check whether SQL Server Agent is installed or not on your existing server.  Before installing SQL Server Agent, you must install SQL Server 2017  on your ubuntu server. If you have already installed SQL Server 2017 then you can connect to SQL Server that you have installed on Ubuntu server in SSMS.

Related Articles:

• Install SQL Server 2017 on Ubuntu Server that is not connected to Internet
• SQL Server Agent Installation on Ubuntu Server that has no internet connection
• Install SQL Tools on Ubuntu Server that does not have internet access.
• Install SQL Server on Red Hat Linux Server

As we can see, SQL Server Agent or SQL Agent is disabled and none of its options are showing as enabled in below image. This is because SQL Server Agent package is not installed on that Ubuntu server.

SQL Agent Package comes with SQL Server 2017 package repository so if you have downloaded SQL Server 2017 repository, you can just run installation command to install SQL Server Agent. You can have a look at my last article where I have installed SQL Server 2017 to understand how to download Microsoft Ubuntu repositories. As we have already installed SQL Server 2017 by downloading its repositories so we can directly install SQL Server Agent here. Run below command to install SQL Server Agent package.

#Install SQL Server Agent
sudo apt-get install mssql-server-agent

You can see SQL Server Agent is installed on this machine in above screenshot and also this installation is suggesting us to restart the SQL Server service to enable SQL Server Agent. Now run below command to restart SQL Server service on this machine. You can see we have restarted SQL Server service in below image.

#Restart SQL Server Service
systemctl restart mssql-server

#Check SQL Server Service Status
systemctl status mssql-server

Now connect to SQL Server Instance in SSMS client. You can also connect to SQL Server using sqlcmd utility but we need to separately install this utility to make database connection that we will do in another article. If you are already connected to SQL Server instance in SSMS then just right click on Agent folder and click on refresh button.

You can see SQL Server Agent folder is enabled and all options are showing now in below image. Even now we can create any agent job to schedule any database tasks now.

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

The post Install SQL Server Agent on Ubuntu Server appeared first on Techyaz.com.

Before going ahead, we need Ubuntu Linux 16.04 server. If you don’t have Ubuntu server then you can create a virtual machine and install Ubuntu 16.04 Server with the help of attached articles in the link.

Install SQL Server on Ubuntu Server

Below are the steps you should follow to install SQL Server 2017 on your Ubuntu 16.04 machine that are connected to internet.

1- First step is to connect to Ubuntu Server locally or using PuTTY.

2- Once you are connected to Ubuntu server, run below command to download the public repository GPG keys:

#Download GPG Keys
curl https://packages.microsoft.com/keys/microsoft.asc | sudo apt-key add –

3- We can see curl package is not installed on this machine so first we should install curl here. Run below command to install CURL package.

#Install CURL Package.
Sudo apt install curl

Once curl will be installed, run curl command that are given in step 2 again to download the GPG keys.

4- Register the Microsoft Ubuntu Repository by running any of the below commands. First command is older one and for RC (Release Candidate) version. If you want to install SQL Server 2017 general availability version then run second command.

#Register Microsoft Ubuntu Repository for RC version
sudo add-apt-repository "$(curl https://packages.microsoft.com/config/ubuntu/16.04/mssql-server-2017.list)"

#Run this command if you are downloading GA (General Availability) Repository.
sudo curl https://packages.microsoft.com/keys/microsoft.asc \| sudo apt-key add - && sudo add-apt-repository "$(curl https://packages.microsoft.com/config/ubuntu/16.04/mssql-server-2017.list)"

We can see add-apt-repository command is not found so we will first install the required package for this command on this server.

#Install add-apt-repository package
Sudo apt-get install software-properties-common

Type y to proceed in above image. Once installed, again run command given in this step initially. Run the one given for general availability.

5- Update the repository by running below command. A series of executions will start during update process.

#Update All Packages
Sudo apt-get update

6- Install SQL Server by running below command.

#Install SQL Server 2017
Sudo apt-get install -y mssql-server

7- Install above suggested package mssql-conf to configure SQL Server 2017. This package will ask you to accept license terms and choose SQL Server edition as shown in below image.

 #Run below utility to configure SQL Server 
sudo /opt/mssql/bin/mssql-conf setup 

8- Now check the SQL Server service by running below command. We can see service is running now.

#Check SQL Server service
systemctl status mssql-server

9- Now, you can connect to this instance using SSMS client from your local host or from the server where you have installed SSMS. Make sure that there should be connectivity between both servers. SQL Agent is disabled because it is not installed yet.  Read this article to install SQL Server Agent on Ubuntu Server to get it enabled for Agent jobs and other agent related features.

10- If you face any issue during connectivity, you can check SQL Server port no 1433. If it is not open, run below command to enable port no 1433 and then establish the connection.

#Open port 1433
sudo ufw allow 1433

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

The post Install SQL Server 2017 on Ubuntu with Internet Access 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.

Before going ahead, we need to have a RedHat Linux server. If you have no idea about installing Linux server or creating a virtual machine where you can install Linux and SQL Server then i would recommend you to read below articles first.

• How to Create a Virtual Machine.
• Install RedHat Linux 7.3 on a virtual machine.
• How to Install SQL Server on RedHat Linux 7.3

If you have installed SQL Server on Red Hat Linux server, your next step should be to install SQL Server Agent on that server. Make sure you have internet access on the Linux server where we are going to install SQL Server Agent. If your server does not have internet connection then you should read attached article about installing SQL Server Agent on RedHat Linux that are running without Internet.

Install SQL Server Agent on RHEL

As this Linux machine has internet connection so let’s go ahead with Installation on Red Hat Linux server. Installation process is quite similar to the installation of SQL Server on Redhat Linux.

You don’t need to download SQL Server Agent package separately the way we did for SQL Server and SQL Tools installations.The package required to install SQL Server Agent included into SQL Server package repository configuration file.

If you have already downloaded SQL Server package repository configuration file to install SQL Server, you can skip this step and go ahead to install Agent on your server. If you don’t have SQL Server package repository configuration file or you have deleted it then you can run below command to download the package repository configuration file.

#Download Microsoft SQL Server Red Hat repository configuration file
sudo curl -o /etc/yum.repos.d/mssql-server.repo https://packages.microsoft.com/config/rhel/7/mssql-server.repo

This will download Microsoft SQL Server Package Repository Configuration File that are required to install SQL Server and SQL Server Agent.

As we have the Agent repository configuration file now, Let us first check the SQL Server in SSMS to see how SQL Server Agent working.  You can see we are not able to do anything in SQL Server Agent folder.

Now our next step is to install SQL Server Agent to enable its related features. Run below command to start the installation.

#Install SQL Server Agent
sudo yum install mssql-server-agent

You cans see series of executions started to proceed with the installation in below image. It will also ask you to enter Y to proceed.

Enter Y to proceed with the installation, once you press enter it will proceed to install. Now SQL Server Agent will install on your machine.

It will also suggest you to restart SQL Server service. If you will not restart SQL Server service, installation will not be completed so next step is to restart SQL Server service on this server.

#Restart SQL Server Service
systemctl restart mssql-server

You can see SQL Server is online now. Go ahead and connect to SQL Server in SSMS as per below image.

Now you can create Agent jobs to automate database activities on your SQL Server instance.
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 Install SQL Server Agent on Red Hat Linux Server appeared first on Techyaz.com.

Before going ahead, we need to have a RedHat Linux server. If you have no idea about installing Linux server or creating a virtual machine where you can install Linux and SQL Server then i would recommend you to read below articles first.

• How to Create a Virtual Machine.
• How to Install RedHat Linux 7.3 on a virtual machine.

If you have installed SQL Server on Red Hat Linux server, you need to install SQL Tools to make database connection locally on the server. Make sure you have internet access on the Linux server where we are going to install SQL Tools. If your server does not have internet connection then you should read attached article about installing SQL Tools on RedHat Linux that are running without Internet.

Install SQL Tools on RHEL

As this Linux machine has internet connection so installing SQL Tools on this Linux machine will be quite easy. Let’s go ahead with the SQL Tools Installation on Red Hat Linux server that are connected to internet. Installation process is quite similar to the installation of SQL Server on Redhat Linux.

Let us first check the SQL Server service to make sure SQL Server is installed on this machine. Run below command to check the service.

#Check SQL Server Services
systemctl status mssql-server

We can see SQL Server is installed on this machine. Now check SQL Tools are installed on this machine or not by running sqlcmd utility. We can see this tool is not installed yet.

Now we will download the Microsoft SQL Tools Redhat repository configuration file by running below command to start the SQL Tools installation.

#Download Microsoft Red Hat repository configuration file
sudo curl -o /etc/yum.repos.d/msprod.repo https://packages.microsoft.com/config/rhel/7/prod.repo

You can see file is downloaded to the given folder location. You can see this in below screenshot.

Run below commands to install SQL Tools along with unixODBC package on this server. We need to install unixODBC because of dependency issue. First update all packages by running below command.

#Run package update.
sudo yum update

Once package update will complete. Run below command to install SQL Tools. Once you execute below command, a series of execution will start and show you the details of package that are going to install.

#Install SQL Tools.
sudo yum install -y mssql-tools unixODBC-devel

After series of execution, setup will ask you to accept the license terms. Type YES to accept the license terms.

I pressed enter button post accepting the license terms, again a series of execution started and SQL tools installation was completed within minutes.

Once SQL Tools will install, you can go ahead and check sqlcmd utility. If your Linux server is not able to recognize SQL Server Tools utilities sqlcmd or bcp we need to set path environment variables. Although, it is optional step but you should run below commands to add /opt/mssql-tools/bin/ to your PATH environment variable.

#Add /opt/mssql-tools/bin/ to your PATH environment variable.
echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bash_profile
echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bashrc
source ~/.bashrc

Let us see whether Linux is able to recognize SQL Tool or not in below screenshot. We can see now sqlcmd is throwing output.

Now you can go ahead and connect to your SQL Server instance locally by using sqlcmd tool. You can see i have connected to SQL Server Instance using sqlcmd in below screen.

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

The post Installing SQL Tools on Red Hat Linux appeared first on Techyaz.com.

Prerequisites

Before going ahead, we need to have a RedHat Linux server. If you have no idea about installing Linux server or creating a virtual machine where you can install Linux and SQL Server then i would recommend you to read below articles first.

• How to Create a Virtual Machine.
• How to Install RedHat Linux 7.3 on a virtual machine.

Below are the prerequisites that needs to have on your virtual machine in order to install SQL Server 2017.

• A Red Hat Linux Machine having Internet Connection
• RAM – 3.25GB
• Disk Space – 6GB
• Processor speed – 2 GHz
• Processor cores – 2 cores
• Processor type – x64

Install SQL Server 2017 on RHEL

Installing SQL Server 2017 on Redhat Linux is straight forward method if your server has internet connection and able to access online repositories. But if your Red Hat Linux machine does not have internet connection you can go with attached article Offline Installation of SQL Server 2017 on Red Hat Linux. Let us go with the SQL Server Installation on Redhat Linux server that have internet connection.

Connect to RHEL server locally or through PuTTY. Check whether SQL Server is previously installed on this machine by someone else or not. You can see SQL Server is not installed, we can see it by checking the SQL Server service. Now download the Microsoft SQL Server Redhat repository configuration file by running below curl command.

#Download Microsoft SQL Server Redhat repository configuration file
sudo curl -o /etc/yum.repos.d/mssql-server.repo https://packages.microsoft.com/config/rhel/7/mssql-server.repo

Next step is to install SQL Server on Linux machine. Run below command to update all package repository on Red Hat Linux server.

#Update Packages
sudo yum update

#Install SQL Server
sudo yum install -y mssql-server

I ran installation command which is showing in below image. A series of execution will start followed by checking the dependencies. If you will face any dependency issue, you should first resolve all missing dependencies then proceed with the installation. Setup will process and show you details of the packages which will be installing. You can see the details in below image.

SQL Server package is in downloading process. Once download will complete, installation process will start. This will take few minutes to install the package.

Now you can see SQL Server database engine is installed on this Redhat Linux server. Installation is not completed yet because setup suggests us to run mssql-conf utility to complete the installation. So next step is to run this process.

Setup is suggesting us to install a mssql-conf utility to accept the license terms and set the sa password. Run below command to configure SQL Server.

sudo /opt/mssql/bin/mssql-conf setup

This execution will ask us to accept the License terms, select the SQL Server edition and also tell us to set the sa password. Let us do that to complete this installation. Once you execute above command, it will ask as to enter YES to access the license terms. Type YES and press enter. Once you press enter post accepting license terms, setup will give you options to choose SQL Server edition. Select correct edition as per your requirement.

Once you choose SQL Server edition, it will ask you to set sa login password. The moment you set the sa password, SQL Server configuration will be completed and ready to use.

Now SQL Server is installed, but sometimes you may face issue connecting to your SQL Server instance. You need to run below commands to open the SQL Server port on the firewall on the Linux server.

#Open Firewall for SQL Server
sudo firewall-cmd --zone=public --add-port=1433/tcp --permanent
sudo firewall-cmd --reload

You can see above commands executed successfully. Port 1433 is already enabled on my machine. If this port is not open on your server it will display as success. Now, you can check the SQL Server service to validate this installation. Run the same command which we have run to check the SQL Server service before starting the installation.

#Check SQL Server Service
systemctl status mssql-server

Now your SQL Server is ready to use. You can connect to this instance using SSMS client tool. You can see i have connected to this instance using SSMS from my local host computer.

If you want to connect to SQL Server on this server only. You need to connect using sqlcmd utility. By default, sqlcmd tool does not install on Linux machine. We need to manually install it. Please visit this attached article to understand step by step process of installing SQL Tools on a Red Hat Linux Server. If you don’t have internet access you can follow another article to install SQL Tools on Redhat Linux server in Offline mode.

If your Linux virtual machine doesn’t have Internet connection, you should read:

• How to Install SQL Server 2017 on RedHat Linux in Offline Mode.
• Installing SQL Tools on RedHat Linux in Offline Mode.
• Install SQL Server Agent on RHEL running without Internet.
• How to install SQL Server on Ubuntu in Offline Mode.

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 Install SQL Server on Redhat Linux appeared first on Techyaz.com.

Related Articles:

• Installing SQL Server on Ubuntu Server
• SQL Server Installation on RedHat Linux

.NET Framework 3.5 Installation

There are two ways to install .NET Framework 3.5 on windows server.

• Using GUI
• Using Powershell

GUI Method

1. Login to Server and launch Server Manager, click on Manage and then select Add Roles and Features to start the Add Roles and Features Wizard.
2. On the Select installation type screen, select Role-based or feature-based installation.
3. Select the target server.
4. On the Select features screen, click on checkbox next to .Net Framework 3.5 Features.
5. On the Confirm installation selections screen, a warning will be displayed asking Do you need to specify an alternate source path?.  Here you can mount your Windows DVD ISO image. Or If your computer does not have access to Windows Update, click the Specify an alternate source path link to specify the path to the \sources\sxs folder on the installation media and then click OK. After you have specified the alternate source, or if the target computer has access to Windows Update, click the X next to the warning, and then click Install and it will be done.

Powershell Method

This is very simple method where you just need to run below powershell command with administrator right.

--Change the source location as per your source patch or location.
Install-WindowsFeature Net-Framework-Core -source c:\sxs

If your .NET framework 3.5 is already installed on your server then you will get below output by running above powershell command. It means .NET 3.5 is already installed on this machine. Read below section to learn how to check if .net 3.5 is installed on your machine.

Validate

Now you can check whether .NET framework 3.5 is installed on your server or not. Run below command to check if .NET 3.5 is installed or not.

--Check if .NET framework 3.5 is installed or not on your server.
Get-WindowsFeature *framework*

You can see .NET framework 3.5 is showing as installed on this machine. 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 Check and Install .NET framework 3.5 on your Server appeared first on Techyaz.com.

Before going ahead, we need a SQL Server Instance running on Ubuntu Linux Server. If you have no idea about installing Ubuntu server or SQL Server 2017 or creating a virtual machine where you can install Ubuntu/RHEL and SQL Server then i would recommend you to read below articles.

• How to Create a Virtual Machine.
• How to Install Ubuntu Linux 16.04 on a virtual machine.
• Installing SQL Server 2017 on Ubuntu Server – Offline Installation.
• Install SQL Tools on Ubuntu Server – Offline Installation.
• Install SQL Server Agent on Ubuntu – Online Method

Offline Installation of SQL Server Agent on Ubuntu

It is time consuming to install anything if your Ubuntu server has no access of internet. We generally call such installations as offline installation. Microsoft suggests below steps for offline installation of SQL Server Agent on Ubuntu server.

• Download SQL Server Agent packages.
• Move this downloaded package to your Ubuntu Linux Machine.
• Install the copied debian package on the server.
• Resolve Missing Dependencies, if you get any.

Now we will go step by step process with the screenshots that will help readers to understand whole process.

SQL Server Agent Offline Installation – Step by Step

Before moving ahead let’s check whether SQL Server Agent is installed or not on this machine. You can connect to SQL Server instance using SSMS on your local host. You can see we are able to see SQL Server Agent folder but it is grayed out and not accessible. We need to install SQL Server Agent on Ubuntu server to enable it.

You can check and verify SQL Server service by executing below command.

#Check SQL Server Service.
systemctl status mssql-server

You should proceed if SQL Server service is running fine. Next step is to start the package download and proceed with installation. Below is the image of SQL Server Agent Package which we will download to install SQL Server Agent.

Download the highlighted debian package for SQL Server Agent. You can download this package on machine or PC which is connected to the internet. Once package will be downloaded to your local PC, next step is to copy this packages to the Ubuntu Linux server that are running without internet connection. I used WinSCP tool to copy this file from machine where i have downloaded it to the Linux server. Make sure that there should be connectivity between both machine.

If you have not installed WinSCP, download it and install on your PC. Launch WinSCP tool and make a connection to Ubuntu server. There are two panes in WinSCp window. The files shows in left side pane is your local system and right side pane is your target Ubuntu server. Now we just need to drag the downloaded debian package from left side pane and drop it to right side pane to copy it to Ubuntu server. Agent file is copied now and we can see that files in both side panes.

Now we can connect to Ubuntu server and validate whether this file is copied there or not. Connect to Ubuntu server and check the files. We can see downloaded file is very much there on Ubuntu server. Now next step is to install this package. We will use the dpkg package to install it as we do for other applications on Ubuntu. Let’s install it by running below command.

#Install SQL Server Agent on Ubuntu
sudo dpkg -i mssql-server-agent_14.0.900.75-1_amd64.deb

This installation has suggested us to restart SQL Server service to complete this installation so go ahead and restart the service by executing below command.

#Restart SQL Server Service.
systemctl restart mssql-server

Now SQL Server Agent is installed on this server. Go ahead connect to this SQL Server Instance using SSMS from local host. This time you would be able to see SQL Server Agent folder enabled.

You can see SQL Server Agent is showing there. Now you can create any jobs on SQL Server to automate database activities.

Read more about SQL Server on RedHat Linux:

• Installing RedHat Linux 7.3 on a virtual machine.
• Install SQL Server 2017 on RedHat Linux – Offline Installation.
• How to Install SQL Tools on RedHat Linux – Offline Installation.
• SQL Server Agent Installation on RedHat Linux – Offline Installation.

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 Install SQL Server Agent on Ubuntu Server without Internet – Offline Installation appeared first on Techyaz.com.

• sqlcmd: Command-line query utility.
• bcp: Bulk import-export utility.

Before going ahead, we need a Ubuntu server and SQL Server 2017 running on that instance. If you have no idea about installing Ubuntu server or SQL Server 2017 or creating a virtual machine where you can install Ubuntu and SQL Server then i would recommend you to read below articles.

• How to Create a Virtual Machine.
• How to Install Ubuntu Linux Server on a virtual machine
• Installing SQL Server 2017 on Ubuntu Server – Offline Installation

SQL Tools Installation on Ubuntu – Offline/Without Internet

Installing any package on Ubuntu Linux is straight forward method if your server has internet connection and able to access online repositories. But it becomes painful if your Ubuntu server has no access of internet. We generally call such installations as offline installation. Microsoft suggests below steps for offline installation of SQL Server Tools on Ubuntu server.

• Download all sql tools related packages. i.e msodbc & mssql-tools
• Move these downloaded packages to your Ubuntu Server.
• Install the copied debian packages on the server.
• Resolve Missing Dependencies, if you get any.
• Set the Path environment Variables for this package.

Now we will follow step by step process with the screenshots that will help readers to understand this process.

Download & Copy SQL Tools Packages to Ubuntu Server

Before moving ahead let’s check whether SQL Server is installed or not on this machine. Run below command to check the SQL Server service.

#Check SQL Server Service
systemctl status mssql-server

We can see SQL Server is installed and running fine on this server. Now you can just type sqlcmd to check sql tool is installed or not. We can see it is not installed yet. As we can see SQL Tools are not installed so next step will package download and installation of that package.

Let’s start with downloading the debian package for SQL Tools. You can download the required SQL Tools debian packages for Ubuntu from the attached link or from Microsoft Repositories. You can download these packages on a machine or PC that is connected to the internet. Below are the list of debian packages which needs to be downloaded to install sql tools.

• msodbcsql_13.1.6.0-1_amd64.deb
• mssql-tools_14.0.5.0-1_amd64.deb

SQL Tools package installation depends on msodbcsql package that must be installed first to avoid any dependency issue. Once package will be downloaded on your local PC, next step is to copy above downloaded packages to the Ubuntu server that are running without internet connection.

You can use any tool, application or method to copy this file from localhost to Ubuntu Linux server. I used WinSCP tool to copy this file from machine where i have downloaded the package to the Ubuntu Linux server. Make sure that there should be connectivity between both machine.

If you have not installed WinSCP yet, download and install it on your PC. Launch WinSCP tool and make a connection to Ubuntu server. I have explained about WinSCP in my last articles, you can follow it to get more details. Once you established the connection, WinSCP will look like below image.

Now we just need to drag the downloaded debian packages from left side pane and drop it to right side pane to copy it to Ubuntu Linux server. Files are copied now and we can see them in both side panes.

You can see SQL Tools packages are copied to location \home\techyaz\ in above screenshot. Now we can connect to Ubuntu server and validate whether files are copied there or not.

Connect to Ubuntu server and check the files. You can run ls -lrt to check the files. Once packages will be copied to ubuntu server, next step is to first install msodbcsql package. Run below command to start the installation.

#Install msodbcsql package
sudo dpkg -i msodbcsql_13.1.6.0-1_amd64.deb

Here we will use dpkg package management system for installation because SQL Tools are debian packages for Ubuntu servers. We can see below dependencies error while executing msodbc package. Now our next step is to fix these dependency issues and then kick off the installation again.

Resolve Dependencies

We can see msodbcsql package depends on unixODBC package so first we need to download, move and install unixODBC package on Ubuntu server.

Resolving dependencies are painful job because every package has some dependencies and you need to download and install all such packages manually if you don’t have internet connection on Ubuntu server. If your Ubuntu server has internet connection, all dependencies will be installed using online repository.

Now let’s download and move unixODBC package to Ubuntu server. We can download all required debian packages from attached link.  We can see unixODBC package has been copied to the server now in below image.

Install this package now.

#Install unixODBC Package.
sudo dpkg -i unixodbc_2.3.1-4.1_amd64.deb

We can see this package has another dependency error. That means UnixODBC package is dependent on given packages i.e. libodbc1 & odbcinst1debian2.

When i downloaded libodbc1 and tried to install it, this package failed because of another dependency.

We can see the dependent package in above image. I downloaded package libltdl7 and installed on Ubuntu server. libltdl7 package got installed successfully without any dependency error.

Once libltdl7 package will be installed, next step is to install all dependencies in reverse order. Here we will install libodbc1 then unixodbc followed by msodbcsql package.

We have seen, there were two dependencies to install unixODBC package. One libodbc1 has been installed. Please perform similar exercise to install another dependency odbcinst1debian2. Once both packages will be installed, go ahead and install unixodbc in order to install msodbcsql package.

If you want to check all dependencies for these packages, you can get it by running below command.

#Check dependencies of both packages.
dpkg -I msodbcsql_13.1.6.0-1_amd64.deb | grep "Depends:"
dpkg -I mssql-tools_14.0.5.0-1_amd64.deb | grep "Depends:"

If you have internet connection on your Ubuntu server then this task will be very easy to perform. You just need to execute below command to install unixodbc package.

#Install unixodbc on Ubuntu if server is connected to Internet.
sudo apt-get -f install unixodbc

SQL Tools Installation

We have resolved all dependencies errors in above section. Now we will install SQL Tools to establish database connection to SQL Server instance from ubuntu server. Run below command to install the msodbcsql package again post resolving dependencies.

#Install msodbcsql Package
sudo dpkg -i msodbcsql_13.1.6.0-1_amd64.deb

Once you will execute above command, you will get below screen to accept the license terms. Choose Yes and press enter button to proceed.

Once you press enter, package execution will start. You can see msodbcsql package is installed successfully now.

Next we will install another package mssql-tools now. Run below command to start the installation.

#Install mssql-tools Package
sudo dpkg -i mssql-tools_14.0.5.0-1_amd64.deb

Again this package will ask you to accept the license terms just like msodbcsql package. Choose yes and press enter to proceed.

You cans see mssql-tools package is installed in below image.

Final step is to set the path environment variables. Run below command to set the path environment variables. Ubuntu will not be able to recognize sqlcmd utility unless you set the path environment variable. You can see that in below screenshot. Ubuntu is able to recognize sqlcmd utility once we set the path environment variables.

#To make sqlcmd/bcp accessible from the bash shell for login sessions, modify your PATH in the ~/.bash_profile file
echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bash_profile

#To make sqlcmd/bcp accessible from the bash shell for interactive/non-login sessions, modify the PATH in the ~/.bashrc file
echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bashrc
source ~/.bashrc

Now connect to SQL Server instance using sqlcmd and run a command to validate this installation. I have checked the SQL Server version installed on ubuntu server.

We get above details that SQL Server 2017 is installed on this Ubuntu server by executing sqlcmd utility. Now we have done with SQL Tools installation on Ubuntu server. Go ahead and connect to your Ubuntu server using SQL Tools.

Read more about SQL Server on RedHat Linux:

• How to Create a Virtual Machine.
• Installing RedHat Linux 7.3 on a virtual machine.
• Install SQL Server 2017 on RedHat Linux – Offline Installation.
• How to Install SQL Tools on RedHat Linux – Offline Installation.
• SQL Server Agent Installation on RedHat Linux – Offline Installation.

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

The post Step by Step Process to Install SQL Tools on Ubuntu Server running without Internet – Offline Installation appeared first on Techyaz.com.