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


keeping dev and live databases in sync


keeping dev and live databases in sync

Author
Message
erics44
erics44
Mr or Mrs. 500
Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)

Group: General Forum Members
Points: 530 Visits: 739
Does anyone know of any ways to keep a dev database up-to-date with changes on a live database without doubling up on the work?

Thanks in advance
SQLEnthusiast
SQLEnthusiast
SSC Veteran
SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)

Group: General Forum Members
Points: 263 Visits: 909
Can you just restore the latest live backup into your dev database when it requires refreshing ?

However that would also copy data as well as stored procs, database permissions etc from live, which might not be what you want.

_______________________________________________________________

Website : www.sqlmatters.com
SQLSACT
SQLSACT
SSCrazy
SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)

Group: General Forum Members
Points: 2140 Visits: 2931
erics44 (7/31/2012)
Does anyone know of any ways to keep a dev database up-to-date with changes on a live database without doubling up on the work?

Thanks in advance


Log Shipping or a manual approach to Log Shipping could work
erics44
erics44
Mr or Mrs. 500
Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)

Group: General Forum Members
Points: 530 Visits: 739
thanks for the reply

yeah im doing that sort of thing at the minute

there is currently a lot of movement on the live (we are nearing a deadline) and its very beneficial to keep the dev updated so theres a lot of work also on the dev

i was hoping that there was some tool or method that replicates the changes on one server to the other without doing these "manual" tasks

thanks again
erics44
erics44
Mr or Mrs. 500
Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)

Group: General Forum Members
Points: 530 Visits: 739
SQLSACT (7/31/2012)
erics44 (7/31/2012)
Does anyone know of any ways to keep a dev database up-to-date with changes on a live database without doubling up on the work?

Thanks in advance


Log Shipping or a manual approach to Log Shipping could work



thanks ill look into it

my other reply was to SQLEnthusiast Smile
SQLEnthusiast
SQLEnthusiast
SSC Veteran
SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)

Group: General Forum Members
Points: 263 Visits: 909
Yes, if you wanted changes to appear on the dev database in real time or near real time then there are several high availability features that could be used such as replication, mirroring or log shipping but these do look like overkill in my opinion. Log shipping also requires the target database to be read-only, which is usually unsuitable for a dev database.

_______________________________________________________________

Website : www.sqlmatters.com
Grant Fritchey
Grant Fritchey
SSC-Forever
SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)

Group: General Forum Members
Points: 41807 Visits: 32666
Just a question, changes are getting made to the production server directly and then you need those brought down to dev and we're not talking data?

I'd say the process is backwards. You should always be deploying upwards. If you put your database into source control and manage it the same way you do app code, you should be able to rebuild a dev environment at any given moment (minus the data). At least, that's how I helped manage about 15 different development teams.

----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore Roosevelt

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
erics44
erics44
Mr or Mrs. 500
Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)

Group: General Forum Members
Points: 530 Visits: 739
Grant Fritchey (7/31/2012)
Just a question, changes are getting made to the production server directly and then you need those brought down to dev and we're not talking data?

I'd say the process is backwards. You should always be deploying upwards. If you put your database into source control and manage it the same way you do app code, you should be able to rebuild a dev environment at any given moment (minus the data). At least, that's how I helped manage about 15 different development teams.


Smile 99.99999 % of the time yes, at the minute we are just going live with a big project that is massively overdue and its like final tweaks, although the final tweaks have been dragging a bit, (in fact even in this instamce it should really be that way, its just come to boiling point where its got to be done yesterday and all resource is on it)

the process will change to a dev, staging, live situations as soon as the system is live
Grant Fritchey
Grant Fritchey
SSC-Forever
SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)

Group: General Forum Members
Points: 41807 Visits: 32666
erics44 (7/31/2012)
Grant Fritchey (7/31/2012)
Just a question, changes are getting made to the production server directly and then you need those brought down to dev and we're not talking data?

I'd say the process is backwards. You should always be deploying upwards. If you put your database into source control and manage it the same way you do app code, you should be able to rebuild a dev environment at any given moment (minus the data). At least, that's how I helped manage about 15 different development teams.


Smile 99.99999 % of the time yes, at the minute we are just going live with a big project that is massively overdue and its like final tweaks, although the final tweaks have been dragging a bit, (in fact even in this instamce it should really be that way, its just come to boiling point where its got to be done yesterday and all resource is on it)

the process will change to a dev, staging, live situations as soon as the system is live


Oh, a death march. Those always turn out well...

I've been in this situation before. I've won the fight and I've lost the fight. The fight is, despite the fact we're in a death march, still do things properly. The places where I won the fight, we knew what we were deploying. The places where I've lost the fight, we spent almost as much time troubleshooting why new stuff kept breaking as we did fixing the stuff that was already broken.

If you're stuck in that situation, I'm sorry. If you don't have a comparison tool to be able to see what has changed between two different databases, I'd suggest getting one. The better examples of this type of tool can be easily automated so that you capture all the changes on the fly. My personal favorite, SQL Compare from Red Gate (my employer), but there are others out there (almost as good) that will get the job done. That's what I'd suggest to try to keep this in some type of control.

----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore Roosevelt

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
erics44
erics44
Mr or Mrs. 500
Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)Mr or Mrs. 500 (530 reputation)

Group: General Forum Members
Points: 530 Visits: 739
Thanks

The comparrison tools are the kind of thing i was looking for

i was considering scripting the procs and stuff from the sys tables and comparing that way, building a kind of comparrison tool of my own :-)
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