Comments posted to this topic are about the item How many environments?
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Mostly 4 Enviroments:
Sometimes 3 where test/acceptation are merged.
2. Test / UAT
3. Train - for end users to be trained on new systems before go live or for new users of existing systems.
As we are using 2005,2008, 2008R2, 2012 and 2014 we have Dev, Test, and Prod in all versions plus Train where required
Hall of Fame
Below are the environments we use for the last 2 GA releases plus the version under development of our software product. The Test, Performance, and QA environments for the current version under development are upgraded nightly from source control.
- Development (version under development and last 2 GA release bug fixes)
- Isolated Test (ad-hoc testing of changes that must be done in isolation)
- Test (automated unit testing of version under development and last 2 GA release bug fixes)
- Performance (automated performance testing of version under development only)
- QA (version under development plus last 2 GA release bug fixes)
- Demo (product demos of latest GA release and version under development)
- UAT (client on-prem for GA release or preview of version under development)
- Production (hundreds of clients, on-prem and hosted for last 2 GA releases)
We have two: Development and Production. The development and UAT occurs on dev.
Some people use their local system for development and then deploy to dev for UAT, but most people just use the dev and prod servers.
Dev, Test and Production. Plus I have a "demo" instance I use for presentations and training.
Just my $0.02 from over here in the cheap seats of the peanut gallery - please adjust for inflation and/or your local currency.
We have an unusual set of environments 12 in all. Each developer has a DEV server vm for development. Check-ins are to a Continuous Integration (CI) server using Team Foundation Studio; this server compiles all projects and validates metadata. Then we have QA, UA, MOCK and PROD ; the Mock server is used as a final staging server and reflects exactly what is on Prod. Additionally we have a TRAINING server for trainers and students, a SANDBOX for troubleshooting, a MAINTENANCE environment for such things as optimizations, and a LOADTEST for performance testing. We also have a REPORTING server which is a replica of PROD and a WEBSERVICE to isolate external data consumers from our PROD environment.
1. Local PC development environment (one per developer)
2. Shared development environment on server (that each developer merges into)
3. Staging environment
4. Testing environment
5. Production environment
6. Sales support environment (unique, sales and marketing version of the software and DB with things that are automated for presentation and demo purposes rather than "normal use")
In theory my company has five environments:
Dev - where we all work, anything goes, drop and recreate at the drop of a hat.
QA - once dev is 'done', it gets deployed here for testing
UAT - once projects pass QA, they are deployed here for final sign-off by the stakeholders
Demo/Staging - When a release is ready, it is deployed here as a test run. Also used for customer demos and support staff training
Prod - the live show
The practice is far less stable....
we travel not to escape life but for life not to escape us
Don't fear failure, fear regret.
3. Our Testing
4. Customer Testing
We also do have demo systems, but they aren't tied directly to my local site's development/release process.
Our typical development stream contains four environments: Staging, System, Parallel, and Production.
However, we're replacing our primary line of business application and (so far) we're up to 17 environments. Outta control!!
Viewing 15 posts - 1 through 15 (of 35 total)