what you need to know to set up your environment to use workflow foundation while still using visual studio 2005

For some reasons, DBA’s need to rename their Databases. One of the reasons might be to comply to Best Practices Policy changes. Here we are going to rename our Database named “Bad_Ass_DB” into “Best_Practice_DB”. This is how Database renaming with TSQL is done in SQL Server 2005....

Gotcha to watch out for with the SQL security update.

Deadlocks can be a pain to debug since they're so rare and unpredictable. The problem lies in repeating them in your dev environment. That's why it's crucial to have as much information about them from the production environment as possible. This is one way of getting it immediatly when it happens,

Visual Studio 2005 (codename Whidbey) and Visual Studio 2008 (codename Orcas) ... What's Next in VS? it will be "Rosario" to check its new Features and Specifications and download its VPC

This article is about configuring SQL Server to query Active Directory using LDAP. It also lists the possible columns that can be used with LDAP query.

Automatic properties are nice, but sometimes they just won't do. Visual C# 2005 included a 'prop' code snippet for a full property with backing filed but 2008 changed the snippet to generate an automatic property. Here's how to restore the 2005 snippet.

Step by Step building a project template and wizard in VS 2005

Updating / Accessing data from another server is very easy using SQLServer 2005. Its very handy to restrict access to Production Server.

Some basic differences among SQL Server 2005 unique columns (primary key, unique key, unique identifiers etc).

How to create a PerfMon counters log file and SQL Profiler Trace file, how to read them both and how to correlate the two files in SQL Profiler.

There are at least 4 ways you can COUNT in SQL Server: COUNT(*), COUNT(ColumnName), COUNT(DISTINCT ColumnName) AND SUM() All 4 combined can be used to speed up queries especially for reporting.

If you move Web Application Projects between Visual Studio 2008 and Visual Studio 2005 and a machine that doesn't have Visual Studio 2005 installed you will find that the project doesn't load due to a build target difference.

This article focuses especially on ADO.NET-side of handling the returned values from the SQL Server 2005's OUTPUT. It is a good alternative for the scope_identity() etc.