SQL Server DBA On-Boarding Checklist
How can we be sure that the new DBAs are productive a soon as possible? How can we use highly qualified contractors in the most effective way from day one?
2017-07-12
3,599 reads
How can we be sure that the new DBAs are productive a soon as possible? How can we use highly qualified contractors in the most effective way from day one?
2017-07-12
3,599 reads
To achieve gains from Database Lifecycle Management in general, and in Continuous Deployment in particular, it pays to aim for lightweight but consistent techniques and processes, refining them iteratively in the light of experience. Edward Elliott describes a Test-driven development process for developing SQL Server databases that worked for CD, based on a series of steps. Though the tools for CD may be necessary, they are not sufficient, without an effective structured process.
2017-07-11
3,560 reads
One of the key tenets in DevOps is to involve the Operations team in the full software development lifecycle and, in particular, to ensure that operational requirements are incorporated...
2017-07-11
4,304 reads
The majority of Azure SQL Database related features reach their General Availability (GA) stage relatively quickly. There are however, some exceptions. The most prominent example in this category is likely Azure SQL Data Sync, which has remained in Preview since its introduction 7 years ago. Fortunately, there are signs that this service might be finally reaching production-ready state. In this article, Martin Pollicht introduces its main characteristics.
2017-07-10
2,856 reads
Jonathan Kehayias discusses SQL Server on VMware, and how to monitor CPU performance – with or without access to vCenter.
2017-07-07
5,127 reads
There are multiple ways to accomplish a database restore. But if you wanted to restore a database from a script how might you accomplish that task quickly and accurately?
2017-07-06
3,891 reads
TSQL Code must work properly and efficiently. That's not enough though. Unless you are working alone, have perfect memory and plan to never change job, then you need to comment and document your code, it must be inherently readable, well laid out, use informative and obvious names, and it must be robust and resilient; written defensively. It must not rely on deprecated features of SQL Server, or assume particular database settings. Robert Sheldon starts a series of articles that explains the basics.
2017-07-05
7,732 reads
In this post, Tim Smith looks at the different options you can use to audit your SQL Server extracts and loads during the ETL process.
2017-07-04
3,755 reads
What native SQL Server options are available to export to Excel? Jeremy Kadlec explains.
2017-06-30
5,930 reads
Tim Radney of SQLskills walks through multiple automation methods you can use to manage and maintain your Azure SQL Databases.
2017-06-29
3,697 reads
By HeyMo0sh
As a DevOps professional, I’ve seen firsthand how cloud costs can quickly spiral out...
By Steve Jones
AI is everywhere. It’s in the news, it’s being added to every product, management...
By Vinay Thakur
RAG — Retrieval Augmented Generation. we have covered so far — embeddings, vectors, vector...
Hi, ssms is free here. I can think of other reasons to do this...
I've written some documentation on using different Markdown types of files on GitHub. It's...
Comments posted to this topic are about the item Not Just an Upgrade
I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens?
USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO USE DNRTest GO CREATE TABLE MyTest(myid INT) GO USE master RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACESee possible answers