Editorial

SQLServerCentral Editorial

The Security of You

  • Editorial

There is a lot of data out there that is specific to an individual, none more important perhaps than biometric data. Steve Jones writes a bit about the security implications involved in working with this data. (This editorial was originally published on Nov 10, 2008. It is being re-run as Steve is at SQL Bits.)

You rated this post out of 5. Change rating

2013-05-03 (first published: )

300 reads

SQLServerCentral Editorial

Are Triggers a "Legacy" Feature?

  • Editorial

It is late evening. Something is wrong with a database. You narrow down the possibilities, getting more frustrated and puzzled. Stay calm. Check the inputs systematically. No! The data going into that table is right, but when you then read it in the table, it's wrong. Why did I stop believing in the supernatural? Then it hits you. Every time it comes as a surprise. They're using triggers. (This editorial was originally published on Nov 10, 2008)

You rated this post out of 5. Change rating

2013-02-19 (first published: )

629 reads

Blogs

Overcoming Imposter Syndrome: A Plan

By

My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...

Advice I Like: Celebrate Success

By

“On the way to a grand goal, celebrate the smallest victories as if each...

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

Read the latest Blogs

Forums

What Are You Waiting For?

By Laura Copeland

Comments posted to this topic are about the item What Are You Waiting For?

BCA Finance CirebonTelp/Wa 0821.3111.159

By twentyonepilotsmerch

Komplek CSB Blok Berry Green, Jl. DR. Cipto Mangunkusumo No.26 Kav. 17 - 18,...

BCA FINANCE SUKABUMI,Telp/Wa 0821.3111.159

By twentyonepilotsmerch

Jl. Sudirman No.31, Gunungpuyuh, Kec. Gunungpuyuh, Kota Sukabumi, Jawa Barat 43123

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers