Comments
Sort by recent activity
It has bailed out a lot of teams I have worked in whose database development process could only be described as a free-for-all. / comments
It has bailed out a lot of teams I have worked in whose database development process could only be described as a free-for-all.
hi @SkipSailors - if you have SQL Server 2016 SP1 or onwards you can use the CREATE OR ALTER PROCEDURE statement. example below: CREATE OR ALTER PROCEDURE dbo.sp_test AS SELECT 1; GO EXEC dbo.sp_test; go CREATE OR ALTER PROCEDURE dbo.sp_test AS SELECT 2 go EXEC dbo.sp_test / comments
hi @SkipSailors - if you have SQL Server 2016 SP1 or onwards you can use the CREATE OR ALTER PROCEDURE statement.example below:CREATE OR ALTER PROCEDURE dbo.sp_testASSELECT 1;GOEXEC dbo.sp_test;goC...
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...
I'm starting a new job at the end of Feb - In the new role I want to focus on helping create a 'high performing team'. on the technical side, one thing I will probably do is to demo a few different products and get the team to decide upon their DevOps toolchain as a group. / comments
I'm starting a new job at the end of Feb - In the new role I want to focus on helping create a 'high performing team'. on the technical side, one thing I will probably do is to demo a few differen...
SQL Source Control just edges it over Prompt - sometimes getting database developers to use source control is like herding cats. SQL Source control makes it so easy that you see very little resistance and the devs can concentrate on delivering value. / comments
SQL Source Control just edges it over Prompt - sometimes getting database developers to use source control is like herding cats. SQL Source control makes it so easy that you see very little resist...
hi @Sergio R - I did spend some time with the command line using the include switch and made some progress but it was a struggle and wasnt "ingeniously simple"... I've created a very bad screen mock-up of what I was thinking to see if anyone else sees value in what i'm talking about. its based on the comparison pane inside SQL Source Control... its basically being able to run something like K-Diff or WinMerge from within SSMS. cheers Ben [image] / comments
hi @Sergio R - I did spend some time with the command line using the include switch and made some progress but it was a struggle and wasnt "ingeniously simple"... I've created a very bad screen moc...
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.
Hello, this isn't specifically a red-gate question but there are some red-gate resources that can help you. this simple talk article looks decent https://www.red-gate.com/simple-talk/sql/database-administration/preparing-to-upgrade-your-sql-server/ alternatively, you can search SQLServerCentral and/or post a question on the forum. The big thing with SQL Server 2016 SP1 is that you get most Enterprise Features included with Standard Edition. I've migrated loads of databases and never really had any issues. I'm sure there is some code analysis features in SQL Prompt that would alert you early. Best advice I can give is don't wait around, give it a bash on a test environment and you will have a feel pretty quickly of how difficult the task will be. / comments
Hello, this isn't specifically a red-gate question but there are some red-gate resources that can help you.this simple talk article looks decenthttps://www.red-gate.com/simple-talk/sql/database-adm...
I love SQL Prompt because it gives me back my time - in abundance, every single day. / comments
I love SQL Prompt because it gives me back my time - in abundance, every single day.
"it would be great if you could try to switch branches and let us know if the end result in the Get Latest screen is as you would expect" - I will have a play around next week and get back to you / comments
"it would be great if you could try to switch branches and let us know if the end result in the Get Latest screen is as you would expect" - I will have a play around next week and get back to you