Andy Warren

I started my SQL journey here at SQLServerCentral as one of the founders, helping to build a place to share and learn that continues to thrive under the editorial guidance of my friend Steve Jones. I've done a lot of volunteer work over the years ranging from our local SQL group (oPASS, SQLOrlando) to serving on the Board of Directors of PASS to designing and building the framework of SQLSaturday (which has gone on to produce more than 1000 locally managed events since we started in 2007). These days I manage a DBA team, but over the years I've been a trainer, consultant, contractor, and DBA. I'm rarely present on social media, the best way to contact me is here, LinkedIn, or via email.

All authors

SQLServerCentral Article

A Pattern Based Approach to Masking Errors

A few years ago I had a requirement to allow both developers and customers to see rows from a table used to store error information while making sure that any PII, PCI or similar sensitive data was not displayed. The tolerance for “oops” was low! This article presents one way to solve the challenge by […]

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(1)

You rated this post out of 5. Change rating

2020-04-27

1,782 reads

SQLServerCentral Article

Error Logging Gone Wild

Many of have applications that log errors to a table. Ever thought about what happens when an application starts to throw a lot of errors? This article looks at the problem and some of the responses you might consider having ready in case it happens to you!

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(6)

You rated this post out of 5. Change rating

2016-10-11

1,820 reads

Technical Article

Time to Rebrand

I became a SQL guy back in 1998 because the company that hired me used SQL Server. It’s been a good ride and it’s paid the bills, but after 15 years or so it’s time to do something different.

2015-04-01

6,297 reads

Technical Article

Mo-SQL

If you’re involved in the database world it’s hard to have missed the rise of the “no-sql” database products, designed to – depending on your view or the product I suppose – make databases simpler, break out of the transaction database paradigm, scale out across hundreds of machines, make it easy to change the db design (or not require one). I think some of the problems no-sql tries to solve are real, others reflect a lack of awareness/training/tools on how and why relational databases could not just solve the problem, but solve it better.

2013-04-01

3,528 reads

All authors

Blogs

Measuring RAG Solutions: Are We Retrieving the Right Information?

By

A RAG pipeline that answers questions in the demo is not the same thing...

Advice I Like: Lots of Ideas

By

“A multitude of bad ideas is necessary for one good idea” – from Excellent...

Building a DBA Agent for Your SQL Server Estate with MCP

By

Yesterday I gave a talk for MSSQLTips called “Building a DBA Agent for Your...

Read the latest Blogs

Forums

Alamat BCA KCP Cilandak KKO I Telp/Wa:0821-8200-233

By layanan_Bca88

Telp/Wa 62 821-8200-233 Jl. Raya Cilandak KKO No.9, RT.1/RW.5, Ragunan, Ps. Minggu, Kota Jakarta...

Alamat BCA KCP Arkadia Telp/Wa:0821-8200-203

By m4rt1n4

Telp/Wa 62 821-8200-203 Gedung Perkantoran Hijau Arkadia, Tower C - Ground Floor, unit C103,...

BCA KCU KUNINGAN Telp/Wa:0821-8200-174

By R4nt4u

Telp/Wa 62 821-8200-174 Menara Karya, Jl. H. R. Rasuna Said Ground floor, RT.1/RW.2, Kuningan,...

Visit the forum

Question of the Day

Adding new column with DEFAULT

Which number will the COUNT() return after executing the following statements: 

DROP TABLE IF EXISTS #test;
CREATE TABLE #test (id INT)
INSERT INTO #test (id)
SELECT *
  FROM GENERATE_SERIES(1, 3) AS gs
;

ALTER TABLE #test ADD flag BIT CONSTRAINT DF_#test_flag DEFAULT 0;
go
UPDATE #test SET flag = 0 WHERE id = 1
UPDATE #test SET flag = 1 WHERE id = 2

INSERT INTO #test (id) VALUES (4)

SELECT COUNT(*)
  FROM #test AS t
 WHERE flag = 0
 

See possible answers