Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
echo88
Starting Member
4 Posts |
 Posted - 2009-08-02 : 10:40:28
|
| Is it possible or good idea to create a separate database schema for a test environmnent? |
|
|
TG
Master Smack Fu Yak Hacker
6065 Posts |
Posted - 2009-08-02 : 10:54:18
|
| well, it's better than testing directly with production code but I would say no. You really should have a separate environment. during dev and/or testing you would need change production data. a poorly written or poorly designed SP could cause excessive blocking, dead locking, or other concurrency problems. part of your testing may include load testing which wouldn't be good in a production environment. Then when you want to "deploy" to prod you would need to change the schema (change code) which is not good practice because you would not technically be deploying the same code you tested. Now if you have a different test and/or dev environment already then why would you want to use a different schema?Be One with the OptimizerTG |
 |
|
|
echo88
Starting Member
4 Posts |
Posted - 2009-08-02 : 12:06:45
|
| We don't have a test environment already - we were looking at options for a school project :) |
|
|
|
|
|
|
using a different database schema for prod & test