Articles

Technical Article

Row Level Security with SQL Server 2016

Have you ever wanted an easier way to provide security at the record level? If so, you can now easily do this with the Row Level Security feature that is being introduced with SQL Server 2016. Greg Larsen shows you how easy it is to use this new feature as a way to provide user access to a specific set of records.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(1)

You rated this post out of 5. Change rating

2016-04-19

4,714 reads

SQLServerCentral Article

sp_msforeachdb: Improving on an Undocumented Stored Procedure

Have you ever wanted to run a query across every database on a server with the convenience of a stored procedure? If so, Microsoft provided a stored procedure to do so. It’s unreliable, outdated, and somewhat obfuscated, though. Let’s improve on it!

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(43)

You rated this post out of 5. Change rating

2016-04-15 (first published: )

17,182 reads

External Article

T-SQL Window Function Speed Phreakery: The FIFO Stock Inventory Problem

Sometimes, in the quest for raw SQL performance, you are forced to sacrifice legibility and maintainability of your code, unless you then document your code lavishly. Phil Factor's SQL Speed Phreak challenge produced some memorable code, but can SQL features introduced since then help to produce code that performs as well and is also easy to understand? Kathi Kellenberger investigates.

2016-04-15

5,825 reads

Technical Article

What is Code Coverage For?

Code coverage is a practice that goes hand in hand with automated testing, reporting the percentage of your code that has been exercised during a test run. Ed Elliott and Redgate have partnered to make a code coverage tool available for SQL Server, both free and open source. SQL Cover measures the coverage of your SQL Server stored procedures and functions. It has built-in support for the popular tSQLt unit testing framework, but can also be used alongside any automated testing framework of your choosing. Find out more in this blog post.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2016-04-14

4,457 reads

Blogs

Word to the wise: don’t turn on SQL vulnerability checks on a blog about SQL

By

Recently, in an attempt to thwart leechers (1990s kids will know), I added some...

Dazzling Stuff in Databricks (SQL) – Qualify

By

Once upon a time I had a series about some cool stuff in Snowflake:...

Advice I Like: Overnight Success

By

“Most overnight successes – in fact any significant successes – take at least 5...

Read the latest Blogs

Forums

Kantor Resmi BCA KCU MADIUN Telp&Wa .0821°8200°203

By layanan_Bca88

Jl. Jend. Sudirman No.79-81, Kejuron, Kec. Taman, Kota Madiun, Jawa Timur 63132.. Fungsi Layanan:...

Kantor BCA KCU BOROBUDUR Telp&Wa .0821°8200°233

By m4rt1n4

Call Cs 08218200233 Jl. Borobudur No.I, RT.03/RW.07, Mojolangu, Kec. Lowokwaru, Kota Malang, Jawa Timur...

Why Successful SQL Server Backups Are Not Enough

By Almighty

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

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