Thanks all. I think I will start using VS.NET to be able to group stored procedures by functionality.

I did on both client and server but it was the permissions issue that was preventing me from using the debugger properly.

I apologize for the delayed reply Barsuk. I did get it to work but only after doing the following:

1. Applying SQL Server 2000 Service Pack 4 to both client and...

I have administrative access on both machines. Added TCP ports 445 and 135. Added Query Analyzer to the Exceptions list. Shouldn't matter anyway cause I have the firewall turned off....

Found this in the server application log:

Event Type: Error

Event Source: SQLDebugging98

Event Category: None

Event ID: 1

Date:  9/26/2005

Time:  4:33:19 PM

User:  N/A

Computer: SED-SERVER

Description:

SQL Server is running as 'SED-SERVER\Administrator' and cannot connect to the debugger on machine 'SIS2XPTEST' (error = 0x80070005 Access...

No favourable results. As per above, I did open a debug session between server and client and still could not debug....at least to be able to step through the stored...

I started a debugging session on my client and ran the following (XP firewall disabled):

netstat -an > netstat.txt

from the command line.

The only reference to port 135 was:

 TCP    0.0.0.0:135            0.0.0.0:0              LISTENING

Is this...

I thought that SP4 inlcuded "hotfix 944". Even if I applied SQL Server 2000 SP4 to both the server and client, do I still need to apply the fix? Where...

I am using the sa username and password to connect to the database instance? Do I still need to grant permissions on sp_sdidebug on the master db on the server?...

On server or client?

SP4 installed on both server and client. sqldbreg2.exe added to client personal firewall exceptions list and port 135. Still cannot remotely debug. Any other things to check?

I tired everything as stated in BOL and still nothing seems to work. Any further suggestions?

After changing to the code above, the resulting log file entry was:

You entered mission ID BKSF05-252. If you see any errors below, please check

the existence of the files manually or...

I apologize, the SQL Server is running SP3a. I will check with BOL.

Yes, the filenames match exactly.