The DevOps movement is supposed to promote a closer collaboration between developers, testers, operational people, and really anyone else that must help software gets build and deployed. The developers need to coordinate their needs and requirements with operational staff. They should work early on with any staff performing testing to help them ensure that bugs are caught quickly and fewer slip through to production. At the same time, operational staff should be responsive and helpful in all the environments software moves through. Operational staff should help build and automate the configuration of development and testing environments, ensuring that systems are built in a repeatable fashion as well as the same way in each stage of the software development pipline.
However, is devops killing the developer? If developers are becoming responsible for testing, that's bad. If developers must learn to function as a DBA as well, then I certainly expect they'll write less code. If developers need to ensure the software can be installed on production systems and train operations staff, then I suspect they aren't very happy with their jobs.
But that's not DevOps. If that's how your organization runs its development, it doesn't understand DevOps. Developers should be leaning on and learning from, as well as teaching other staff. When I read that post, I think the developer has missed the idea of DevOps. It isn't that developers need to become completely versed and responsible for the full stack. It's that they should be working with everyone involved in the process the entire time that software is being developed, using the specialized knowledge each person has.
DevOps isn't something new. I've worked in teams that worked like this in the past, but we never had a name for what we did. We just thought we were part of the same team. I've also worked in organizations with walls between all groups. That wasn't a team, and we had lots of four letter words for that style of process.
DevOps is a good term and a good idea for software development. If a company implements it well, then it works and people are happier with the way software is produced. If they aren't, then the process hasn't been configured correctly.
There’s sinister work afoot at Monte Bank. Backups corrupted beyond repair – and without a trace of the cause. Can the DBA Team save the data? Find out in Part 3 of their new series, 5 Worst Days in a DBA’s Life.
24% of devs don’t use database source control – make sure you aren’t one of them
Version control is standard for application code, but databases haven’t caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out…
This article demonstrates a method of importing a data file directly into a temporary table and selectively inserting data from the temporary table into a SQL Server table, all in a single set of SQL commands. More »
The SSC team has put together a little quiz on database source control to go with Rob Richardson, Robert Sheldon, and Tony Davis' new book, SQL Server Source Control Basics. Do you daydream about source control... or daydream to avoid it? More »
SQL Server 2012 brought in some great new features and one of the important ones is scalability and performance via AlwaysOn. AlwaysOn is a superset feature and is a combination of many things you will learn about. As the language suggests, this technology achieves a SQL Server infrastructure that can be "always on". For businesses that run 24x7 downtime means the loss of business. This type of risk is out of the question for these businesses. This book discusses in detail the concepts of SQL Server AlwaysOn starting from the basics.
Yesterday's Question of the Day
(by Steve Jones):
Can I create a regular table in tempdb?
create table MyTable
, mychar varchar(200)
Answer: Yes, we can run this as is.
We can easily create regular tables in tempdb. Run the code to see that this is allowed.
Comparing records to previous records in query
Here is a sample table:
I'm looking to write a query that will only return the invoices for each customer that...
need help parsing XML
- i have a Storedprocedure that returns an xml
@SearchType = N'A',
@SearchInputList = N'57575757',
@FAsInputList = null
below is the XML
import to multiple excel files
I have a query with the fields: unitname, pointname, point description
smithfield,waverley, boot status
islignton, shenfield, exit status
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.