on 11-02-2017 9:22 PM
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.
Does anyone have input on use of Datasources of test vs production in Crystal Reports using SQL Server ? see question above...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are using SQL Server "command"
see screenshot.... screenshot.png
The SQL is stored in command.screenshot.png
User | Count |
---|---|
78 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.