Articles

External Article

Practical steps for end-to-end data protection

If you plan to make production data available for development and test purposes, you'll need to understand which columns contain personal or sensitive data, create a data catalog to record those decisions, devise and implement a data masking, and then provision the sanitized database copies. Richard Macaskill show how to automate as much of this process as possible.

2019-08-02

SQLServerCentral Article

Worst Practices - Objects Not Owned by DBO

Last week Andy launched a new series about Worst Practices by talking about why the Hungarian naming convention is bad for column names. This week he's at it again, declaring that the practice of having objects owned by anyone other than dbo is BAD! Agree or disagree, we think you'll enjoy reading this article and adding your thoughts to the discussion!

(7)

You rated this post out of 5. Change rating

2019-08-01 (first published: )

38,423 reads

Blogs

A New Word: on tenderhooks

By

on tenderhooks – adj. feeling the primal satisfaction of being needed by someone, which...

Ramblings about data communities and your contributions, no excuses

By

I have been active in the data community throughout my career. I have met...

SQL Server Journey till 2025 (brief)

By

Quick Summary for Microsoft SQL Server till 2025, I am fortunate to be part...

Read the latest Blogs

Forums

Ola Hallengren Index Optimize Maintenance can we have data compression = page

By JSB_89

I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...

how do i map the "current" object entry in for each to one variable

By stan

hi, in an ssis  for each loop over an object variable called MyListVariable, i...

Simulating Mercury’s Orbital Motion Using Pure T-SQL (NASA 2025 Dataset)

By NKTgLaw

SQL Server is typically viewed as a transactional or analytical database engine. However, it...

Visit the forum

Question of the Day

String Similarity I

On SQL Server 2025, when I run this, what is returned?

SELECT EDIT_DISTANCE_SIMILARITY('SQL Server', 'MySQL')

See possible answers