You are on page 1of 3

EXECUTING THE MS-SQL 2005 SCRIPT

Important: The final responsibility for executing this script lies with the client.

The information provided here is a guide to explain the process of what the DBA
is doing. At no time should you ever run the script yourself on the live
environment without express permission of the engagement partner and the
client.

 Connect to the server by using Microsoft Remote Desktop, or similar


application.

 Open a command shell (START -> RUN -> cmd.exe) and create an empty
directory (mkdir c:\audit).

 Transfer the audit scripts (run_PwC-MSQL-2005.bat and


sqlserver2005_script.1.0.pwc) to this directory on the server by using
the Windows network, FTP or similar protocol.

 Open a command shell (START -> RUN -> cmd.exe), change to the
created folder (cd c:\audit), and execute the script (run_PwC-MSQL-
2005.bat).

 The script will prompt you for a server name, username, and password.

If database-level authentication is used:

 Enter the machine name (localhost would suffice), privileged database


user account (such as “sa”), and its corresponding password.
If operating system-level authentication is used:

 (Log in to the operating system using an account which is also a


privileged database user account) Enter the machine name (localhost
would suffice), and leave the user name and password fields blank.

 It should not take more than 5 minutes to run. Output will be displayed as
the script progresses.

 If it seems to be taking an unusually long time, it might be for the following


reasons:

– Database is unusually busy (this should not be run during normal


business hours).

– Hardware is inadequate (in particular where this is being run on a


test / development box).

 Once the script has finished, inspect the output files by typing “dir output”.

 The output files may be quite large, so request the DBA to ZIP them for
you.

You might also like