Articles

External Article

Securing SQL Server with DoD guidelines

Making sure your SQL Servers are secured against malicious users is difficult. The United States Defense Information Systems Agency (DISA) publishes a set of guidelines for organizations securing different pieces of software that connect to the US Department of Defense’s networks (DoD). Whether you’re working with the DoD or not, these Security Technical Implementation Guides (STIGs) are a good resource to help you understand potential security vulnerabilities and mitigate them.

2021-02-22

SQLServerCentral Article

Getting Started with Azure Purview

Introduction Azure Purview is Microsoft’s unified data governance service that helps you discover and get insight into your available data. It replaces Azure Data Catalog and is now based on Apache Atlas, one of the leading open-source data governance and metadata frameworks. Apache Atlas was created by Hortonworks and big names within finance, pharma, etc. […]

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(2)

You rated this post out of 5. Change rating

2021-02-18

5,267 reads

Blogs

T-SQL Tuesday #204: Are tech blogs dead?

By

This is my late response to T-SQL Tuesday #204. I almost always forget about...

Should You Use CHOOSE(): #SQLNewBlogger

By

I was experimenting with CHOOSE() recently after I was asked a question. In a...

T-SQL Tuesday #204 – Are blogs still relevant? (Roundup)

By

I did not expect 27 responses to my T-SQL Tuesday #204 invitation, but it...

Read the latest Blogs

Forums

Why Successful SQL Server Backups Are Not Enough

By Almighty

Comments posted to this topic are about the item Why Successful SQL Server Backups...

Adding Bits II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Adding Bits II

An Unlimited Token Budget

By Steve Jones - SSC Editor

Comments posted to this topic are about the item An Unlimited Token Budget

Visit the forum

Question of the Day

Adding Bits II

I have a table, dbo.bittest, where I am testing an application response. This has this structure:

CREATE TABLE [dbo].[BitTest]
(
[insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()),
[a] [bit] NULL
) ON [PRIMARY]
GO
My application runs this code:
INSERT dbo.BitTest
(
    insertdate,
    a
)
VALUES
(DEFAULT, true)
GO

See possible answers