Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Sitka
Aged Yak Warrior
571 Posts |
 Posted - 2008-07-11 : 16:47:36
|
I was wondering how some of you might respond to this individuals plea for help. I tried but couldn't make sense of what he/she was asking. quote:
I haven't noticed many posts on the web regarding SQL 2005 Standard edition and debugging T-SQL code so I decided to post here in the hope someone can offer me good advice.About 6 months ago I purchased SQL 2005 Standard with 50 User cals (cost a small fortune but that is beside the point). A situation has just arisen where we need to debug a rather large T-SQL procedure and I began attempting this at 3:00pm today (it's now 9:30 pm and I'm still going). I searched the net and followed all the posts but when I opened a stored procedure in Visual studio, the set break point option was grayed out. After many hours of messing around, I found a small number of articles that state I can not debug SQL in my copy of Visual Studio and I need the PRO version.I have several questions about this so here goes:1: Why can't I debug T-SQL in the version of Visual Studio that was supplied with SQL Standard 2005? Wouldn’t this make sense?2: If I am not able to debug in the supplied version of VS 2005, why can’t I find more posts about it online? It's like no one has ever tried to debug a T-SQL SP in SQL 2005 and or tried to fix it when they couldn't.3: Also, if this is the case, Why did MS only include this functionality in the most advanced version of Visual Studio 2005 when debugging code is considered core functionality? 4: Wasn't debugging standard functionality in all earlier versions of SQL?4: Where could I have found this information to prevent this situation arising before I made my purchase?5: How can I legally fix this problem without spending $550 on a copy of Visual Studio Pro?Any help you guys can offer me would be greatly appreciated. I am very frustrated about this situation and my manager will be even more frustrated with me when I tell him how I messed up.Thanks
I started to reply to 1. with"SQL 2005 standard does not come supplied with Visual Studio they are separate products"then froze up.But it did get my thinking of T-SQL debugging, does that notion even make any sense. How would it help?"it's definitely useless and maybe harmful". |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2008-07-11 : 17:35:38
|
| Does anyone actually use the SQL debugger? I never have.CODO ERGO SUM |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-07-11 : 17:43:50
|
| My developers are constantly asking me for permissions to use it. It requires sysadmin! I tell them no, so they setup their own environments and ask me for the backups. lolTara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
Sitka
Aged Yak Warrior
571 Posts |
Posted - 2008-07-14 : 08:54:24
|
originally the question was on MSDN Forums. Now I can't find it again.quote:
Does anyone actually use the SQL debugger? I never have.
me neither, probably why I couldn't answer the questions. But that got me paranoid about missing out on something, had to check in here for a little reality."it's definitely useless and maybe harmful". |
|
|
|
|
|
|
What is T-SQL debugging?