#1 - Ten hacker tricks to exploit SQL Server systems
SQL Server hackers have a medley of tricks and tools to gain access to your database systems. Learn their techniques and test SQL Server security before they do.
#2 - Password cracking tools for SQL Server
When performing SQL Server penetration tests and security audits, there is one probe you must not miss: password cracking. Get tools to check for password weaknesses.
#3 - Restore basics: How to restore using T-SQL commands
SQL Server Enterprise Manager may be a quick and easy way to run backups and restores, but T-SQL commands offer much greater flexibility.
#4 - Migrating SQL 2000 DTS packages to SQL Server 2005 Integration Services
SSIS is more than a replacement for DTS Packages. Migrate to this new powerful ETL platform with the transitional tools of Upgrade Advisor and Package Migration Wizard.
#5 - How to debug T-SQL stored procedures
Easy-to-use graphical debugging tools in Visual Studio 2005 will help simplify the process of unit testing your T-SQL code.
#6 - Exception handling best practices in SQL Server 2005
SQL Server 2005 brings you TRY/CATCH, a new T-SQL feature that helps find and address errors before they reach application code. Get best practices for working with it.
#7 - Stored procedures vs. dynamic SQL: When should you use each?
Stored procedures and dynamic SQL each have their place in the SQL Server world. In this tip, Serdar Yegulalp maps out the best scenarios for each.
#8 - Restore basics: How to restore SQL Server using Enterprise Manager
To restore a SQL Server database you have two basic options. Edgewood Solutions' Greg Robidoux explores the first of two in this SQL Server restore series.
#9 - SQL Server Integration Services programming basics
SSIS is more than a tool to move data around in SQL Server 2005. Contributor Serdar Yegulalp outlines its features while explaining why SSIS is an impressive ETL tool.
#10 - Stored procedure: Determine last database backup
You have many SQL Servers to administer and you just want to know when the last backup was taken for each database on each instance. This stored procedure will help.
Take a look at the Top 10 SQL Server tips of 2005.
This was first published in December 2006