Framework Manager - a few production questions

[ry1633]

Hi all,

I've reached the point where I'm ready to bring a package to production.  I've got a few questions for you gurus who've already been down this road.

1.  Data Sources - thus far, in dev and testing,  I've been using one datasource.   But I'll have to point my package to the production data source.   What's the best and quickest way to do that?    Can I import the production source into my project and just point the package definition to that datasource instead?   I'd rather not have to make this part any messier than I have to.  :)

2. Versioning. --- So far, during development and testing I've turned off the versioning because we've had many dozens (if not hundreds) of iterations and I was told early on to disable versioning during those development phases.   But once we go production I assume I'll want to enable versioning?  What are some tips or good practices for this?

[MFGF]

Hi all,

I've reached the point where I'm ready to bring a package to production.  I've got a few questions for you gurus who've already been down this road.

1.  Data Sources - thus far, in dev and testing,  I've been using one datasource.   But I'll have to point my package to the production data source.   What's the best and quickest way to do that?    Can I import the production source into my project and just point the package definition to that datasource instead?   I'd rather not have to make this part any messier than I have to.  :)

2. Versioning. --- So far, during development and testing I've turned off the versioning because we've had many dozens (if not hundreds) of iterations and I was told early on to disable versioning during those development phases.   But once we go production I assume I'll want to enable versioning?  What are some tips or good practices for this?

Hi,

it makes sense to have the Production instance use the same data source name as the Dev/Test instances. Assuming you haven't defined a specific catalog/schema in your FM model, there should be no issues in using the same package without alterations.

You'd only need versioning if you plan to make untested changes to the production server. If you do all your development and testing on the Dev and Test instances, you should be able to deploy the package and reports in one go to Production, and not need versioning at all?

MF.

[Penny]

In our DEV environment we have a datasource that contains multiple datasource connections  - we call it Banner.  Each database that has a connection has the same structure as our production datasource.

We use the same datasource name in our PROD environment, but it contains a single datasource connection only ... to production data.

When the user runs a report in DEV they get prompted for a database connection, but when the report runs in PROD they do not get prompted as there is only a single datasource connection available (production datasource)..

That way when we deploy we don't have to make any changes to datasources.