How can we help you today? How can we help you today?
ben_b
Hi @gmartin Welcome to the forums.  We had this scenario too. As well as the options listed above, here are some other possible options. 1.  Create SSIS packages that will copy the data over from prod to dev.  This will be a data only refresh. (You can use BIML to make it dynamic)   2.  Backup/Restore from prod every night but also schedule a job to publish/deploy your dev work from source control to the freshly restored copy on your dev server 3.  Create a separate dev database and do your development work using cross database references until they are ready for production.  (not great but can work) 4.  Truncate/Insert Into using linked server 5.  Truncate/Insert Into using a replicated copy of the production database. 6.  Truncate/Insert Into using polybase 7.  Use transactional replication (prod=publisher, dev=subscriber).  You can still do your dev work on the replicated copy. Out of all of these, 7 would prob be the simplest.  Needless to say, pros and cons to all of them. We went for option 1.  We had a really smart developer come in who automated it all for us. "Also, I see things on the Red Gate site about DB Dev Ops.  To be honest, I don't exactly know what that term precisely means.  Any pointers toward educating me on that would also be appreciated." As for this, I have written a post to help people get started with devops:  https://benbrown-sql.com/devops/ Best of luck Ben / comments
Hi @gmartin Welcome to the forums.  We had this scenario too.As well as the options listed above, here are some other possible options.1.  Create SSIS packages that will copy the data over from pro...
0 votes
thanks very much for taking the time to answer.  I will definitely check out the command line and get back to you. / comments
thanks very much for taking the time to answer.  I will definitely check out the command line and get back to you.
0 votes