You won't completely avoid locks. There are cases where shared Schema locks will be put in, even with the nolock hint. Of course, these locks just keep you from modifying...

One way to do it is the following (this works against the Products table in the Northwind database):

CREATE PROC usp_ShowProduct

  @ProductID int = 0

AS

SELECT 

...

Updates to system tables are generally discouraged. One way to do this would be to issue the appropriate ALTER TABLE statements via a script which went out and searched all...

You can change the collation using the rebuildm.exe command from the command line. However, if you are doing this on an existing system, you should back up your existing data...

SQL Agent will allow you to create jobs which run on a schedule. However, SQL Agent has to be running during the time the jobs need to run.

SQL Server is...

The bulkadmin role is a fixed server role. It is new to SQL Server 2000. To find it, go to Security | Server Roles in Enterprise Manager for a given...

What you can do is build a database that has the schema as it should be. Then use a tool like SQL Compare to check the differences in the schema....

The best way to think of triggers is to consider them specialized stored procedures which fire on a particular data change operation. You've got the basic format correct.

The inserted and...

Best way to let them see the data is to put it in a trace table as a staging point and then put it in a usable form in another...

Since the column already exists, you'll need to add it as a constraint:

ALTER TABLE users

ADD CONSTRAINT DF_users_picker DEFAULT '1' FOR picker

K. Brian Kelley

http://www.truthsolutions.com/

Author: Start to Finish...

Thanks for those additions. Indeed, both are missing from the article and are useful for helping us get the most out of QA.

K. Brian Kelley

http://www.truthsolutions.com/

Author: Start to Finish Guide to...

As NPeeters has done, the WHERE will need to have some expression where a true or false value can be obtained. With the original query, just moving the ORDER BY...

In the derived table, you don't need the ORDER BY. Move the ORDER BY outside of the parentheses and you should be fine. SQL Server doesn't need custid sorted in...

When you pass in the result as the example given by NPeeters, SQL Server is going to treat the whole result as a single string. It won't break it down...

Did anyone change it using the Server Network Utility?

K. Brian Kelley

http://www.truthsolutions.com/

Author: Start to Finish Guide to SQL Server Performance Monitoring

http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1