SQL 2008 R2 Express Edition Installation (NGAS)

SQL Server 2008 R2 Express
Edition Installation
Users’ Guide
1
SQL Server 2008 R2 Express Edition Installation
SQL Server 2008 R2 Express Edition

Installation Contents
Page
1.0 System Requirements……………………….…………………………………………………….………….. 2
2.0 How to Install SQL Server 2005………………………………………………………………….……….. 5
3.0 Getting Started with MS SQL Server 2005…………………………………………………….…….. 19
4.0 How to Restore a Database………………………………………………………………….…………….. 23

.
5.0 How to Create a Login………………..…........................................................................ 32
6.0 How to Run Scripts….……………………………………………………………………..…….….………… 35
7.0 How to Create a Database Backup……………………………………………………………..………. 39
8.0 How to Configure SQL Server Configuration Manager………………………………………… 44
Commission on Audit
Commonwealth Ave, Q.C
2
System Requirements 1.0
Component Requirement
Framework2 SQL Server Setup installs the following software components required by the product:
 .NET Framework 3.5 SP11
 SQL Server Native Client
 SQL Server Setup support files
Software2 SQL Server Setup requires Microsoft Windows Installer 4.5 or a later version
After installing required components, SQL Server Setup will verify that the computer
where SQL Server 2008 R2 will be installed also meets all the other requirements for a
successful installation.
Network Software Network software requirements for the 64-bit versions of SQL Server 2008 R2 are the
same as the requirements for the 32-bit versions.
Supported operating systems have built-in network software. Stand-alone named and
default instances support the following network protocols:
 Shared memory
 Named Pipes
 TCP/IP
 VIA
Note Shared memory and VIA are not supported on failover clusters.
The VIA protocol is deprecated. This feature will be removed in a future version of
Microsoft SQL Server. Avoid using this feature in new development work, and plan to
modify applications that currently use this feature.
Internet Software Microsoft Internet Explorer 6 SP1 or a later version is required for all installations of SQL
Server 2008 R2. Internet Explorer 6 SP1 or a later version is required for Microsoft
Management Console (MMC), SQL Server Management Studio, Business Intelligence
Development Studio, the Report Designer component of Reporting Services, and HTML
Help.
Virtualization SQL Server 2008 R2 is supported in virtual machine environments running on the Hyper-
V role in Windows Server 2008 SP2 Standard, Enterprise and Datacenter editions. The
virtual machine must run an operating system supported for the specific SQL Server 2008
Commission on Audit
3
R2 edition listed later in this topic.

In addition to resources required by the parent partition, each virtual machine (child
partition) must be provided with sufficient processor resources, memory, and disk
resources for its SQL Server 2008 R2 instance. Requirements are listed later in this topic.3
Within the Hyper-V role on Windows Server 2008 SP2, a maximum of four virtual
processors can be allocated to virtual machines running Windows Server 2008 SP2 32-bit
or 64-bit editions. A maximum of 2 virtual processors can be allocated to virtual
computers that are running Windows Server 2003 32-bit editions. For virtual computers
that host other operating systems, a maximum of one virtual processor can be allocated to
virtual computers. For more information about the Hyper-V role in Windows Server 2008
SP2.
Note Guest failover clustering is supported in SQL Server 2008 R2.
Hard Disk Disk space requirements will vary with the SQL Server 2008 R2 components you install.
Drive A CD or DVD drive, as appropriate, is required for installation from disc.
Display SQL Server 2008 R2 graphical tools require Super VGA or higher resolution: at least
800x600 pixel resolution.
Other Devices Pointing device: A Microsoft mouse or compatible pointing device is required.
The following requirements apply to all SQL Server 2008 R2 installations:

1. .NET Framework versions are required:
 SQL Server 2008 R2 on Windows Server 2003 (64-bit) IA64 — .NET Framework 2.0 SP2
 SQL Server Express — .NET Framework 2.0 SP2
 All other editions of SQL Server 2008 R2 — .NET Framework 3.5 SP1
Installation of .NET Framework requires a restart of the operating system. If Windows Installer
installation also requires a restart, Setup will wait until .NET Framework and Windows Installer
components have installed before restarting.
Note
Installing .NET Framework 2.0 SP2: .NET Framework 2.0 SP2 is not available as a separate download.
You will need to install .NET Framework 3.5 SP1 which includes .NET Framework 2.0 SP2.
2. SQL Server Setup will not install the following required components for SQL Server Express,
SQL Server Express with Tools, and SQL Server Express with Advanced Services. You must
install these components manually before you run SQL Server Setup:
 SQL Server Express — .NET Framework 2.0 SP2 and Windows installer 4.5. On Windows Vista
SP2, use .NET Framework 3.5 SP1.
 SQL Server Express with Advanced Services — .NET Framework 3.5 SP1, Windows Installer 4.5,
and Windows PowerShell 1.0.
Commission on Audit
4
 SQL Server Express with Tools — .NET Framework 3.5 SP1, Windows Installer 4.5, and
Windows PowerShell 1.0.
3. As with all virtualization technologies, SQL Server 2008 R2 running in a Windows Server
2008 SP2 Hyper-V virtual computer will be slower than on a physical computer with the same
physical resources.
Processor, Memory, and Operating System Requirements

 Reporting Services
Starting in SQL Server 2008 R2, the Reporting Services component no longer supports
Itanium-based servers running Windows Server 2003 or Windows Server 2003 R2. Reporting
Services continues to support other 64-bit operating systems, including Windows Server°2008
for Itanium-Based Systems and Windows Server°2008°R2 for Itanium-Based Systems. To
upgrade to SQL Server 2008 R2 from a SQL Server 2008 installation with Reporting Services
on an Itanium-based system edition of Windows Server 2003 or Windows Server 2003 R2, you
must first upgrade the operating system.
 WOW64
WOW64, a feature of 64-bit editions of Windows that enables 32-bit applications to run
natively in 32-bit mode. Applications function in 32-bit mode, even though the underlying
operating system is running on the 64-bit operating system. WOW64 is supported only for
stand-alone instances of SQL Server. WOW64 is not supported for SQL Server failover cluster
installations
For SQL Server 64-bit Edition installations on 64-bit supported operating systems,
Management Tools are supported in WOW64. For more information about supported
operating systems, select an edition of SQL Server 2008 R2 from the sections below.
On a supported 64-bit operating system, SQL Server 32-bit Edition installations can be
installed to the Windows on Windows (WOW64) 32-bit subsystem of a 64-bit server.
 Other operating system notes
SQL Server 2008 R2 is not supported on Windows Server 2008 SP2 Server Core or Windows
Server 2008 R2 Server Core installations.
Operating systems listed in the SQL Server Standard sections are also supported for SQL
Server Standard for Small Business
SQL Server editions that are supported on Windows Server 2008 R2 64-bit x64 Standard are
also supported on Windows Small Business Server 64-bit x64.
Commission on Audit
5
How to Install SQL Server 2008 2.0

1. Click SQLManagementStudio_x86_ENU for 32 bit computers;
SQLManagementStudio_x86_ENU for 64 bit computers.
Figure 2.1 2008 R2 Management Studio and Database Engine Installer
2. Wait for SQL Server 2008 R2 Setup
Figure 2.2 SQL Server 2008 R2 Initialization (Management Studio)
Commission on Audit
6
3. Choose New installation or add features to an existing installation.
Figure 2.3 SQL Server Installation Center (Management Studio)
4. Check I accept the licensing terms checkbox and click Next.
Figure 2.4 SQL Server 2008 R2 Setup : License Terms (Management Studio)
Commission on Audit
7
5. The Feature Selection will appear then check the Management Tools – Basic and SQL Client
Connectivity SDK checkboxes and click Next.
Figure 2.5 SQL Server 2008 R2 Setup : Feature Selection (Management Studio)
6. Click Next button.
Figure 2.6 SQL Server 2008 R2 Setup : Error Reporting (Management Studio)
Commission on Audit
8
7. Wait for the SQL Server setup.
Figure 2.7 SQL Server 2008 R2 Setup : Installation Progress (Management Studio)
8. SQL Server 2008 R2 installation completed successfully then click Close.
Figure 2.8 SQL Server 2008 R2 Setup : Completed Successfully (Management Studio)
Commission on Audit
9
9. Click Exit button from the upper right portion.
Figure 2.9 SQL Server Installation Center (Management Studio)
10. Click SQLManagementStudio_x86_ENU for 32 bit computers;

SQLManagementStudio_x86_ENU for 64 bit computers.
Figure 2.10 2008 R2 Management Studio and Database Engine Installer
Commission on Audit
10
11. Extracting Files
Figure 2.11 Extracting Files (Database Engine)
12. Wait for the SQL Server setup processes.
Figure 2.12 SQL Server 2008 R2 Initialization (Database Engine)
Commission on Audit
11
13. Choose New installation or add to an existing installation.
Figure 2.13 SQL Server Installation Center (Database Engine)
14. Check I accept the license terms checkbox and click Next.
Figure 2.14 SQL Server 2008 R2 Setup : Licence Terms (Database Engine)
Commission on Audit
12
15. Feature Selection will appear and click Select All then Next.
Figure 2.15 SQL Server 2008 R2 Setup : Feature Selection (Database Engine)
16. Instance Configuration will appear then put SQLExpressR2_[Agency Name] on Named instance
then Click Next.
Figure 2.16 SQL Server Server 2008 R2 Setup : Instance Configuration (Database Engine)
Commission on Audit
13
17. In Server Configuration click Service Accounts then in the Startup Type choose both Automatic.
Figure 2.17 SQL Server 2008 R2 Setup : Server Configuration (Database Engine)
18. Click Collation tab and click Customize.
Commission on Audit
14
19. Click the SQL collation, used for backwards compatibility and choose
SQL_Latin1_General_CP1_Cl_AS then click Ok button.
NOTE: Make sure to choose the right collation for it will affect the report generation, login
connections in eNGAS, eBudget and Security Systems. There is no other way in changing the
collation once Database Engine successfully installed, you need to re-install it then choose the
right collation.
Figure 2.19 Customize the SQL Server 2008 R2 Database Engine Collation
20. Click Next.
Commission on Audit
15
21. Click Mixed Mode (SQL Server authentication and Windows authentication) and click Add
Current User then Next.
NOTE: Remember your password for sa (System Administrator) account.
Figure 2.21 SQL Server 2008 R2 Setup : Database Engine Configuration – Account Provisioning (Database Engine)
Commission on Audit
16
22. In Data Directories tab, change the location path the following then click Next.
a. User database directory
b. User database log directory
c. Temp DB directory
d. Temp DB log directory
e. Backup directory
NOTE: For security purposes, we are advising to create folder for Data Files and DB Backup in
other partition of your Computer (Local D:\).
Figure 2.22 SQL Server 2008 R2 Setup : Database Engine Configuration – Data Directories (Database Engine)
Commission on Audit
17
23. Click Next
Figure 2.23 SQL Server 2008 R2 Setup : Error Reporting (Database Engine)
24. Wait for the Installation Progress to finish.
Figure 2.24 SQL Server 2008 R2 Setup : Installation Progress (Database Engine)
Commission on Audit
18
25. SQL Server 2008 R2 installation completed successfully. Click Close.
Figure 2.25 SQL Server 2008 R2 Setup : Installation Completed Successfully (Database Engine)
26. Click Exit button from the upper right portion.
Figure 2.26 SQL Server Installation Center (Database Engine)
Commission on Audit
19
Getting Started with MS SQL Server
2008 R2 Express Edition 3.0
1. Search for the SQL Server Management Studio installed in your computer.
Figure 3.1 Accessing SQL Server Management Studio installed
2. Connecting to server
A. Using System Administrator
Server Name : [Computer Name] \ [Database Engine Instance Name] (see Figure 2.14 for
your instance name)
Login : sa
Password: (see Figure 2.19)
Commission on Audit
20
Figure 3.2 Connecting to Server using “sa” account
a. If you have multiple servers, click the drop down in Server name section then
choose Browse for more to make sure you are using the right Database Engine.
NOTE: Multiple server names will appear if you installed SQLEXPRESS more than one.
Figure 3.3 Connecting to Server with multiple server names
Commission on Audit
21
b. Click the correct Instance Name (see Figure 2.14) then OK.
Figure 3.4 Browse for Servers
B. Using the Windows Authentication Mode
Figure 3.5 Connecting to Server using Windows Authentication Mode
Commission on Audit
22
3. You are now connected in your Server.
Figure 3.6 Successfully connected to Server
Commission on Audit
23
How to Restore a Database 4.0

1. Right click Database and choose Restore Database…
Figure 4.1 Restoring Database
2. Type engas_uacs as your Database Name and click From Device’ Radio Button and its
Ellipsis Button.
Figure 4.2 Restoring eNGAS Database
Commission on Audit
24
3. Click Add button
Figure 4.3 Specify Backup for eNGAS
4. For blank engas database, choose the engas database from the training folder provided
under DATABASES Folder then click Ok.
NOTE: Navigate to your DB Backup Folder if you want to restore your own backup file.
Commission on Audit
25
Figure 4.4 Choosing the blank eNGAS database.
5. Click OK.
Figure 4.5 Specify Backup for eNGAS after choosing the backup file
Commission on Audit
26
6. Make sure to check the checkbox of your database file before clicking Ok.
Figure 4.6 Restoring eNGAS Database after choosing the file
7. Restore of database completed successfully. Click OK.
Figure 4.7 Restoring eNGAS database completed successfully
Commission on Audit
27
8. You can now see the database you restored.
Figure 4.8 eNGAS database restored
9. Now, restore eBudget database. Right click Databases then choose Restore Database (see
Figure 4.1)
10. Type budget_uacs as your eBudget Database Name and click From Device’ Radio Button and
its Ellipsis Button.
Commission on Audit
28
Figure 4.9 Restoring eBudget Database
11. Click Add.
Figure 4.10 Specify Backup for eBudget
Commission on Audit
29
12. For blank eBudget database, choose the budget database from the training folder provided
under DATABASES Folder then click Ok.
NOTE: Navigate to your DB Backup Folder if you want to restore your own backup file.
Figure 4.11 Locate Back Up File
Commission on Audit
30
13. Click OK.
Figure 4.12 Specify Backup for eNGAS after choosing the backup file
14. Make sure to check the checkbox of your database file before clicking Ok.
Figure 4.13 Restoring eBudget Database after choosing the file
Commission on Audit
31
15. Restore of database completed successfully.
Figure 4.14 Restoring eBudget database completed successfully
16. You can now see the databases you restored, engas_uacs and budget_uacs under
Databases.
Figure 4.15 eBudget database restored
Commission on Audit
32
How to Create a Login 5.0
1. Add new login. Navigate to Security > Logins, right click Logins then choose New Login.
NOTE: This is one time setup only.
Figure 5.1 Creating new login
2. In General tab, fill up the following setups (this is a permanent login name and
password, should not be changed):
Login name: ngas_sysadmin

Password: perfect
Uncheck Enforce Password Policy
Commission on Audit
33
Figure 5.2 Creating new login : General
3. In Server Roles tab, check sysadmin checkbox then click OK
Figure 5.3 Creating new login : Server Roles
Commission on Audit
34
4. You can now see the newly created login.
Figure 5.4 New login created
Commission on Audit
35
How to Run Scripts 6.0
1. Run the script, change dbusername and dbpassword to ngas sysadmin.sql. Double click
it or drag the highlighted script in the below figure to your MS SQL Server Management
Studio.
Figure 6.1 Choosing changing dbpassword of sysadmin.sql to be run
2. Make sure that you are in the right database name (engas_uacs) before clicking
Execute.
Figure 6.2 Running script : changing dbpassword of sysadmin.sql
Commission on Audit
36
3. Run the script EXEC BS_SP_LINK_WITH_ENGAS.sql to link eBudget System to eNGAS

System.
Figure 6.3 Choosing EXEC_BS_SP_LINK_WITH_ENGAS.sql to be run
4. Make sure that you are in the right database name (budget_uacs) and engas database
name (engas_uacs) should be in the close brackets then click Execute.
Figure 6.4 Running script : EXEC_BS_SP_LINK_WITH_ENGAS.sql.sql
Commission on Audit
37
5. Run the script Security_sysadmin.sql to eNGAS System.
Figure 6.5 Choosing Security_sysadmin.sql to be run
6. Make sure that you are in the right database name (engas_uacs) before clicking
Execute.
Figure 6.6 Running script : Security_sysadmin.sql in eNGAS System
Commission on Audit
38
7. Change database name to “budget_uacs” then click Execute
Figure 6.7 Running script : Security_sysadmin.sql in eBudget System
Commission on Audit
39
How to Create a Database Backup 7.0

1. Right click on the database you want to back up then navigate to Task > Back up…
Figure 7.1 Back up eNGAS database
Commission on Audit
40
2. In Back Up Database General tab, click Add, Select Back up Destination Window will appear.
Click the ellipsis button to select the destination of your back up.
Figure 7.2 Select Back up Destination
3. Select the path of your back up folder and type for the filename of your backup then click Ok.
We recommend to use the following format of your back up:
[database_name]_[Date]_[Time].bak
Ex. engas_uacs_03012015_1PM.bak
NOTE: We suggest that you always change the filename of your database every time you back
up.
Commission on Audit
41
Figure 7.3 Backup destination and backup filename
4. Click Ok.
Figure 7.4 Specify Back Up Destination with database filename
Commission on Audit
42
5. Click the right path or location then click Ok.
Figure 7.5 Back up database
a. You will see the below image if you click the Options. You can choose if you
want to append or overwrite the existing back up sets. Check also the Verify
backup when finished.
Commission on Audit
43
Figure 7.6 Back up Database : Options
6. The backup of eNGAS database completed successfully. Click OK.
Figure 7.7 Back up of eNGAS Database completed successfully
Commission on Audit
44
How to Configure SQL Server

Configuration Manager 8.0
1. Search for the SQL Server Configuration Manager installed in your computer.
Figure 8.1 Open SQL Server Configuration manager
2. You will see the below image
Figure 8.2 SQL Server Configuration Manager Screen
Commission on Audit
45
3. Click SQL Server Services on the left side of the screen and make sure that the SQL
Server Browser and SQL Server is running. If not, right click then click Start.
Figure 8.3 SQL Server Servces
a. Enabling SQL Server Browser if not set to Automatic. Right click the SQL Server
Browser and click Properties.
Figure 8.4 Enabling SQL Server Browser
Commission on Audit
46
b. Navigate to Service Tab > Start Mode and choose Automatic. Click Apply then Ok.
Figure 8.5 SQL Server Browser Properties
c. To start it, right click the SQL Server Browser and click Start.
Figure 8.6 Starting SQL Server Browser
Commission on Audit
47
4. Navigate to SQL Server Network Configuration Tab and double click the Protocols for
your Instance
Figure 8.7 SQL Server Network Configuration
5. Enabling Protocols, right click on Named Pipes, TCP/IP and VIA and click Enable.
Figure 8.8 Enabling SQL Server Network Configuration Protocols
Commission on Audit
48
Figure 8.9 All Protocols Enabled
6. Double click on the TCP/IP. Make sure that it is enabled.
Figure 8.10 TCP/IP Properties : Protocol Tab
Commission on Audit
49
7. Navigate to IP Addresses Tab and put the IP Address of your Server / PC Server on IP
Address Section and click Apply.
Figure 8.11 TCP/IP Properties : IP Addresses
8. Click OK.
Figure 8.12 TCP/IP Warning Dialog Box
Commission on Audit
50
9. Click Ok
Figure 8.13 TCP/IP Properties
10. We need to restart the SQL Server in order to take effect the changes in our TCP/IP.
Navigate to SQL Server Browser > SQL Server Browser. Right Click SQL Server Browser
and click Restart.
Figure 8.14 Restarting SQL Server
Commission on Audit
51
Things to remember:
1. Windows Firewall should be turned off in both PC Server and Clients (during training)
2. Static IP should be set in both PC Server and Clients (during training)
a. Navigate to your connection’s properties. Select Internet Protocol Version 4 (TCP/IPv4) and
click Properties.
Figure 8.15 Wi-Fi Properties
Specify the
Commission on Audit
52
b. Specify the IP Address and the Subnet Mask then click Ok.
Figure 8.16 Internet Protocol Version 4 (TCP/IPv4) Properties.
Commission on Audit

SQL 2008 R2 Express Edition Installation (NGAS)

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

SQL 2008 R2 Express Edition Installation (NGAS)

Încărcat de

Drepturi de autor:

Formate disponibile

SQL Server 2008 R2 Express

SQL Server 2008 R2 Express Edition

1.0 System Requirements……………………….…………………………………………………….………….. 2

2.0 How to Install SQL Server 2005………………………………………………………………….……….. 5

3.0 Getting Started with MS SQL Server 2005…………………………………………………….…….. 19

4.0 How to Restore a Database………………………………………………………………….…………….. 23

6.0 How to Run Scripts….……………………………………………………………………..…….….………… 35

7.0 How to Create a Database Backup……………………………………………………………..………. 39

8.0 How to Configure SQL Server Configuration Manager………………………………………… 44

System Requirements 1.0

R2 edition listed later in this topic.

Drive A CD or DVD drive, as appropriate, is required for installation from disc.

The following requirements apply to all SQL Server 2008 R2 installations:

Processor, Memory, and Operating System Requirements

How to Install SQL Server 2008 2.0

Figure 2.1 2008 R2 Management Studio and Database Engine Installer

2. Wait for SQL Server 2008 R2 Setup

Figure 2.2 SQL Server 2008 R2 Initialization (Management Studio)

3. Choose New installation or add features to an existing installation.

Figure 2.3 SQL Server Installation Center (Management Studio)

4. Check I accept the licensing terms checkbox and click Next.

6. Click Next button.

7. Wait for the SQL Server setup.

8. SQL Server 2008 R2 installation completed successfully then click Close.

9. Click Exit button from the upper right portion.

Figure 2.9 SQL Server Installation Center (Management Studio)

10. Click SQLManagementStudio_x86_ENU for 32 bit computers;

Figure 2.10 2008 R2 Management Studio and Database Engine Installer

11. Extracting Files

Figure 2.11 Extracting Files (Database Engine)

12. Wait for the SQL Server setup processes.

Figure 2.12 SQL Server 2008 R2 Initialization (Database Engine)

13. Choose New installation or add to an existing installation.

Figure 2.13 SQL Server Installation Center (Database Engine)

18. Click Collation tab and click Customize.

20. Click Next.

NOTE: Remember your password for sa (System Administrator) account.

23. Click Next

24. Wait for the Installation Progress to finish.

25. SQL Server 2008 R2 installation completed successfully. Click Close.

26. Click Exit button from the upper right portion.

Figure 2.26 SQL Server Installation Center (Database Engine)

Getting Started with MS SQL Server

2008 R2 Express Edition 3.0

Figure 3.1 Accessing SQL Server Management Studio installed

A. Using System Administrator

Figure 3.2 Connecting to Server using “sa” account

Figure 3.3 Connecting to Server with multiple server names

Figure 3.4 Browse for Servers

B. Using the Windows Authentication Mode

Figure 3.5 Connecting to Server using Windows Authentication Mode

3. You are now connected in your Server.

Figure 3.6 Successfully connected to Server

How to Restore a Database 4.0

Figure 4.1 Restoring Database

Figure 4.2 Restoring eNGAS Database

3. Click Add button

Figure 4.3 Specify Backup for eNGAS

Figure 4.4 Choosing the blank eNGAS database.

Figure 4.6 Restoring eNGAS Database after choosing the file

7. Restore of database completed successfully. Click OK.

Figure 4.7 Restoring eNGAS database completed successfully

8. You can now see the database you restored.

Figure 4.8 eNGAS database restored