Skip to Content
avatar image
Former Member

DSN connection across different environments

Hie Guys,

A database has 3 different servers for DEV, TEST & PROD. Now, while creating a DSN for the Universe, do you have to create a DSN for each environment (Dev, Test & Prod) ? How does this work? Could anyone please help me understand the concept? Thanks.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Jun 24, 2014 at 07:45 AM

    Hi

    If you have three SQl servers (Dev,Test,Prod ) and three bo servers (Dev,Test,Prod )   you need to create three different DSN connections in Dev SQL.

    IN THE DEV SERVER

    1. Create DSN connection (Dev DSN Connection) in  the Dev SQL to connect Dev SQL to BO Dev and then develop the universe.

    2. Create another DSN connection (Test DSN Connection)  in the Dev SQL to connect Test SQL to Test BO Dev

    3. Create another DSN connection (Prod DSN Connection)  in the Dev SQL to connect Prod SQL to Prod BO Dev

    Then while promoting to Test environment, you need to send universe along with connection, but in the connection you need to change the Dev SQL connection to Test SQL connection ((Test DSN Connection)  (Select the connection -> Click on change connection)

    Then while promoting to Prod environment, you need to send universe along with connection, but in the connection you need to change  to Prod SQL connection (Prod DSN Connection) 

    And once the universe and connection are promoted successfully come back to Dev and change the connection to Dev SQL (Dev DSN Connection)

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 25, 2014 at 08:42 AM

    Hi Jeevan  ,

    scenario 1

    1. Do you have 3 diff bo servers and 3 db servers as Dev QA Prod .

    It s an ideal scenario. Here you can create DSN on each server with same name pointing to respective DB.

    For e.g.  On BO prod  server create DSN name ABC pointing to prod DB ,  like wise on Dev server create DSN name ABC  pointing to Test DB . do the same for dev also. So you need not to change connection even during promotion.

    Scenario 2

    You have 3 diff db and single bo where you want your development. This is not ideal Scenario but some people do this.

    In this case you can have 3 diff DSN in BO server . and create 3 diff connection based on each DSN .

    Now you can do connection overriding . That means  you can specify in universe which users should use which connection while creating or refreshing reports.

    Regards

    Jeevan

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 23, 2015 at 06:58 AM

    Hi Guru's

    I am have the similar scenario, dev and qa are on same server.

    but naming convention is maintained as devviewdb.viewname.tablename and qaviewdb.viewname.tablename, view names remain the same across dev and qa.

    I could change the connections maually but how to handle db names, we are using teradata as source and dsn same across deva and qa, Please help

    Regards

    Sharma

    Add comment
    10|10000 characters needed characters exceeded