Microsoft has introduced very impressive new security feature in SQL Server 2016 called Dynamic Data Masking (DDM).Dynamic Data Masking allow user to decide how much of the sensitive data to reveal with minimal impact on the application layer.
For many developers, database security and Access control is just something that gets in the way of development work. However, several recent security breaches have had devastating consequences and have caused a change in attitude about the value to any organisation of having database applications that meet industry standards for access control and security. The problem, however is in admitting that you have a problem and finding answers to those problems you are just too shy to ask in public.
Numbers are both very useful and also susceptible to all sorts of attacks when their domain is limited. Steve Jones looks at some issues occurring in today's world.
Is your msdb database growing bigger every day? If so you might want to consider purging some of the history records. Greg Larsen explains.
Identify the Database Server which is used to mount the database in Sharepoint 2010
Triggers are generally over-used in SQL Server. They are only rarely necessary, can cause performance issues, and are tricky to maintain If you use them, it is best to keep them simple, and have only one operation per trigger. Joe Celko describes a feature of SQL that 'gets complicated fast'.
Technology has made many advances in the world, but it has also eliminated many jobs. This Friday's poll asks how you feel about that as a technology worker.
By Brian Kelley
My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...
By Steve Jones
“On the way to a grand goal, celebrate the smallest victories as if each...
Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...
Jl. Kemang Sel. No.60, RT.4/RW.2, Bangka, Kec. Mampang Prpt., Kota Jakarta Selatan, Daerah Khusus...
Jl. Gedung Hijau Raya No.41, Pondok Indah, Kec. Kebayoran Lama, Kota Jakarta Selatan, Daerah...
How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?
See possible answers