Data Sanitization is the process of making sensitive information in non-production databases safe for wider visibility. This White Paper is an overview of various techniques which can be used to sanitize sensitive production data in test and development databases.
2004-11-29
1,885 reads
Creating an enterprise security plan is a complex endeavour. It involves evaluating multiple threats that gain access through many network paths to a hodgepodge of different applications and systems. With the focus on systems and paths, databases are frequently overlooked. Securing the database should be a fundamental tenet for any security practitioner when developing his or her security plan. The database is the source of data, the "crown jewels" in the information economy. Any security effort must start with this in mind and end with the strongest level of controls applied at the database layer.
2004-11-26
2,129 reads
SQLServerCentral.com wrapped up two weeks of voting by the community on the best third party products to help you with your SQL Servers. Read on to see who won.
2004-11-24
6,697 reads
Transactions in SQL Server can be very complicated, and are often misunderstood. Don Peterson brings us part 2 of his series on transactions. This part deals with XACT_ABORT, compilation errors and error handling in transactions.
2004-11-24
19,730 reads
Over the last few years, corporations have invested billions of dollars to integrate the automations of core business systems in large ERP applications. This paper looks at the risk of downtime and solutions for building an around-the-clock database.
2004-11-24
2,129 reads
Mattias Fagerlund, a longtime author and contributor here is developing a new product to help developers migrate between versions of their databases. He's searching for a few Beta developers to assist.
2004-11-23
2,777 reads
SQL Server has a great build in messaging system with SQLMail. Unfortunately it requires Outlook and Exchange to work properly. Some people don't like this or do not run Exchange and have issues getting it to work. Gregory Larsen takes a look at how you can use SMTP to send email from SQL Server.
2004-11-23
21,135 reads
E
very day a developer somewhere needs to write code to iterate through SQL Server™ system objects, query and update tables in linked servers, handle optimistic concurrency, and retrieve column and stored procedure metadata. In this month's column, I will address these and other T-SQL development scenarios based on some of the questions I most frequently receive from readers.
2004-11-23
1,686 reads
How prepared are you for your next interview? How prepared are you to give one? SQLServerCentral.com has compiled a number of questions from our ever popular Question of the Day into a book. Read about the project and show your support today by picking up a copy.
2004-11-22
6,531 reads
There are plenty of good sources of information about how to deploy SQL Server in a secure fashion. However, these resources are often targeted at database administrators tasked with securing already developed applications. In addition, there is a rich body of information that discusses writing secure .NET and ASP.NET code, including .NET code that accesses SQL Server. However, many of these resources focus on the data access code that runs on the application servers rather than the Transact-SQL (T-SQL) code that executes within SQL Server. Developing T-SQL code that runs securely on SQL Server is the primary focus of this column.
2004-11-22
2,400 reads
By ChrisJenkins
Have you been thinking about migrating your reporting to Microsoft Fabric or Snowflake but...
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
WA:08218154393 Jl. Paus No.81, RT.1/RW.8, Wil, Kec. Pulo Gadung, Kota Jakarta Timur, Daerah Khusus...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers