Topic
  • 6 replies
  • Latest Post - ‏2013-09-25T10:29:54Z by pdubovitsky
Bzoo
Bzoo
71 Posts

Pinned topic Removing a test database from a connection

‏2013-09-09T14:04:27Z |

All:

Need to remove a corrupt Test database  from an existing  connection

and add a new Test database to that connection. I have 3 questions:

 

1) Will this process (removing /adding a test database  to an existing connection)

affect the Production CQ  database any way.

 

2) Do I need clearquest_db_owner password for this process / operation

 

2) Any documentation on this process of removing /adding a new test

database to an existing connection

 

Thanks for your help

 

Regards,

Bzoo

  • pdubovitsky
    pdubovitsky
    376 Posts

    Re: Removing a test database from a connection

    ‏2013-09-09T14:50:28Z  

    1) You can have as many of the production and test databases as you need. Creating another database would not impact existing ones.
    http://pic.dhe.ibm.com/infocenter/cqhelp/v8m0r1/index.jsp?topic=%2Fcom.ibm.rational.clearquest.admin.doc%2Ftopics%2Ft_cr_new_user_db.htm

    2) In order to create new database, you need to provide backend database vendor and vendor-specific parameters. Unless you are using MS_ACCESS, these parameters include backend database user name and password.

    3) ClearQuest administration manual would be helpful.

    Pavel

     

  • Bzoo
    Bzoo
    71 Posts

    Re: Removing a test database from a connection

    ‏2013-09-09T14:57:44Z  

    Hi Pavel:

    Thanks for your quick response.

    Regards,

    Bzoo

  • d.potam
    d.potam
    38 Posts

    Re: Removing a test database from a connection

    ‏2013-09-24T10:12:57Z  

    Just example: in my case we have three databases. First DB it is a production databases. Second DB it is a database with copy of production data. It uses by testing group. Third DB it is a development database.

    First developer testing his developing on own database, then he upgrade DB of testing group to last schema version, and then, if all ok, the production database got upgrade.

    Updated on 2013-09-24T11:07:55Z at 2013-09-24T11:07:55Z by d.potam
  • Bzoo
    Bzoo
    71 Posts

    Re: Removing a test database from a connection

    ‏2013-09-25T00:50:20Z  
    • d.potam
    • ‏2013-09-24T10:12:57Z

    Just example: in my case we have three databases. First DB it is a production databases. Second DB it is a database with copy of production data. It uses by testing group. Third DB it is a development database.

    First developer testing his developing on own database, then he upgrade DB of testing group to last schema version, and then, if all ok, the production database got upgrade.

    Hi Potam:

     

     I like your idea of having 3 DBs.  Could you please elaborate. I would like to know

    when you populate this second database with the copy of Production data.

    • Is it done  periodically(daily,weekly,monthly)
    • when you want to push a new schema.

    How to create this second DB:

    Assume the production database is at schema version 10.

    Start with an empty database, put a schema (v:10) on top of this and copy the contents of

    production  database. Is this the right way to create?

    Please let me know.

    I need this information very badly.

    Thanks

    Bzoo.

  • d.potam
    d.potam
    38 Posts

    Re: Removing a test database from a connection

    ‏2013-09-25T06:52:37Z  
    • Bzoo
    • ‏2013-09-25T00:50:20Z

    Hi Potam:

     

     I like your idea of having 3 DBs.  Could you please elaborate. I would like to know

    when you populate this second database with the copy of Production data.

    • Is it done  periodically(daily,weekly,monthly)
    • when you want to push a new schema.

    How to create this second DB:

    Assume the production database is at schema version 10.

    Start with an empty database, put a schema (v:10) on top of this and copy the contents of

    production  database. Is this the right way to create?

    Please let me know.

    I need this information very badly.

    Thanks

    Bzoo.

    I imagine that copy of production data on test database must be applied each time when testers want to test new functions on actual data.

    Our DBA create backup of production database every night, but I copy this backup on tester's database only when Project Manager want this (2-3 times in year).

    Process of copying from one database to another database is describe at http://blogs.onresolve.com/2007/10/changing-the-logical-name-of-a-clearquest-user-database/

    It is important becouse you can't just copy from one DB to second DB and link second DB with ClearQuest.

  • pdubovitsky
    pdubovitsky
    376 Posts

    Re: Removing a test database from a connection

    ‏2013-09-25T10:29:54Z  
    • d.potam
    • ‏2013-09-25T06:52:37Z

    I imagine that copy of production data on test database must be applied each time when testers want to test new functions on actual data.

    Our DBA create backup of production database every night, but I copy this backup on tester's database only when Project Manager want this (2-3 times in year).

    Process of copying from one database to another database is describe at http://blogs.onresolve.com/2007/10/changing-the-logical-name-of-a-clearquest-user-database/

    It is important becouse you can't just copy from one DB to second DB and link second DB with ClearQuest.

    User Database renaming is not supported, and could cause some issues.
    It does not mean that it does not work, but preferred way would be to create a copy of the master and user databases, and update properties of the databases to point them to the new location. First of all, it is supported by the vendor. Second, your would be testing on exact copy of production data (not a change even in the DB name).
    When testing is completed, the changes can be promoted to the "Production" dbset using cqload exportintegration/importintegration utilities.

    Pavel