Your code seems to work correctly.

I've tested your code (in tempdb) with

DECLARE @ProjectID int

DECLARE @TimeEntryStart datetime

DECLARE @TimeEntryEnd datetime

DECLARE @TimeEntryUserID int

SET @ProjectID=35

SET @TimeEntryStart=convert(datetime,'2008-04-14 02:30:00.000')/*RETURNS 1*/

SET @TimeEntryStart=getdate()/*returns NULL*/

SET @TimeEntryEnd=NULL

SET @TimeEntryUserID=1035

SELECT [tempdb].[dbo].[f_TimeEntryOverlap]

(@ProjectID, @TimeEntryStart,...

I guess so. You can find sp_who2 in the master database and it is marked as system.

try Me.TabControlRiskForm.Pages(1).enabled = false

instead of

Me.TabControlRiskForm.Pages(1).Locked = True

The stored procedure calls another package?

Have you added some debugging routines in the package to see if it actually executes?

I would create a small program outside of sql server that does this. (datasets in .NET?)

You could also try to store the outputs in temporary tables.

For text-files you might consider...

With the stored procedure sp_who2 you can see which connection is blocked by another connection. Then you could kill the offending connection (beware of the rollback).

Current locks: sp_lock

It might be solved by increasing the mem to leave area to 512mb instead of the default 128mb.

-g 512

Usually the recovery time is less than 1 minute, undo operations excluded.

Are there any long running transactions on the database?

Does uid.test_sp exist in the database NorthWind? And does uid has execute permissions on uid.test_sp?

Have a look at

http://www.sqlservercentral.com/articles/DTS/dtsandglobalvariables/2266/

There they assign values to global variables.

Wow, megajoins.

Do the joinable fields used in the query have an index? (the id fields)

Do the queryfilter fields have an index?

A:

Perhaps an index on T1.OWNER_EMP_ID and an index on...

If it needs to be clustered, always add the "clustered". Defaults can change over time.

You could look for some spacemonitoring-scripts.

A basic loop across the tables and

the stored procedure sp_spaceused might work also.

*edit*

have a look at http://www.sqlservercentral.com/scripts/tables/62545/

There is the deny right that overrules allow. If an user is member of a role which has deny update on table X, the user can't update it even when...

Doesn't AWE require fixed memory instead of dynamic allocating?

Up to date with servicepacks (sp4 has an AWE bug fixed by a hotfix)