Network Admin

&KDSWHU 'DWDEDVH$GPLQLVWUDWLRQ²
0LFURVRIW64/6HUYHU
&RQWHQWV
Overview ................................................................................................................13–2
Starting and Stopping the Database ...................................................................13–2
Database Performance .........................................................................................13–4
Scheduling Database Tasks (DB13)....................................................................13–9
Checking the Database Backup (DB12)............................................................13–15
Initializing Backup Tapes ...................................................................................13–18
Database Backups with Microsoft Tools..........................................................13–19
Database Error Logs...........................................................................................13–28
Verify Database Consistency.............................................................................13–29
Run Update Statistics .........................................................................................13–29
System passwords .............................................................................................13–30
System Administration Made Easy 13–1

Chapter 13: Database Administration – Microsoft SQL Server
Overview
2YHUYLHZ
Microsoft SQL Server is a low maintenance database that is increasingly popular with smaller R/3
installations. This chapter will review the database administrative tasks that can be accomplished within
the R/3 System with associated tasks utilizing the Microsoft administrative tools.
6WDUWLQJDQG6WRSSLQJWKH'DWDEDVH
6WDUWLQJWKH'DWDEDVH
1. From the NT desktop, choose Start → Programs → MS SQL Server 7.0 → Service Manager.
2. Choose Start/Continue.
3. Check that Microsoft SQL Server

is started by checking the color
and shape of the status icon (the
green arrow), and the status
message at the bottom of the
window.
Release 4.6A/B
13–2
Starting and Stopping the Database
6WRSSLQJWKH'DWDEDVH
1. Verify that R/3 has been stopped.
If R/3 has not been stopped, stop R/3 now.
Follow the proper procedure to stop R/3.
2. From the NT desktop, choose Start→ Programs→ MS SQL Server 7.0 →Service Manager.
3. Choose Stop.
4. Choose Yes.
5. Check that Microsoft SQL Server

is stopped by checking the color
and shape of the status icon (a red
square), and the status message at
the bottom.
For more information on stopping the database, see chapter 9.
System Administration Made Easy

13–3
Database Performance
'DWDEDVH3HUIRUPDQFH
2YHUYLHZ
The CCMS System has tools available for R/3 Administrators to monitor the database for
growth, capacity, I/O statistics, and alerts. This section will discuss the initial transactions
that can help the database administrator.
'DWDEDVH$FWLYLW\67
:KDW
The Database Performance Monitor (ST04) provides a database-independent tool to analyze

and tune the following components:
< Memory and buffer usage
< Space usage
< CPU usage
< SQL requests
< Detailed SQL items
:K\
To manage your system performance, the database must be monitored. One of the
important items is the ability to view the database error log from within R/3. This view
saves the extra effort of logging into the database to view this log.
Release 4.6A/B
13–4
+RZ
*XLGHG7RXU

1. In the Command field, enter transaction ST04 and choose Enter

(or from the SAP standard menu, choose Tools → Administration → Monitor → Performance → Database →
ST04 - Activity).
2. An initial overview of database activity is
provided which pertains to database,
operating system, CPU, and memory.
Microsoft SQL Server allows the analysis
of specific attributes pertaining to 2d
memory, space, I/O, and quality of table
reads and writes. This information can
signal adjustments necessary to improve
performance of the database.
In the screen to the right, some important
areas are highlighted: 2a 2a
a. Memory Usage
Procedure cache and Data cache hit
ratio can reflect memory problems.
These values should be greater than 2b
95 percent for optimal memory usage.
b. Server Engine/Elapsed 2c 2c
Shows how hard the CPU has been
working on Microsoft SQL Server
processes. You are interested in the
ratio of busy : idle time.
c. SQL Requests
Allows for snapshots of how SQL
queries are utilizing table access
pertaining to full table or index scans.
A high ratio of full table scans vs. index
scans can indicate performance
bottlenecks.
d. Detail analysis menu

13–5
3. This screen is the Detailed analysis menu

(option 2D).
c. This screen is composed of the
following three sections:
< Analyze database activity 3a
< Analyze exceptional conditions 3b 3b

< Additional functions
d. Areas of common interest are: 3a
< Server details
< SQL processes 3b
< Error logs (see the following screen)
c. Additional functions are links to 3a
transactions that will be discussed in 3c
later sections.
This screen shows the Database Error Log.
3b
Release 4.6A/B
13–6
'DWDEDVH$OORFDWLRQ'%
:KDW
The Database Allocation transaction is used to analyze:

< Database growth
< Database index, consistency, etc.
< Tables
:K\
One critical reason is to monitor database growth. Using the growth rate you could project
the growth to determine when you may need to get additional disk storage for the database.
+RZ
*XLGHG7RXU

1. In the Command field, enter transaction DB02 and choose Enter

(or from the SAP standard menu, choose Tools → Administration → Monitor → Performance → Database→
DB02-Tables/Indexes).
2. An initial review would identify
the type of database, name, size,
file systems, and totals for
database objects.
The following describes some of
the features of the screen to the
right:
2a
a. Database information indicates 2b
space used for data and log
information. 2c
b. DB space history takes you to

the View database history screen.
c. DB analysis takes you to an
analysis menu screen.
d. To determine attributes for a
specific database object, use
Detail analysis to make 2d
decisions for an individual
object.

13–7
This screen is the DB space history

display.
A spreadsheet allowing analysis
1
based on calendar scenarios exists
with the ability to sort on column
information.
1. To view by file, choose Files.
Here you can analyze the physical

file information.
This screen is the DB analysis

display.
From here, the administrator can:
< Analyze the database for
missing indexes, conflicts
between ABAP Dictionary and
database, and R/3 Kernel
integrity.
< Perform a database
consistency check.
Analysis can be done for table
specific objects to determine the
largest tables, and tables that are
modified.
Release 4.6A/B
13–8
Scheduling Database Tasks (DB13)
6FKHGXOLQJ'DWDEDVH7DVNV'%
:KDW
The DBA Planning Calendar (DB13) is the scheduling tool for DBA tasks in R/3. Using the
Calendar, the DBA can schedule many of the DBA tasks that need to be performed, such as:
< Database and transaction log backup
< Update statistics
< Check table and database consistency
:K\
These tasks can be conveniently managed and scheduled without going to the database. The
DBA Planning Calendar works with transaction DB12 (Backup logs). For more information on
transaction DB12, see page 13–15.
+RZ
To schedule a backup task using the DBA Planning Calendar, the backup must be able to
run “unattended,” which means that you must have one of the following options:
< A single tape drive with sufficient capacity to back up the database without changing
tapes.
< Multiple tape drives with sufficient total capacity to back up the database without
changing tapes.

13–9
*XLGHG7RXU

1. Enter transaction DB13 and choose Enter.

(or from the SAP standard menu, choose Tools → CCMS → DB Administration → DB13-DBA Planning
Calendar).
2. Double-click on the date.
If a task exists for that day, this

window appears.
3. Choose Insert to add a new task.
Release 4.6A/B
13–10
4. In StartTime, enter the time to begin

the backup. 4
The start time is the time on the

database server.
5. Under Action, select a task (for
example, Full Database Backup).
6. Choose Continue.
7. Select all the databases.

8. Choose OK.
8
9. Select the backup device.
(Select R3DUMP0 if you only have
a single tape drive attached.)
9
10. Choose OK.
10

13–11
11. In the Log backup tape options pop-

up window, select the following
options as appropriate: 11a
a. Unload tape
To eject the tape after the 11b
backup is completed.
b. Initialize tape
To overwrite existing data, 11c
rather than appending to last
backup.
11d
c. Verify backup
To verify the backup after it has
run.
If you are doing an online 12
backup when transactions are
being performed, selecting this
option is not useful because the
database changes during this 13
time will cause this test to fail.
d. Format tape
To erase the entire tape and
write a new tape label.
This option is selected when
using a brand new tape, or a
tape that was previously used
with a different application.
12. In Expiration period for backup
volumes, enter the number of days
to protect the tape.
The backup tape is protected from
overwriting by the backup
program for this number of days.
13. Choose OK.
Release 4.6A/B
13–12
14. The task will be listed in the day.
14
'HWHUPLQLQJWKH7DSH/DEHO1HFHVVDU\IRUD%DFNXS

1. Double-click on the day.

13–13
2. If there is more than one entry,

select the backup entry.
3. Choose Volumes needed to see what
tape (label name) is required for 2
that backup.
Using the correct tape is

important. If the wrong tape is
used, the backup will fail. For
further information on tape
labeling, see chapter 3.
4. The required tape is displayed (for

example, CD27S).
'HOHWLQJDQ(QWU\IURPWKH3ODQQLQJ&DOHQGDU'%
1. On the DBA Planning Calendar,
double-click on the date.
Release 4.6A/B
13–14
Checking the Database Backup (DB12)
2. Select the item to delete.

3. Choose Delete. 2
a. Here you can also choose Change
to change the options you
originally selected for the job.
3a 3
4. Choose Yes.
5. The item has been deleted.

6. Choose .
5
&KHFNLQJWKH'DWDEDVH%DFNXS'%
:KDW
The Backup Logs transaction (DB12) provides backup and restore information, such as:
< Log file size and free space in the log file
< Date and time of last successful restore for:
R/3 database
Transaction log
Master database
Msdb database
< Backup history
< Restoration history
< Backup device list

13–15
< SQL Server jobs

< Tapes needed for restore
:K\
It is a convenient “one stop” point for backup information.

Some of the important backup information such as tape label name is passed to DB12 from
DB13. The “tapes needed for restore” option is important.
Do not rely on the “tapes needed for restore” feature. You must have a method that does
not rely on R/3 being available to tell you what tapes you will need to do a restore of the
R/3 system.
If there is a severe disaster, and the R/3 system is lost, R/3 is not available for you to look
at this report.
The only missing information is the run time (duration) of the backup job. This is a problem
indicator, when compared to the expected duration of the backup.
+RZ
*XLGHG7RXU

1. In the Command field, enter transaction DB12 and choose Enter

(or from the SAP standard menu, choose Tools → CCMS → DB Administration → DB12-Backup logs).
2. Review log space information to
analyze growth.
3. Review backup information and
notice the date and time of success
or failures.
4. The following is a list of the
available buttons and their
functions: 4a 4b
a. Backup history 4c
A spreadsheet summary of
2 4d
each backup is listed. Each
backup type can be reviewed 4e
with detailed log information
available using History info. 3
(see the SAP R/3 screen below).
b. Restoration history
A spreadsheet of detailed
restoration information is
listed.
Release 4.6A/B
13–16
c. Backup device list

Each logical device name is
listed with the appropriate
physical device name (see the
Backup Device List screen 4a
below).
d. SQL Server jobs
A spreadsheet listing of all
scheduled jobs with options
for CCMS, Database and History
Info is listed. History Info lists
the specifics of the job, that
pertain to success or failure of
the job.
e. Tapes needed For restore
A listing of the tapes that are
needed to restore the various 4c
databases. Scroll to the bottom
of the screen, for the
instructions to restore the
database (see the Tapes Needed
For Restore screen below).

13–17
Initializing Backup Tapes
4e
,QLWLDOL]LQJ%DFNXS7DSHV
:KDW
Initializing the tape writes a label on the tape header. This label is the same as the physical
label of the tape (for example, CD26S).
:K\
The tape label and the expiration date are additional safety levels to prevent backing up to
the wrong tape, and possibly, destroying needed data. When using the DBA Planning
Calendar (DB13) for backups, the tape must be properly labeled to execute a backup to tape,
because the transaction expects a specific tape to be in the drive. If the tape label does not
match the required label, the backup will fail.
+RZ
Initializing and labeling is an option when executing the backup using DB13, SQL Server
Enterprise Manager, or NT Backup. (For SQL Server, see SAP note 141118 for a description
of the tape label naming convention used by DB13).
Release 4.6A/B
13–18
Database Backups with Microsoft Tools
'DWDEDVH%DFNXSVZLWK0LFURVRIW7RROV
Backing up R/3 on SQL Server involves backing up the following SAP-specific and
database-related directories:
< \usr\sap
< \usr\sap\trans
< <homedirectory> of <sid>adm
< \<sid>data
The R/3 database files
< \<sid>log
The R/3 log file
If the log is allowed to grow to capacity and use all available filespace on the drive, SQL
Server will stop. This event is critical, because when R/3 stops, so does the business
processes that require R/3 to be running.
< \tempdb
Also backup the following Microsoft SQL Server databases:
< Master
In case of failures or hardware or software disasters, the Master database contains the
data necessary to recover the database.
< MSDB
The MSDB database contains the data for the SQL Server job scheduler and the database
backup history.
To make the backup process easier, and open to fewer errors, we recommend that you
backup the entire server and not just specific directories and files.
2QOLQH%DFNXS²8VLQJ64/VHUYHU(QWHUSULVH0DQDJHU
:KDW
The SQL 7.0 Enterprise manager is Microsoft SQL Server’s “general tool.” Here it is used to
backup the following while R/3 is running:
< The R/3 database
< The R/3 log
To clear the log, the log backup must periodically be done in the initialization mode.
If the log is allowed to grow to capacity and use all available filespace on the drive, SQL
Server will stop. This event is critical, because when R/3 stops, so does the business
processes that require R/3 to be running.

13–19
< \tempdb
You must also backup the following SQL Server databases:
< Master
If there is a hardware or software disaster, the master database contains the data
necessary to recover the database.
< MSDB
The MSDB database contains the data for the SQL Server job scheduler and the database
backup history.
:K\
An online backup allows you to backup the database(s) when R/3 and the database is
running, so that system users are not impacted.
+RZ
To backup any of the databases mentioned above:

1. On the NT desktop, choose Start → Programs → Microsoft SQL Server 7.0 → Enterprise Manager.
In the Enterprise Manager:
2. Expand the SQL Server Group under
which your server is located. (You
6
may have a different group name.)
3. Expand the server that you want to 2
look at. (You will have a different 3
server name.)
4. Choose Management 4
5. Choose Backup. 5
6. Choose Tools → Backup Database.
Release 4.6A/B
13–20
7. In Database, choose to select the

database to backup. 11
8. Under backup, select the type of 7

backup to perform (for example,
Database - complete).
Select Database – complete to do a full 8
backup of the database. Select
Transaction log to backup only the
transaction log.
9. Under Destination: 9
< Select the media (in this case
Tape)
< Select the device R3DUMP0.
10. Under Overwrite select Overwrite
existing media. 10
11. Choose the Options tab.
12. Under Options, select:

< Verify backup upon completion
< Eject tape after backup
< Backup set will expire
13. Under Backup set will expire, select 12
one of the following options and 12
complete the entry field:
< After (a defined number of days),
then enter the number of days.
12
< On (a specific date), then enter
13
the date.

13–21
On the screens below, you have three options:

< Backup without checking the tape label.
< Backup checking the tape label.
< Initialize the tape and writing a new tape label, before backing up.
To backup without checking the tape
label:
1. Leave the following options
deselected:
< Check media set name and backup set
expiration
< Initialize and label media
1
This step will overwrite and destroy

any data on the tape. Be certain that
the correct tape is in the drive. 1
2. Choose OK.
The backup will now begin.
2
Release 4.6A/B
13–22
To check the tape label before backing

up:
1. Select Check media set name and
backup set expiration.
2. Enter the tape label in Media set
name (for example, RD26S).
3. Choose OK, to begin the backup.
1
If the label of the tape does not
2
match the name entered in Media set
name, the backup will fail.
To initialize the tape before backing

up:
1. Select Initialize and label media.
2. Enter the tape label name in Media
set name (for example, RD26S).
This step will relabel, overwrite, and

destroy any data on the tape. Be
certain that the correct tape is in the
drive.
1
3. Choose OK to begin the backup. 2

13–23
2IIOLQH%DFNXS²8VLQJ17%DFNXS
:KDW
The offline backup is done when R/3 and the database are down. Here, we also use the
offline backup to also backup other files which are needed to restore R/3. Since high
capacity tape drives are now more common, it is simpler and safer to backup the entire
server. This full server backup eliminates the possibility of not backing up an important file.
For smaller customers, the entire server could be backed up to a single DLT cartridge.
At a minimum, backing up R/3 on SQL Server involves backing up the following SAP-
specific and database-related directories:
< \usr\sap
< \usr\sap\trans
< <homedirectory> of <sid>adm
< \<sid>data (the R/3 database files)
< \<sid>log (the R/3 log file)
< \tempdb
In addition to these directories, you must back up any directories and files for third-party
products, interfaces, etc. that store their data outside the R/3 database. Getting all the
required files and directories can be difficult, which is why we recommend that you backup
the entire server.
:K\
The data in the database does not change while the backup is being made, which means that
you have a static “picture” of the database and do not have to deal with the issue of data
changing while the backup is being run. With some third party applications, you cannot
back up the files unless they are closed, and this is not possible unless R/3 and the
application are shut down. Therefore, an offline backup needs to be done. A “full server”
offline backup also gives you the most complete backup in the event of a catastrophic
disaster. On one tape, you have everything on the server.
+RZ
Due to system limitations on the documentation system, the location of the files in this
example are presented differently from the recommendations in the SAP installation
manual.
Release 4.6A/B
13–24
*XLGHG7RXU

To do an offline backup, we use NT Backup interactively:

1. Shut down R/3.
2. Shut down the database.
3. Shut down any other applications.
4. Insert the appropriate tape into drive.
5. On the NT desktop, choose Start → Programs → Administrative Tools → Backup.
6. Select all drives on the server.
7. Choose Backup. 7
Enter appropriate information in the

Backup Information dialog box.
8. In Tape Name, enter the tape label
name (for example, CD26S).
9. Select Verify After Backup. 8
10. If your tape drive supports 9
hardware compression, select 11
Hardware Compression. 10
11. Under Operation, select Replace.
12. In Description, enter a description.
13. Choose OK. 12
13

13–25
14. This window will appear to verify

that the correct tape is in the drive.
15
Even if the tape name you entered
in the previous screen matches the 14
tape label, this window will
appear.
15. Choose Yes.
16. The backup will run. The window

displays the backup progress.
16
17. When the backup has successfully

completed, choose OK.
17
Release 4.6A/B
13–26
18. From the menu bar, choose

Operations → Exit. 18
19. Remove the tape from the tape

drive and store properly.

13–27
Database Error Logs
'DWDEDVH(UURU/RJV
5²67
You can view the database error logs from within R/3 using transaction ST04. For more
information on database error logs, see the Database Performance Analysis (ST04) section
earlier in this chapter.
0LFURVRIW64/6HUYHU(QWHUSULVH0DQDJHU
*XLGHG7RXU

1. From the NT desktop, choose Start → Programs → Microsoft SQL Server 7.0 → Enterprise Manager.
In the Enterprise Manager:
2. Expand the SQL Server Group
under which your server is
located.
3. Expand the server where the R/3
system is installed. 2
3
4. Expand Management.
4
5. Expand the SQL Server Logs.
6. Select the Current log.

Here, you can also look at the six
previous error logs.
7. Read the log in the right-hand side
window.
7
Release 4.6A/B
13–28
Verify Database Consistency
9HULI\'DWDEDVH&RQVLVWHQF\
:KDW
In a database management system, consistency can be represented from the logical and
physical levels. R/3 must insure a logical consistency when communicating with the SQL
Server engine, and SQL Server must insure a physical consistency for the database.
:K\
Sometimes a physical inconsistency can occur in the database’s internal structures. This
problem occurs when R/3 “thinks” the data is, and where the data actually is, in the
database are different.
+RZ
SQL Server uses the DBCC CHECKDB command to correct and repair the database to a
consistent state. This is executed using:
< CCMS Scheduling calendar (DB13)
< The SQL Server Enterprise Manager
The consistency checks should be done during non-peak hours or when R/3 users are
offline. For those coming from SQL Server 6.5 environments, SQL Server 7.0 executes the
DBCC CHECKDB job much faster than SQL Server 6.5.
5XQ8SGDWH6WDWLVWLFV
:KDW
Database objects statistics help make data access more efficient.
:K\
The optimizer of the database engine will perform better if the table index’s statistical
information is current. This information helps R/3 find an item in the database faster.
+RZ
By default, SQL Server 7.0 has automatic statistics turned on. The possibility of manually
scheduling update statistics using the CCMS scheduling calendar still exists. Examples of
when this scheduling might be necessary after large data inserts or deletes from a given
table (for example, client copy, BDC sessions, and archiving).

13–29
System passwords
6\VWHPSDVVZRUGV
64/VHUYHU
For additional information, see SAP note 28893.
User IDs to change:
< sa
< sapr3
During the installation, by default:

< SQL server does not ask for, nor does it set, a password for user sa.
Once the installation is complete, the system administrator must manually create a
password.
< For user sapr3, a password is created, but it is created with a default password.
Therefore, you must change the password. Beginning with release 4.5, user sapr3 is no
longer used by R/3.
These “loopholes” must be closed manually.
+RZ
*XLGHG7RXU

1. From the NT desktop, choose Start → Programs → Microsoft SQL Server 7.0 → Enterprise Manager.
In the SQL server Enterprise Manager:
2. Expand the SQL Server Group.
3. Expand the server.
4. Expand Security.
5. Choose Logins.
2
3
4
5
Release 4.6A/B
13–30
System passwords
6. On the right side of the screen,

double-click “sa” (or “sapr3,” if
sapr3 was created).
7. Choose General tab.

8. Enter new password in Password. 7
9. Choose Apply.
10. Reenter the password in Confirm

New Password.
11. Choose OK.
10
11

13–31
System passwords
12. Choose OK.
12
For user sapr3, up through release 4.0,

the following also needs to be done:
13. In the SQL Server Enterprise
Manager Console, choose Tools →
13
SQL Query Analyzer.
Release 4.6A/B
13–32
System passwords
14. Enter the following SQL 15

commands:
use <SAPSID>
go
14
sap_change_password
‘<OLD_PASSWD>’,
‘<NEW_PASSWD>’
15. Choose Execute Query (or choose
Query → Execute Query).

13–33
System passwords
Release 4.6A/B
13–34

Network Admin

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Network Admin

Diunggah oleh

Hak Cipta:

Format Tersedia

&KDSWHU 'DWDEDVH$GPLQLVWUDWLRQ²

System Administration Made Easy 13–1

3. Check that Microsoft SQL Server

Follow the proper procedure to stop R/3.

5. Check that Microsoft SQL Server

For more information on stopping the database, see chapter 9.

System Administration Made Easy

The Database Performance Monitor (ST04) provides a database-independent tool to analyze

1. In the Command field, enter transaction ST04 and choose Enter

System Administration Made Easy

3. This screen is the Detailed analysis menu

< Analyze exceptional conditions 3b 3b

This screen shows the Database Error Log.

The Database Allocation transaction is used to analyze:

1. In the Command field, enter transaction DB02 and choose Enter

b. DB space history takes you to

System Administration Made Easy

This screen is the DB space history

Here you can analyze the physical

This screen is the DB analysis

System Administration Made Easy

1. Enter transaction DB13 and choose Enter.

If a task exists for that day, this

4. In StartTime, enter the time to begin

The start time is the time on the

7. Select all the databases.

System Administration Made Easy

11. In the Log backup tape options pop-

14. The task will be listed in the day.

'HWHUPLQLQJWKH7DSH /DEHO 1HFHVVDU\IRUD%DFNXS

System Administration Made Easy

2. If there is more than one entry,

Using the correct tape is

4. The required tape is displayed (for

2. Select the item to delete.

5. The item has been deleted.

System Administration Made Easy

< SQL Server jobs

It is a convenient “one stop” point for backup information.

1. In the Command field, enter transaction DB12 and choose Enter

c. Backup device list

System Administration Made Easy

System Administration Made Easy

To backup any of the databases mentioned above:

6. Choose Tools → Backup Database.

7. In Database, choose to select the

8. Under backup, select the type of 7

11. Choose the Options tab.

12. Under Options, select:

System Administration Made Easy

On the screens below, you have three options:

This step will overwrite and destroy

To check the tape label before backing

To initialize the tape before backing

This step will relabel, overwrite, and

System Administration Made Easy

To do an offline backup, we use NT Backup interactively:

Enter appropriate information in the

System Administration Made Easy

14. This window will appear to verify

16. The backup will run. The window

17. When the backup has successfully

18. From the menu bar, choose

19. Remove the tape from the tape

&KDSWHU 'DWDEDVH$GPLQLVWUDWLRQ²

'HWHUPLQLQJWKH7DSH/DEHO1HFHVVDU\IRUD%DFNXS