Maybe Security is Harder than Rocket Science
It's hard to build strong security over time, but it's worth the effort. Steve Jones notes that even smart people have problems implementing strong security.
It's hard to build strong security over time, but it's worth the effort. Steve Jones notes that even smart people have problems implementing strong security.
From an IT infrastructure and compliance perspective, the importance of protecting data is clear. But it also has profound business implications and can even be a competitive differentiator by helping drive customer loyalty and retention. David Hobbs-Mallyon talks about Microsoft’s approach to data security.
Rodney Landrum gets lost in the fourth dimension, while coding the infinite possible combinations of SQL Server dates and times.
Learn a quick method to find and remove duplicate records in your SQL Server tables.
What version of your code is the true one? Steve Jones talks some version control today.
When starting out with PowerShell, it is hard to escape from the detail to work out the best strategy for creating scripts. Laerte Junior explains how, when and why it pays to think in terms of versatile functions to meet varying demands.
This article talks about using the statistical program, R, for applying simple statistics against data in Microsoft SQL Server.
One of the most important features of the SQL Server 2016's new Query Store is the reporting. With these features, it is now possible to get a wealth of information on how your query workload is performing, either aggregated for the entire query workload or for a single query. With this information, you can see the effects of 'forcing' an execution plan for specific queries and get feedback of the consequences.
rsNeatPublish: Toolset to automate deployment of all SSRS 2008R2/12/14/16 objects
Today Steve Jones looks at security training and the need for understanding from upper management.
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