By Lisa Vaas – The patches that could have stopped last week’s attack on Microsoft Corp. database software were so difficult to install or so poorly publicized that some of Microsoft’s own database administrators failed to install them.

From SQLTeam – This article was written by Lynn Zhu and Demico Quinn. They write “Before coming up with the solution that this article will describe, we decided that this would be a great topic to write about and share our experiences with others. We also found that there were not a lot of articles

by Dianne Siebold – Debugging is an integral part of writing an application. Visual Studio .NET provides numerous enhancements to the debugger, including a unified debugging interface, Web service debugging, and cross-language debugging. One of the debugger’s most useful new features is the ability

By Robert Lemos – Other companies also make products containing the Microsoft database software that has been exploited by the worm. More than 30 products, from security scanners to backup servers, use the vulnerable Microsoft SQL Server 2000 and Microsoft SQL Desktop Edition (MDSE) 2000 software, a

by Brad M. McGehee – Learn the basics of SQL Server disaster recovery from a leading industry expert in this exclusive interview.

By Brian Moran – Microsoft released SQL Server 2000 Service Pack 3 (SP3) on January 17, raising the inevitable question, “To install or not to install?” Brian Moran is aggressive about applying service packs, find out why.

One of the most important aspects for a database environment is ensuring reliable backups are being executed and a dependable recovery plan is established in the event of a system failure or data corruption. Several options are available for defining your backup and recovery model and your choices

Alexander Chigrik offers 15 optimization tips for ensuring that you’ve constructed your SQL Server tables to perform in the most efficient manner possible.

By Dennis Fisher – The security researcher whose code was used as a template for the Slammer worm is now reconsidering his position on releasing sample exploit code. David Litchfield, co-founder of Next Generation Security Software Ltd., in Surrey, England, said in a post to the BugTraq maili

No one writes code that references constraint names so it is not important to name a constraint. If this is your thought, it may be time to think again. Eventually you are bound to end up coding a small piece of T-SQL code, which will reference a constraint name; you had better be aware that constra