We have switched to using a hosted (dedicated) server for our databases and
websites. I tend to use SQL mainly via my Visual Studio Prof server explorer.
I have an MSDN Prof license so we only pay for SQL WOrkgroup on the hosted
server and this does not permit SP debugging. What is the best way for me to
set things up so that I can debug stored procedures and take advantage of the
other features of SQL? We need to keep a public licensed version on the
server to serve out public websites but I guess I could upgrade this to
Standard or install my MDSN copy alongside it? Or I could presumably install
the MSDN developer / standard verion on my workstation here, but would it
then let me debug databases on the remote server? Any advice on best setups
for this configuration would be much appreciated.
Thanks, Neil

SageNeil (neilryder (AT) yahoo (DOT) com) writes:
I would not expect it be possible for you run the SQL debugger on the
remote server, with less than you log in on the remote box, and run
Mgmt Studio there. (Provided that you have SQL 2008, that is.)

For debugging to work, SQL Server needs to be able to write back to your
machine and have permission to do so. It would be some hassle to set that
up and open holes in firewalls. The port is 135, RPC, certainly not one
to treat casually.

Way back in SQL 2000 days, I used the debugger occasionally, but eventually
I realised that I spent more time on getting it to work than I saved by
using it. Today, I do all my SQL debugging through PRINT and SELECT.

--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx