Here's a simple SQL to give you locking information.
The SQL tells you what resource type you are using, the object name, lock request mode, lock status, and also the calling program's name.
And all this from a simple query on sysprocesses, and syslockinfo!
One of the issues you'll face with SQL Server is blocking which is caused by other processes that are holding locks on objects. Until the locks are removed on an object the next process will wait before proceeding. This is a common process that runs within SQL Server to ensure data integrity, but depending on how transactions are run this can cause some issues. Are there ways to get around blocking by using different indexes to cover the queries that may be running?