cancel
Showing results for 
Search instead for 
Did you mean: 

Crystal Reports 14 - Set DataSource Location

mark_tractor
Explorer
0 Kudos

Currently, we have a DataSource for Production and a DataSource for Test.

To change between the two, we do a 'set datasource location'. When we set to Production, I believe we are impacting Production database performance. Doing this does a validate of data between the different DataSources ?

Is there a better way to segregrate production vs test data connections ?

When we are building a report or making major modifications we want to be connected to test.

mark_tractor
Explorer
0 Kudos

We are using SQL Server "command"

The SQL is stored in command.screenshot.png

Accepted Solutions (0)

Answers (2)

Answers (2)

mark_tractor
Explorer
0 Kudos

Does anyone have input on use of Datasources of test vs production in Crystal Reports using SQL Server ? see question above...

abhilash_kumar
Active Contributor

Hi Mark,

1. Setup an ODBC connection on the 'developer' machine so that it points to the 'Dev' database.

2. On the Production system, setup a similar ODBC (with the same name) so that it points to the 'Prod' database.

The report should now work seamlessly on both environments via ODBC without having to do a 'set datasource location'.

-Abhilash

mark_tractor
Explorer
0 Kudos

Thank you Abhilash,

your answer helps. Currently, we have one server where we do development and it also serves as the production server where the reports run. Thanks for your input, this solves my question.

Former Member
0 Kudos

What database are you using?

If Oracle and tables names are same you can make report Schema independent by going to Set Datasource click and open up each table.

Click on the line which says something about Alias do not have crystal open so can't recall exact title. Enter the table name into that field, repeat for each table. When you port to Production you will not need to verify each table.

mark_tractor
Explorer
0 Kudos

We are using SQL Server "command"

see screenshot.... screenshot.png

The SQL is stored in command.screenshot.png