Post reply

Gathering application details

  • September 22, 2009 at 11:08 pm

    #98114

    Hi we are a DBA and we are inheriting databases from our client.

    In the course of time we are looking to gather application details from the company who held the contract with the client.

    What details you think we should be gathering or put on a spreadsheet so that it makes easier for us later in the future..

    We have these points:

    Application Name

    Environment

    Login process

    Host name

    DomainName

    User /pwd

    IP

    OS Environment

    No. Of CPU's

    SQl server instance name

    SQL server version

    SQL user/pwd

    Port

    Number of Databases associated with the application

    Database/s Name/s associated with the applications

    Client connectivity procedure

    Backup Strategy

    Production DBA contact info

    thanks,

  • September 23, 2009 at 3:24 am

    #1057359

    Hi all,

    Any views/opinions on this please

    Thanks,

  • September 24, 2009 at 10:42 am

    #1058150

    Crunchy,

    You might be interested in:

    1) Sensitivity of the data (needs for any special handling, security, encryption, etc.)

    2) Backup requirements and schedule

    3) Restore agreements (such as service level agreements, implications of downtime, need to apply transaction logs)

    4) Purpose of the application

    5) Owner of the data (business function owner)

    6) Any special requirements (such as cross database chain linking, maintaining local views against a vendor database that may change, periodic truncation and reloading of all data)

    7) Level of development activity, to get an idea of how often changes or implementations occur.

    8) Any known plans to deactivate the application or replace it? Move it to another dbms? Upgrade it to a new version of the dbms?

    9) Is the application active? Are the databases read-only?

    9) What is the setup for environments - development, unit test, acceptance test, production, training, reporting? And what method is used to put data into the various environments.

    10) Who is the security officer for the application, who has authority to give or remove security rights, what is the procedure for this.

    11) Are the application and databases in line with the usual standards and policies of your organization? If not, who gave permission for the variance?

    12) Who maintains the application and databases? Who is the lead programmer? Who is the lead DBA?

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply