Stop SQL Injection Attacks Before They Stop You
This article discusses: How SQL injection attacks work, Testing for vulnerabilities, Validating user input, Using .NET features to prevent attacks, and Importance of handling exceptions
This article discusses: How SQL injection attacks work, Testing for vulnerabilities, Validating user input, Using .NET features to prevent attacks, and Importance of handling exceptions
The CLR integration in SQL Server 2005 greatly expands on the capabilities of the SQL Server platform. One new area is the ability to build user-defined types and user-defined aggregates. Solomon Rutzky brings us a way to get around some of the limitations in this area with his SQL# toolkit.
Today is the opening day for the PASS conference here in Denver and it's kind of exciting. As many of you read this, I've hopefully gotten Simon Galbraith, owner of Red Gate software, and my boss, out here at the ranch shoveling manure. He's anxious to get on the ATV for a ride, so maybe I can work out a deal to reduce my workload 🙂
In the latest in their popular series on 'Unit Testing' database development work , Alex K and Alex S give some examples of unit testing Database Modifications
We've compiled a list of our dozen most popular tips in the area of upgrading to SQL Server 2005 and they run the gamut.
Everyone wants to know what a DBA does and it is becoming a hard question to answer as the responsibilities and capabilities of database platforms increase. Longtime author Vincent Rainardi brings us the proposition of a new type fo DBA, one that focuses more on data warehousing.
There's a free event in Indianapolis for SQL and .NET developers. It's on October 13th and it's jointly sponsored by the .NET and SQL users groups. If you're in the area reigster and support this group.
There have been some strange things that have happened in this world that I would never have expected. The Red Sox winning the World Series, Macs with Intel processors, and are things I never thought I'd see. But none of the them seems as strange as this to me.
One of the fundamental rules of a stable, controlled production system is that you apply updates singly, after they've been tested, and you document the change. This way you can ensure that if a problem occurs, you can do some backtracking to see what might have caused instability.
An article explaining where to find packages when saved to SQL Server.
By John
Microsoft has released SQL Server 2025, bringing big improvements to its main database engine....
By Steve Jones
A customer was asking about what certain items in Redgate Monitor mean. They have...
By Brian Kelley
Pass or fail, act on your certification test results.
I have table: t1 in schema1 with 19 billion records. I have another table...
Comments posted to this topic are about the item Minimally Viable Security
Comments posted to this topic are about the item Encoding NULL
What is returned from this code in SQL Server 2025?
SELECT BASE64_ENCODE(NULL)See possible answers