﻿<?xml version="1.0" encoding="utf-8"?><rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="2.0"><channel><title>SQLServerCentral.com Content tagged Security, Strategies, SQL Server 2005 - Security</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Security, Strategies, SQL Server 2005 - Security posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Stop SQL Injection Attacks Before They Stop You</title><description>This article discusses: How SQL injection attacks work, Testing for vulnerabilities, Validating user input, and more.</description><guid>http://www.sqlservercentral.com/redirect/articles/3073/</guid><pubDate>2007/07/09</pubDate><link>http://www.sqlservercentral.com/redirect/articles/3073/</link></item><item><title>Anticipate the worst when developing SQL Server databases</title><description>Arthur Fuller advises DBAs to try to break their software in order to make sure their SQL Server databases can withstand potential attacks. See if your code can hold up to his suggested tests.</description><guid>http://www.sqlservercentral.com/redirect/articles/2620/</guid><pubDate>2006/10/12</pubDate><link>http://www.sqlservercentral.com/redirect/articles/2620/</link></item></channel></rss>