SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Development and Production Database


Development and Production Database

Author
Message
david.carnley
david.carnley
SSC Rookie
SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)

Group: General Forum Members
Points: 27 Visits: 27
I think in the long run you might be best off by creating simulators - small apps or scripts that produce transactions similar to production. Over time you could evolve these into a full test suite that could simulate all of the possible types of transactions.
ps.
ps.
SSCertifiable
SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)

Group: General Forum Members
Points: 7099 Visits: 3668
writing triggers on all tables would be little cumbersome and as said earlier would hit production.

You can also think of implementing log shipping. keep log backup interval relatively higher and use this interval to study the data in ur developement database by bringing database in multi_user mode.. Hope u're not planning to enter data into developement simultaneously..



Pradeep Singh
Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (213K reputation)SSC Guru (213K reputation)SSC Guru (213K reputation)SSC Guru (213K reputation)SSC Guru (213K reputation)SSC Guru (213K reputation)SSC Guru (213K reputation)SSC Guru (213K reputation)

Group: General Forum Members
Points: 213597 Visits: 41977
Periodic "Log Shipping" or on demand "Replication" would do it.

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
robertm
robertm
Old Hand
Old Hand (396 reputation)Old Hand (396 reputation)Old Hand (396 reputation)Old Hand (396 reputation)Old Hand (396 reputation)Old Hand (396 reputation)Old Hand (396 reputation)Old Hand (396 reputation)

Group: General Forum Members
Points: 396 Visits: 118
Jeff you beat me to it. I would most certainly look at using Transactional Replication to solve this issue, assuming that's going to be suitable for your environment.

However the idea of capturing trace information is something I hadn't considered before and offers up some nice functionality such as repeatable tests which could be easily added into a dbfit FitNesse test for example.



Gursoy Yerli
Gursoy Yerli
Grasshopper
Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)

Group: General Forum Members
Points: 11 Visits: 48
What we're doing is simple as long as you script your database changes from DEV to PROD. Here how it goes.

1) We backup PROD database every day (week or month. Depends on your dev cycle)
2) We restore PROD database into another database and run clean-up scripts (due to compliance on sensitive data)
3) We backup cleansed database and port backup file(s) to DEV environment
4) We restore cleansed PROD backup on DEV environment and run incremental script to bring PROD "data" to DEV schema.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search