Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

keeping dev and live databases in sync Expand / Collapse
Author
Message
Posted Tuesday, July 31, 2012 4:00 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, December 3, 2014 4:50 AM
Points: 288, Visits: 580
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
Post #1337761
Posted Tuesday, July 31, 2012 4:32 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, December 15, 2014 7:13 AM
Points: 243, Visits: 755
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
Post #1337771
Posted Tuesday, July 31, 2012 5:00 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 12:03 AM
Points: 1,380, Visits: 2,708
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

Post #1337785
Posted Tuesday, July 31, 2012 5:02 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, December 3, 2014 4:50 AM
Points: 288, Visits: 580
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
Post #1337786
Posted Tuesday, July 31, 2012 5:03 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, December 3, 2014 4:50 AM
Points: 288, Visits: 580
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 :)
Post #1337789
Posted Tuesday, July 31, 2012 5:41 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, December 15, 2014 7:13 AM
Points: 243, Visits: 755
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
Post #1337809
Posted Tuesday, July 31, 2012 6:15 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 5:40 AM
Points: 14,205, Visits: 28,532
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
Post #1337835
Posted Tuesday, July 31, 2012 6:23 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, December 3, 2014 4:50 AM
Points: 288, Visits: 580
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.


:) 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
Post #1337844
Posted Tuesday, July 31, 2012 6:33 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 5:40 AM
Points: 14,205, Visits: 28,532
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.


:) 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
Post #1337850
Posted Tuesday, July 31, 2012 6:51 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, December 3, 2014 4:50 AM
Points: 288, Visits: 580
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
Post #1337862
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse