March 7, 2008 at 2:29 pm
I'm an inexperienced DBA and have a request from developers to install Visual Studio 2005 Debugging components on SQL 2005 servers.
Is this a good practice?
How do you get just the debugging components from the installation or do you have to install all of VS 2005?
We have both a 32 bit SQL 2005 server and a 64 bit SQL 2005 cluster, how friendly is VS 2005 to be installed on each of these platforms?
From http://msdn2.microsoft.com/en-us/vstudio/aa700921.aspx see that all do debugging local but Pro and Team have remote what does that really mean?
March 7, 2008 at 3:10 pm
I believe our developers install the full product on their workstations and use it from there. they use VS for DB Pros
March 7, 2008 at 3:53 pm
the vs debugging package is safe but should be placed on development servers only. i'd personally keep them off test servers also (since i think test should mimic production as closely as possible) but that's up to you and your policy makers.
remote debugging let's the developers use the debug environment within visual studio and step though sql scripts/procedures line-by-line and inspect local variables just like any other language.
the remote debugger installer is already on your ss2k5 box. here's how to install it: http://msdn2.microsoft.com/en-us/library/bt727f1t(VS.80).aspx
March 8, 2008 at 10:59 am
Thanks, the link http://msdn2.microsoft.com/en-us/library/bt727f1t(VS.80).aspx is very helpful.
I've checked and they have VS 2005 installed, with debugging on the Dev server. I think this all came about because a consultant did some work on the training server 6 months ago and the developers now have to try and figure it out, dont' know why the work was not done on the dev server. But good recommendations from everyone to keep the debug off the production cluster.
Thanks again
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply