This is the first of two articles to describe the principles and practicalities of masking data in databases. It explains why an organization sometimes needs masked data, the various forms of masked data we can use, the sort of data that needs to be masked, and the potential pitfalls.
ORMs (Object Relational Mappers) are tools (libraries, modules, packages) that provide the functionality for interacting with SQL databases. This article will look at how to use any SQL Database in GO with GORM.
In a previous article, we showed how to expose an Amazon RDS instance to the public internet securely for direct access to the database. In this article we shall configure an Amazon EC2 instance for network access to an existing Amazon RDS instance. The purpose of this would be to make sure that if we deploy an application to this EC2 instance, communication from the client to the RDS instance would be smooth.
For the final release of SQL Server 2022, Microsoft popped a surprise that wasn’t in the release candidates
There are many things to consider when deciding whether to invest in a database monitoring tool or whether to use a homegrown solution. However, the business frequently wants to know one thing and one thing only: what’s the return on this investment (ROI)? In this webinar, Microsoft Data Platform MVP, Grant Fritchey, is joined by our expert panel to share the pros and cons to building a monitoring system versus purchasing one.
Steve reminds us about being charitable if we are fortunate enough to do so.
Learn the basics of the ROUND() function in this article.
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
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