In this video we'll be installing
SQL Server 2012 Express as part of our
PI Server installation. In the previous
video, we planned out our installation by
reviewing documentation, reviewing PI system
components, decided on architecture as well as
machine sizing. And lastly we downloaded all of the relevant
information from Tech Support website including
documentation as well as all of the install
kits. If you already have a SQL Server
installed or available to you on the network, you can continue
with our next video where we'll install the PI Server
itself. So the first step we'll want to take
in installing our SQL Server is to review the
documentation. In our last
video, we downloaded a white paper on installing SQL Server
that we'll want to pull up now. With
that up I'll want to review what pre-requisites
I'll need before I can begin this
installation. It looks like they are on
page 5 and it looks like we have 3
pre-requisites. Those pre-requisites are Microsoft .NET Framework
3.5, .NET Framework 4
as well as Power Shell 2.0
In Windows Server 2012, .NET Framework 3.5
is no longer installed by default. So I know
I'll have to add it manually. The other two components are
already present. So to
install 3.5, I will need
to open up my Server
Manager and once that open, I need to go to
Manage, and I'll want to
add a feature which is the
Microsoft .NET Framework 3.5
From here, I'll
follow the Wizard's prompts and
go to Feature Installation and I want to install it on my PISRV
machine. Continue down to
Features and we'll see enable .NET
Framework 3.5 and I'll go ahead and click next.
You'll notice here there is a
warning label at the top of our screen and it
looks like it's saying that we are missing some source
files to install this feature. If we try to just
click next and install,
the installation will fail unless we are connected to the
internet. Thankfully Microsoft
has published a KB article on this
topic, the KB
number is
2734782.
And if we take a look at
that,
this gives us the information
that these are error codes because the computer cannot connect
to the internet and download 3.5. So
they go through a few methods here of how to
correct this problem. What we are going to be doing
is using this method 4
where we can specify
an alternate source path for these
installation files. So let's go ahead and do that
in Server Manager. So I can
come down to the bottom here and specify an alternate
source path. I've already downloaded
these files onto my
local machine. So I'll just need to point the installer to them.
So I'll copy
this path and then
specify it here.
With that specified I should be able to click
install and .NET Framework 3.5 should
install.
Alright. So it looks
like our .NET Framework
3.5 has finished installing. So I can
go ahead and click close. Also
can close out all of my other windows.
So now that our pre-requisites
for SQL Server are done, we can move onto
installing the SQL Server. It is important to note
that we are installing SQL only for
AF and we'll mainly be keeping the defaults
where possible. For more information on best practices
with SQL, there are some more details in the white paper
that we brought up previously as well as
available for Microsoft. So
now what I'll want to do is I can use my
white paper and navigate down to the next
step and see that it'll want me to run
the setup file as an administrator. In order to do
that, I must be part of the administrator
group. I can check on that by
going to Computer
Management and then checking my local users and groups.
So if I look
under Groups, there is a group for
administrators. And I can see my name right
there as part of the administrators
group. So I should be able to run it as
administrator. So what I'll do now is
navigate to my install
kit
and I can right click and run it as
administrator.
So it looks like
our installation package is ready.
So what we are going to do is
select a new SQL Server. And through this
process, I'm going to be following the steps outlined
in that white paper.
OK, so our first step is to
accept the license terms.
And then SQL will
check for any product updates that are
available.
It looks like it has found one update for us, so I'll
go ahead and install
that.
OK,
so now we can see we
are ready to do some configuration. If
we look over here on the right, we
can see that our pre-requisites
are installed. Like I mentioned, we enabled 3.5
and Power Shell and the .NET Framework 4.0 were already on the
machine. And it looks like the install kit will take
care of the 2010 shell.
So we can leave all the defaults
on this page as that's all the AF Server requires. So I'm
going to go ahead and select next.
Now we have the option to
name our instance. We can just
leave this as the default and
click next.
OK, and now we have the option
to configure service
accounts. So it's best practice that the SQL Server
run under a low privileged account which is a network
service or a specific service account on the domain that has been
given only the correct permissions. In our
case, this NT service SQL Server
account will work. And we also can
configure the SQL Server browser.
In this case, we are going to disable
this as we do need remote connections to the SQL
Server and that's its only purpose, so we are going to
disable it as a security check.
We can also take a
look at the next tab. However we will just leave this as
default and click next.
So next we need
to specify our authentication
mode as well as our SQL Server
administrators. OSIsoft recommends you leave the
Windows authentication mode
checked. And so also recommend this for the SQL Server
administrators, that
instead of a single user, it's pointed
to a group. So in this case, the install
kit has accepted me as the only administrator
because by default it adds the person
running the install kit to this list. We'll want to
change that and add the local
administrators group from this computer. So I'll go
ahead and click Add,
Locations.. I'll click PI Server which is our
local machine. And the box here I'll
type administrators. And then I can
check names and click OK.
So now you can see our administrators
group for the local machine is added and as
we've checked at the beginning of this video, I'm part of that
group. So I'll go ahead and remove my own name
which will make it a lot easier to manage permissions later.
Next we can check on the data
directories tab. We are going to leave these
as default. User instances,
we are going to disable as it is not
used by PI AF. And file stream,
we are going to leave the default, we
can then select next. Error reporting is our final
configuration option before the install proceeds.
This is completely optional
but I'll go ahead and check the option
to send these errors and click next which will begin our install.
OK, so it looks like our
installation has completed and we can check to make sure that all the steps
succeeded. And if they did, we
can go ahead and click close. And now we are
done with the install of
SQL Server 2012 Express.
Now we are ready to install the PI Server,
starting with the PI AF Server. And we'll do
that in our next video.