In this third article of the exploring SQL Server 2016 Always Encrypted series, Greg Larsen looks at the differences between an Always Encrypted column that uses an encryption type of Deterministic and those that use encryption type of Randomized.
Automatically capture replication conflicts and generate an automated email notification.
This week Steve Jones wonders about the age of your instances and whether you are planning on upgrades or aware of how many out of support instances you might have.
Read this tip to learn how to import data from multiple Excel worksheets into SQL Server using SSIS.
An evaluation of the SQL Azure Database Performance Levels recommended by the DTU Calculator service, and a comparison with on premise SQL Server performance.
We have an operating system for how our organizations are run. Steve Jones talks about a new one that might be important for the world rules by software.
In-Memory OLTP has evolved to be a great solution. However, a production system that uses it needs careful monitoring to avoid stress conditions becoming problems. As with many new features of SQL Server, it pays to plan a monitoring strategy to ensure that you are alerted as soon as possible when things go awry.
The idea of using a queue in a database is one that some people try to avoid, preferring to use a messaging service. However, Steve Jones notes that this isn't always necessary.
Now that we have our database under source control, we will want to share our work with other developers. If we are in a centralized source control system, our changes may be committed straight into the central repository.
When we are working in a distributed system, it means pulling down any changes from other developers, addressing any areas of conflict, and pushing our changes up to allow others to benefit from our work. This allows our changes to be synchronized with the changes other developers have made.
This level is principally about setting up a distributed source control system, namely Git, and how to commit database development changes to a local repository, before pushing them into a remote 'central' repository for sharing with other developers.
The next level will delve a little deeper into Git's versioning mechanisms, and show some examples of how to share database changes during development, and how to deal with conflicting changes.
Jeremy Kadlec introduces the Enhanced Data Integration Suite (EDIS), a SQL Server T-SQL stored procedure based solution to automate, manage, and audit ETL processes so you no longer have to manually build SSIS Packages.
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers