I've been learning about continuous integration (CI) and continuous deployment (CD) from a number of people at Red Gate Software. As a company, we've embraced the concepts, pushing most, if not all, of our software through this process. We are using our Development Manager software internally for more and more of our web projects. Some of our tools, SQL Prompt, include "experimental features" pushed out rapidly to users, with the options for them to turn these features on or off as users desire. We update these tools often, releasing dozens of times a year. There are no shortage of challenges in working at this pace, but we are addressing the issues as best we can.
One of the big issues that I see in a CD environment is there is a bigger burden placed on developers to ensure the code is of very high quality. In this type of environment, there may be less QA work being done manually, and more automated testing. There is a quicker turnaround when you find issues that developers need to correct. Customers see changes sooner, and more often, and will expect corrections or new features to appear just as quickly. All of this adds up to more pressure on individual developers.
The question I wanted to ask this week is about how developers feel about this? You could take this question a number of ways, but let us know what you think.
Is Continuous Deployment good for developers?
Does this result in higher quality work from developers? Is it more stressful? Does it mean that developers get into a rut and not learn new techniques because they are working faster? Does a developer have less responsibility because automated test and customer feedback will allow them to quickly address issues?
I think this is a multi-edged sword for developers. It can be a burden or a blessing, but a lot of the way you view it probably depends the individual developer. No matter what the issues, if you use it to improve your skills, as well as your software, I think it's the best way to build software.
You are tasked with examining poor performance for queries on a certain table, or range of tables. Perhaps a sales report is timing out or running unacceptably slow; perhaps your web application is failing to return the result set before the application timeout is reached. You need to find out what's causing the bottleneck, and optimize either the queries used, the table schemata, or both. More »
Teach yourself the programming fundamentals of SQL Server 2012—one step at a time. Ideal for beginning SQL Server database administrators and developers, this tutorial provides clear guidance and practical, learn-by-doing exercises for building database solutions that solve real-world business problems.
# This script is used ONLY in test/development environments!
# If you are planning to use this to restore production databases you should first test and evaluate the script in a test environment.
# You can change the script if needed to match your environment and needs.
# Script will restore all the databases (*.bak) which are located in the folder defined as parameter.
# It will place database files to location defined for data and log files in SQL Server instance settings
# Steps to run this script:
1)First Save the script in file "D:\PSScriptToRestoreDatabases.PS1" -- you can save it at any location and write the command accordingly.
3)write below commands .. Specify the BackupFileLocation and SQLServerInstance in this command D:\PSScriptToRestoreDatabases.PS1 -BackupFileLocation [bak_file_location] -SqlServerName [SQL Server Instance]
-BackupFileLocation parameter is the full path to the folder where the BAK files are located
-SqlServerName parameter is the SQL Server instance name where to restore
xp_regread execute permission denied
- Hello All,
I am having the issue described here:
More specifically the user right-clicks on a table and gets 'EXECUTE permission denied...
Performance counters missing...
Hi Team ,
SQL Server performance database objects
These SQL Server performance objects are not available:
The SQL Server is not...
- I uploaded a trace file to DTA, the file size is 4GB & i need to run it against all Databases.
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.