| Author |
Topic |
|
philld
Starting Member
6 Posts |
 Posted - 2008-06-24 : 18:48:31
|
| This is my first post on the board so I would like to say hi to everyone before I begin my problem.I am in a situation where I need to debug a very large T-SQL stored procedure and have just discovered that I can't.I run SQL 2005 Standard edition with the default copy of Visual studio that ships with the product.I have followed the instructions written in many posts on how to debug an SP in Visual studio 2005 but it doesn't work. When I attempt to add a break point to the T_SQL code, the breakpoint option is grayed out.After some research, I have discovered that I cannot debug T-SQL code with the copy of Visual studio that ships with SQL (hopefully I am wrong).If I am right then I have a major problem with this situation. I have just got through paying $8,000 for a copy of SQL server Standard 2005 with 50 user cals and I find I have to pay extra to do something which was standard functionality in a previous version?I am shocked that after searching the web, I do not see 1 complaint to Microsoft about this functionality. Am, I crazy or does this seem scandalous?I don’t understand how in a previous version, you would be allowed to debug code (even in standard version from what I have been told) but yet in the new version, they remove this and make you pay extra for what is really core functionality.Someone please, please tell me I am wrong. What I don’t seem to understand is how so many users run the professional edition and I don't see hardly any posts with users running the STD edition.I even did some comparison research on MSDN regarding the different versions of SQL and did not find the debug feature listed as being in 1 version vs. another.So please can somebody help me understand what is going on.Thanks |
|
|
philld
Starting Member
6 Posts |
Posted - 2008-06-24 : 19:39:59
|
| The most infuriating part about this is that the breakpoint option is available, but grayed out. Why would this be the case if the version I have cannot debug T-SQL code? If it can’t do it then why tease that it can? |
 |
|
|
philld
Starting Member
6 Posts |
Posted - 2008-06-24 : 19:45:57
|
| Hello Again,So I have been doing some more reading and it appears I am correct that it will not work. So my question to all of you SQL users is....1: Does anyone else have a problem with this situation? That this feature is only available in the pro version when it was previously available in all versions?2: Have I fallen into a clever trap set by Microsoft, an inexperienced user making an informed decision?3: How would I have known to get the pro version? The info to make this decision is just not readily available. How would I know the Standard edition wouldn't allow you to debug? That seems like basic functionality.4: How can I legally fix this problem without having to buy a $550 copy of Visual Studio 2005 Pro? |
|
|
|
philld
Starting Member
6 Posts |
Posted - 2008-06-25 : 07:52:32
|
| Does No one have any opinions on this? If I'm being stupid, please tell me. |
|
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2008-06-25 : 09:05:45
|
| home grown effort.....break the code down into smaller parts and test each bit in-line in QA.I haven't had to debug procedures via the official debug method, but usually running snippets via QA and building up more data on each iteration is a reasonable substitute.you could also put in some "I am here" style commands and output some variables to a text file usng the likes of the xp_cmdshell stored procedure. |
|
|
|
philld
Starting Member
6 Posts |
Posted - 2008-06-25 : 09:22:28
|
| Thanks for your suggestion. The code I am trying to debug is over 20,000 lines long, it was written by a developer who no longer works for us. I have managed to locate a trial version of VS 2005 PRO and are downloading it right now. |
|
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2008-06-26 : 07:24:01
|
| Aha the best type of code.....long, tedious and of unknown quality. |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-06-26 : 07:29:20
|
| and situation would become much more worse if you dont have any comments in it. |
|
|
|
philld
Starting Member
6 Posts |
Posted - 2008-06-26 : 07:52:58
|
| I would say the comments to code ratio is about 1:200 and the usefulness of the comments are about 2/10. |
|
|
|
|
SQL 2005 Standard Won't debug?