default database for opening a .sql file?

I am using SQL Server Management Studio. Whenever I open a .sql file, it
does 2 annoying things:
1) prompts me to connect, yet again.
2) sets the database drop down to master again.
The second one, in particular, is really annoying. Is there a way to change
the database that it connects to when I open a .sql file?
Note: setting the default database for the server worked for windows created
with "New Query" but not for opening .sql files.
Heh, 2 seconds after posting I stumble across it. When it prompts me to
connect, there is an Options button. I clicked it and on the Connection
Properties tab it had the same "connect to database" dropdown that I used to
set the default for new query windows. Now whenever I open a .sql file it
goes to the right database.
"Adam J. Schaff" <aschaff@.cascodev.com> wrote in message
news:%23dCE6D4IHHA.4928@.TK2MSFTNGP06.phx.gbl...
>I am using SQL Server Management Studio. Whenever I open a .sql file, it
>does 2 annoying things:
> 1) prompts me to connect, yet again.
> 2) sets the database drop down to master again.
> The second one, in particular, is really annoying. Is there a way to
> change the database that it connects to when I open a .sql file?
> Note: setting the default database for the server worked for windows
> created with "New Query" but not for opening .sql files.
>
|||>I am using SQL Server Management Studio. Whenever I open a .sql file, it
>does 2 annoying things:
> 1) prompts me to connect, yet again.
SQL Server 2005 Service Pack 2 will fix this problem. We just released a
December CTP that has this improvement and many more.
http://www.microsoft.com/downloads/details.aspx?FamilyID=d2da6579-d49c-4b25-8f8a-79d14145500d&DisplayLang=en
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
"Adam J. Schaff" <aschaff@.cascodev.com> wrote in message
news:%23dCE6D4IHHA.4928@.TK2MSFTNGP06.phx.gbl...
>I am using SQL Server Management Studio. Whenever I open a .sql file, it
>does 2 annoying things:
> 1) prompts me to connect, yet again.
> 2) sets the database drop down to master again.
> The second one, in particular, is really annoying. Is there a way to
> change the database that it connects to when I open a .sql file?
> Note: setting the default database for the server worked for windows
> created with "New Query" but not for opening .sql files.
>

Default cube view in SSMS?

Hi,

When browsing a cube in management studio, is there a way set up default value in PivotTable?

Let’s say the cube has 20 dimensions and 10 measures, but user see 2 dimensions and one measure more often; when open a cube, can SSMS just show the default view (2 dimensions and one measure

Thanks in advance.
You can create a perspective with just the 2 dimensions and the measure more used. However, SSMS nor Excel will use one as the default (I think). Of course, if you a Pivot Table for the new perspective is just a question of refreshing that PT.|||
Thank you very much Tiago, your information is very helpful.
I really appropriated.

|||

SSMS is not a tool for end user.

If you, as administrator, want to see some predefined MDX queries you constuct it once then intercept the MDX with profiler and save the MDX in file. Then you can call those MDX queries in SSMS every time you want.

Debugging TSQL Stored Procedures

Running SQL Server Express is there a way to debug TSQL stored procedures?I also have Visual Studio .NET 2003, can I use it to debug the TSQL stored procedures?

Thanks in advance,

Mark

No you need VS 2005 to debug SQL 2005.|||T-SQL Stored Procedure in 2005 can only be done with VSS 2005? Aargh

... I agree, this is a step backawards. Looking at my machien, I see

our company base install has included VSS, but it seems only for

Integration Services, Analysis Services and Reporting Services.

What do I need to do to get it to include the SQL 'component' into VSS?|||

I think you mis-read Euan's post, he said you need VS 2005, as in Visual Studio. Only one "S"; different that VSS for Visual Source Safe. Different thing altogether.

Mike

|||

I know ... you under-estimate the power of the typo and the rushing poster :-)

I was rushing the post, and didn't check what I was typing too clearly - a bad habit! I do know (and have used) Visual Source Safe ... and do have VS 2005 installed.

Now I just need to understand what I need to do to get it to open the SQL solution I have created - when I try to open projects, the extensions listed cover Integration Services, etc. etc. but not SQL project.

Thanks for trying to help me back onto the path - and again, sorry for the mistaken acronyms...

|||If you only have the BI Projects then you just have the BI version of VS, you need the Pro SKU or higher for SQL Projects.|||

Euan Garden wrote:

If you only have the BI Projects then you

just have the BI version of VS, you need the Pro SKU or higher for SQL

Projects.

Thanks Euan. Going to arrange that now.

Debugging Stored Procedures with Visual Studio.net has stopped working

Hi, I used to be able to debug stored procedures via Visual Studio.net 2003. However, this has stopped working. It does not produce an error just simply doesn't work anymore i.e. the breakpoints are by-passed.
I have the correct settings in the Debug configuration section. If any-one knows how to rectify this your help would be appreciated.
I have thought about re-installing the remote debugging functionality on the server. However, our Visual Studio.net discs are with a developer who is away at present.

Thanks in advance
LeeIf any-one else has the same problem, we've solved it. Here's how and why it happened.

We installed Service pack 3 of SQL server and overlooked some of the release notes. This installation was the culprit. To get debugging back working again we needed to execute the statement.

sp_sdidebug legacy_on

via Query Analyzer on our sql server.

Cheers
Lee|||Hi, i try to debug a store procedure in SQL Server. I do an example.
1.Open Server Explorer.

2.Under the Servers node in Server Explorer, expand the SQL Server machine name, expand the SQL Servers node, expand the SQL Server instance, expand the Northwind database node, and then expand the stored procedures node.

3.Right-click the CustOrderHist stored procedure and then click Step Into Stored Procedure.

4.The Run stored procedure dialog box opens, which lists the parameters of the stored procedure. Type ALFKI as the value for the @.CustomerID input parameter and then click OK.

5.In the Visual Studio design environment, a window opens that displays the text of the stored procedure. The first executable line of the stored procedure is highlighted. Press F11 to step through the stored procedure to completion.

6.In the Output window, the following message is displayed, which indicates successful execution:
The program 'SQL Debugger: T-SQL' has exited with code 0 (0x0)

But in step 5, the first executable line of the stored procedure is not highlighted, so I can't press F11 to step through.

Please help me

debugging stored procedure with SSM studio?

Hi,
I know that it 's possible to debugg stored procedure with VS 2005 and is
there a way to do it with SQL Server Management Studio?
Thanks in adavance,
Laurent
Laurent,
check this link
http://msdn2.microsoft.com/en-us/library/ms241871
Markus
|||Sure, but I would like to work just within SQL server Management Studio.
<m.bohse@.quest-consultants.com> a crit dans le message de news:
1132055397.773192.152280@.z14g2000cwz.googlegroups. com...
> Laurent,
> check this link
> http://msdn2.microsoft.com/en-us/library/ms241871
> Markus
>

Debugging SQL Server 2005 Stored Proc with Visual Studio 2005

Hello,

we have a SQL server 2005 with Visual studio Prof. 2005 in the

employment.

The debuggers function only in Visual studio correctly, as long as no

code on the SQL server must be implemented.

If a BREAK POINT in a Stored Procedure is set, this is not activated,

since this cannot be bound.

Does someone know, what it lies and can like one it eliminate?

Thank you for your assistance in advance.

Yours sincerely

Big_Ben_31

---

This entry was translated automatically with the translation

service babel.altavista.com from the German into English.

I will have to ask the obvious question about your setup. Have you ensured that it is complete? The new topics in BOL and MSDN describe the steps in details including troubleshooting ones. Please start with the links below:

http://msdn2.microsoft.com/en-us/library/kkyhd4yb.aspx

http://msdn2.microsoft.com/en-us/library/s4sszxst.aspx

Debugging SQL Server 2005 Stored Proc with Visual Studio 2005

Hi all,

I have a big ol' stored proc (about 6,000 lines), written in T-SQL. I want to debug this stored proc using something other than a bunch of PRINT statements. I tried using the Visual Studio debugger (Server Explorer - Database - Stored Proc - "Step Into Stored Procedure"), but this is behaving erratically.
The "Current statement" yellow cursor is rarely on the line that is currently being executed. It is usually between 2 and 100 lines above the actual current statement. It seems that the further down the code I get, the bigger the distance (in lines) between the yellow cursor and the actual current statement. Maybe something related to comments or multi-line statements?
I have heard of a similar problem with older versions of Visual C++ related to line feeds and return carriages (CR, LF vs. CRLF) but this doesn't seem to be the problem.
Has anyone had similar problems?

Thank you,

Vince

Might be experiencing something similar. I am used to working in SQL Server. I create my stored procedures in the query editor in SQL Server 2005. Sometimes I want to debug the procedure, so I have to go into VS, open up the object explorer, make sure that the debugging setting it on, find the stored procedure and step into it.

Well... I am seeiing erradic behavior as well; about 75% of the time, the yellow cursor disappears. Like right now... It thinks it is still debugging but the cursor is gone and the only option available for debuuging is to stop debugging. oh, and the task bar says its running... I can't seem to find out why this is happening, since I am seeing no other reports of this happening to people. Your post is the closest so far. Did you resolve your problem?

|||

While I dont have an exact remedy for you, this is not that uncommon. I have used the tools (both VS and SQL) for about two years now since the first public beta whenever that was :)...

I have seen this behavior over the months several times, but not as of late. It usually had to do with referring to old versions of code. Make sure you are referencing the correct Server/DB/Proc and refresh then debug. And check you DB connection properties.

Hope this helps,

Derek

|||

I do think it does have something to do with saving the procedure using Visual Studio 2005. It *seems* that if I save it to a project and try debugging it I have less problems...

This leads me to ask about best practices for managing T-SQL and databases. I'm sure my circumstances are not uncommon; I have a single, rather large database that is utilized by multiple applications (many of which can be in a beta development stage requireing frequent changes to the database). I was to implement source control practices for myself and my teams and I favor subversion for source control. When I create a new application, or upgrade an application to VS 2005, how can I best set up my database for change management?

I have the impression that Microsoft wants me to change the way that I work to handle my database, but it is very unclear HOW they want me to work with their products. Sometimes I write stored procedures that are not part of a single application, but that are used by multiple applications - both web and desktop. So, in this case would it be best to create some kind of database project that is seperate from my applications? And if so, how could I organize it to manage change and quality? Ugh.

|||

Hi Ryan,

I think you will find SQL Server source control integration a good first step towards acommplishing change management in the database. There have been several 3rd party attempts at the problem of managing change in the database, but those I have used were fair at best.

In general, your database can and should be a seperate entity for all but the most simplest projects aka "mom and pop websites/apps". My dev. team uses VSS (not used Team System so you may want to check into that as well) and each project is self-contained in the repository. We do not mix and match projects of different types. So maybe very simplistically speaking your VSS repository structure...

FRONTEND

-Web

-Desktop

MIDDLETIER

-Classes

-Web Services

DATABASE

-Database X

--Stored Procs

--Functions

--Triggers

DML

DDL

-Database Y

-Database Z

etc...you may enjoy a recent post on my blog regarding the usage of mangement studio's VSS integration...

http://derekcomingore.iuplog.com/default.asp?item=167168

Derek

Debugging SPs in SQL Server 2005

Hi,
Are there any new feature for debugging non-CLR SPs in Management Studio? I
couldn't find anything in BOL.
Thanks in advance,
LeilaThere's no debugger of TSQL code in Management Studio. You have to use Visua
l Studio for that.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Leila" <Leilas@.hotpop.com> wrote in message news:%23ZJkGf4GGHA.3000@.TK2MSFTNGP14.phx.gbl..
.
> Hi,
> Are there any new feature for debugging non-CLR SPs in Management Studio?
I
> couldn't find anything in BOL.
> Thanks in advance,
> Leila
>

Debugging SPs in SQL Server 2005

Hi,
Are there any new feature for debugging non-CLR SPs in Management Studio? I
couldn't find anything in BOL.
Thanks in advance,
Leila
There's no debugger of TSQL code in Management Studio. You have to use Visual Studio for that.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Leila" <Leilas@.hotpop.com> wrote in message news:%23ZJkGf4GGHA.3000@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Are there any new feature for debugging non-CLR SPs in Management Studio? I
> couldn't find anything in BOL.
> Thanks in advance,
> Leila
>

Debugging SPs in SQL Server 2005

Hi,
Are there any new feature for debugging non-CLR SPs in Management Studio? I
couldn't find anything in BOL.
Thanks in advance,
LeilaThere's no debugger of TSQL code in Management Studio. You have to use Visual Studio for that.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Leila" <Leilas@.hotpop.com> wrote in message news:%23ZJkGf4GGHA.3000@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Are there any new feature for debugging non-CLR SPs in Management Studio? I
> couldn't find anything in BOL.
> Thanks in advance,
> Leila
>

Debugging SPs in SQL Server 2005

Hi,
Are there any new feature for debugging non-CLR SPs in Management Studio? I
couldn't find anything in BOL.
Thanks in advance,
LeilaThere's no debugger of TSQL code in Management Studio. You have to use Visua
l Studio for that.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Leila" <Leilas@.hotpop.com> wrote in message news:%23ZJkGf4GGHA.3000@.TK2MSFTNGP14.phx.gbl...

> Hi,
> Are there any new feature for debugging non-CLR SPs in Management Studio?
I
> couldn't find anything in BOL.
> Thanks in advance,
> Leila
>

Debugging or a parody on it?

Hi, I am new here.

I tried to debug stored procedures in the Visual Studio and you know… it was a real shock. Like going in time 10 or 20 years back.

The stored procedures I deal with contain a lot of @.tab and #tab, but it appears that I can not evaluate the values of these objects! The only type of object I can evaluate is a variable. But SQL is designed for the table data, right? So the most important type of data is not accessible!

How can I understand, what records have been affected by Update or inserted by Insert? Using prints or debug selects? Is it an era of FORTRAN or ALGOL?

To make it worse, to enter a debugger, I need to provide values of all parameters. It might be simple for the outermost procedure, but for inner stored procs, and where some parameters are some short-living identity values of some records, created in a transaction, it is very difficult to prepare all conditions to make a correct run.

So my question is, may be I had overlooked something? Is it a real debugger or just a joke from Microsoft? Sorry, but I am really angry after wasting a lot of time last week on it.

If you want to trace changes on the record level it might be better to enable auditing in SQL Server and examine the log files with Profiler. Here is one article about enabling auditing in SQL 2000:

http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx

|||

Thank you. But agree with me, it is far from simplicity of the debugging process we have with C# code.

Ok, I'll google if there any 3rd party tools.

Debugging In Business Intelligence Studio

I've been trying to get debugging working in BIS, but I can't seem to do it. If I am using the full blown version of Visual Studio I don't have any problems. I have read that TSQL debugging is limited to Visual Studio Professional or higher, however, there is no indication where Business Intelligence Studio is in the Visual Studio continuum. I don't know if it is considered lower or higher than Professional.

Anyway, if it is possible to use BIS for debuggin TSQL, then how does one go about doing it? I've have been competely unsuccessful to date. I have attempted to install and use the Remote Debugger, but that hasn't worked for me. So, I'm left to conclude that BIS doesn't support TSQL debugging.

Microsoft, Can you please give the final word here? This would be very nice to know one way or another.

Thanks,

DCB99

Hi dcb99,

The 'official' word (but not final) is the material you read with respect to TSQL debugging being limited to VS Professional (or higher) is correct. BI or No BI plays no part in the equation. A debugger (not the TSQL debugger of years passed) ships with VS Pro and above.

The final word is; we have it on our plate, for the next shipping version of SQL Server to get a robust debugging experience baked into the DBA - BIS experience.

Terrence Nevins

SQL Server Program Manager

|||

Terrance,

Thanks for your response. However, it doesn't quite answer my question I don't think. If I do not install a version of Visual Studio apart from installing SQL Server 2005, does BIS support debugging? I guess I'm reading that your email says it does not support debugging.

Thanks in advance.

dcb99

Debugging In Business Intelligence Studio

I've been trying to get debugging working in BIS, but I can't seem to do it. If I am using the full blown version of Visual Studio I don't have any problems. I have read that TSQL debugging is limited to Visual Studio Professional or higher, however, there is no indication where Business Intelligence Studio is in the Visual Studio continuum. I don't know if it is considered lower or higher than Professional.

Anyway, if it is possible to use BIS for debuggin TSQL, then how does one go about doing it? I've have been competely unsuccessful to date. I have attempted to install and use the Remote Debugger, but that hasn't worked for me. So, I'm left to conclude that BIS doesn't support TSQL debugging.

Microsoft, Can you please give the final word here? This would be very nice to know one way or another.

Thanks,

DCB99

Hi dcb99,

The 'official' word (but not final) is the material you read with respect to TSQL debugging being limited to VS Professional (or higher) is correct. BI or No BI plays no part in the equation. A debugger (not the TSQL debugger of years passed) ships with VS Pro and above.

The final word is; we have it on our plate, for the next shipping version of SQL Server to get a robust debugging experience baked into the DBA - BIS experience.

Terrence Nevins

SQL Server Program Manager

|||

Terrance,

Thanks for your response. However, it doesn't quite answer my question I don't think. If I do not install a version of Visual Studio apart from installing SQL Server 2005, does BIS support debugging? I guess I'm reading that your email says it does not support debugging.

Thanks in advance.

dcb99

Debug Stored Procedure - Visual Studio 2003 - Possible?

I can not step into stored procedures that I have created using the VS IDE.
This is the error message that I receive when attempting to debug the stored
procedure:
"Cannot debug stored procedures because the SQL Sserver database is not
setup correctly or user does not have permission to execute
master.sp_sdidebug. Run SQL Server setup or contact database admininstrator."
I am the database administrator! I have sp_sdidebug set to legacy_on. Not
sure what else to try. My boss does not want to pay for SQL Server Dev
edition, so I would really like to get this working.
Any suggestions will be greatly appreciated.
Thank you,
Michael Garcia
If your boss doesn't want to shell out $49 for the Developer Edition,
perhaps you could helpfully point out that many experienced people
have spent countless hours attempting to get debugging working from
the VS IDE, and have failed to do so. To obtain actual evidence, do a
google groups search on the topic and read threads from other
frustrated users. Ask him to consider how much he is paying you by the
hour, counting benefits, and then ask him to do the math. Caveat --
you can't use the Developer edition as a production server, but it's
indispensable if you care anything about creating a secure and robust
database app.
--Mary
On Tue, 19 Oct 2004 09:19:03 -0700, "Mike"
<Mike@.discussions.microsoft.com> wrote:

>I can not step into stored procedures that I have created using the VS IDE.
>This is the error message that I receive when attempting to debug the stored
>procedure:
>"Cannot debug stored procedures because the SQL Sserver database is not
>setup correctly or user does not have permission to execute
>master.sp_sdidebug. Run SQL Server setup or contact database admininstrator."
>I am the database administrator! I have sp_sdidebug set to legacy_on. Not
>sure what else to try. My boss does not want to pay for SQL Server Dev
>edition, so I would really like to get this working.
>Any suggestions will be greatly appreciated.
>Thank you,
>Michael Garcia
|||Your point is noted; however, I got it working yesterday.
For all those that are having problems getting debugging working in VS for
MSDE try this!
First find the file mssdi98.dll in C:\Program Files\Microsoft Visual Studio
..NET 2003\sqlserver
Copy it to the binn directory of your MSDE instance.
Second run dcomcnfg.
Component Services -> Computers -> My Computer
Select properties for My Computer. Go to the Default COM Security tab.
Edit the default settings for access permissions. Add yourself and system
if it is not there and make sure allow is checked.
This got it working on both my systems.
Good luck!
Michael Garcia
"Mary Chipman" wrote:

> If your boss doesn't want to shell out $49 for the Developer Edition,
> perhaps you could helpfully point out that many experienced people
> have spent countless hours attempting to get debugging working from
> the VS IDE, and have failed to do so. To obtain actual evidence, do a
> google groups search on the topic and read threads from other
> frustrated users. Ask him to consider how much he is paying you by the
> hour, counting benefits, and then ask him to do the math. Caveat --
> you can't use the Developer edition as a production server, but it's
> indispensable if you care anything about creating a secure and robust
> database app.
> --Mary
|||You're lucky -- others have hit the wall configuring DCOM and dealing
with SP2 issues. Please have your boss get you the Dev edition anyway
-- there are many things you simply cannot do from the VS IDE unless
you want to write a lot of script.
--Mary
On Wed, 20 Oct 2004 09:39:02 -0700, "Mike"
<Mike@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Your point is noted; however, I got it working yesterday.
>For all those that are having problems getting debugging working in VS for
>MSDE try this!
>First find the file mssdi98.dll in C:\Program Files\Microsoft Visual Studio
>.NET 2003\sqlserver
>Copy it to the binn directory of your MSDE instance.
>Second run dcomcnfg.
>Component Services -> Computers -> My Computer
>Select properties for My Computer. Go to the Default COM Security tab.
>Edit the default settings for access permissions. Add yourself and system
>if it is not there and make sure allow is checked.
>This got it working on both my systems.
>Good luck!
>Michael Garcia
>"Mary Chipman" wrote:

Debug Sql Server 2005 Stored Procedure in Sql Server Management St

I am trying to figure out how to debug a Stored Procedure (SP) from Sql
Server Management Studio. Like in Query Analyzer in Sql Server 2000, where I
could right click an SP and then click debug on it will let me debug the SP.
Of course, I would execute sp_sdidebug 'legacy_on' before doing that.
In Sql Server Management Studio I do not see an option for debugging an SP
when I right click the SP nor do I see debugging SP option in the menu. I
read BOL, and it mentions to run sp_sdidebug. I tried to run sp_sdidebug but
I get "Could not find stored procedure sp_sdidebug". I tried this step in
master DB, user DB, and msdb but all give me the same error.
The user who is trying to debug the SP is already a member of symin role.
I can debug the SP from Visual Studio 2005, but I would like the same
capability I had in Sql 2000 to be in SMSS. Besides, the Results windows in
SMSS gives me resultset, which I cannot get from the Visual Studio, if I use
VS for debugging.
I have also read that many of the features, such as debugging, xp_cmdshell
etc. come disabled by default in SQL 2005, which is okay. But could somebody
tell me how to make the entire Stored Procedure debugging process work from
within SSMS?
Reply appreciated.
Thanks>I am trying to figure out how to debug a Stored Procedure (SP) from Sql
> Server Management Studio.
Can you please post to the SQL Server 2005 newsgroups.
http://www.aspfaq.com/sql2005/show.asp?id=1

Debug sp from Business Intelligence Dev Studio?

Is there a way to debug SQL Server 2005 stored procedures from within BI
Studio? I don't see any way to do it, but may be missing something.
I can do it from a VS 2005, but some systems don't have that installed.
Thanks,
TomHi ,
I don't think you can debug .NET sp without VS 2005 Pro or Team suite. You
should be able to debug a TSQL sp without VS (but I haven't checked) as it
was there as a feature in SQL 2000
kind regards
Greg O
--
Looking to use CLR in SQL 2005. Try some pre-build CLR Functions and SP
AGS SQL 2005 Utilities, over 20+ functions
http://www.ag-software.com/?tabid=38
"TomT" <tomt@.newsgroup.nospam> wrote in message
news:B633E6CF-F829-4A63-A2AA-8C5C219E75A0@.microsoft.com...
> Is there a way to debug SQL Server 2005 stored procedures from within BI
> Studio? I don't see any way to do it, but may be missing something.
> I can do it from a VS 2005, but some systems don't have that installed.
> Thanks,
> Tom|||I don't think the T-SQL debugger is also there in SSMS.
--
HTH,
SriSamp
Email: srisamp@.gmail.com
Blog: http://blogs.sqlxml.org/srinivassampath
URL: http://www32.brinkster.com/srisamp
"GregO" <grego@.community.nospam> wrote in message
news:ebLSm2y7FHA.3976@.TK2MSFTNGP15.phx.gbl...
> Hi ,
> I don't think you can debug .NET sp without VS 2005 Pro or Team suite.
> You should be able to debug a TSQL sp without VS (but I haven't checked)
> as it was there as a feature in SQL 2000
> kind regards
> Greg O
> --
> Looking to use CLR in SQL 2005. Try some pre-build CLR Functions and SP
> AGS SQL 2005 Utilities, over 20+ functions
> http://www.ag-software.com/?tabid=38
> "TomT" <tomt@.newsgroup.nospam> wrote in message
> news:B633E6CF-F829-4A63-A2AA-8C5C219E75A0@.microsoft.com...
>|||Hello,
I think you need to use Visual Studio 2005 to debug.
You may refer to the following information:
http://www.microsoft.com/technet/co...SQL_101204.mspx
*Q: What kind of debugging options do we have with managed code? Do we have
to attach a debugger to the SQL Server process?
A: Visual Studio 2005 would provide support for debugging Transact SQL and
CLR routines that are registered / running in SQL Server. The debugging in
SQL Server follows per connection model. You can either debug the objects
directly using Visual Studio Server Explorer or attach a client process and
see / debug activities on the connections that client process makes. The
debug engine inside sql server would provide an integrated t-sql / clr
debugging experience.*
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Sophie,
Waht about TSQL debugging?
Greg
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:ywy6NV07FHA.832@.TK2MSFTNGXA02.phx.gbl...
> Hello,
> I think you need to use Visual Studio 2005 to debug.
> You may refer to the following information:
> http://www.microsoft.com/technet/co...SQL_101204.mspx
> *Q: What kind of debugging options do we have with managed code? Do we
> have
> to attach a debugger to the SQL Server process?
> A: Visual Studio 2005 would provide support for debugging Transact SQL and
> CLR routines that are registered / running in SQL Server. The debugging in
> SQL Server follows per connection model. You can either debug the objects
> directly using Visual Studio Server Explorer or attach a client process
> and
> see / debug activities on the connections that client process makes. The
> debug engine inside sql server would provide an integrated t-sql / clr
> debugging experience.*
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||That's what I was afraid of. It seems then that a customer buying SQL Server
2000 can debug sp's via Query Analyzer at no additional cost, but a customer
buying SQL 2005 will have to buy VS2005 to be able to do this.
Hopefully this functionality will be added back in to the product....
"Sophie Guo [MSFT]" wrote:

> Hello,
> I think you need to use Visual Studio 2005 to debug.
> You may refer to the following information:
> http://www.microsoft.com/technet/co...SQL_101204.mspx
> *Q: What kind of debugging options do we have with managed code? Do we hav
e
> to attach a debugger to the SQL Server process?
> A: Visual Studio 2005 would provide support for debugging Transact SQL and
> CLR routines that are registered / running in SQL Server. The debugging in
> SQL Server follows per connection model. You can either debug the objects
> directly using Visual Studio Server Explorer or attach a client process an
d
> see / debug activities on the connections that client process makes. The
> debug engine inside sql server would provide an integrated t-sql / clr
> debugging experience.*
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hello,
I understand your concerns. However, this is how SQL server 2005 is
designed. I suggest that you access the following web site which provide
good information about Debugging in SQL Server 2005:
Demystifying Debugging in SQL Server 2005
http://www.windowsitpro.com/SQLServ.../SQLServer_4775
4.html
How to: Debug a SQL CLR Stored Procedure
http://msdn2.microsoft.com/en-us/library/ms165051.aspx
How to: Enable SQL Server 2005 Debugging
http://msdn2.microsoft.com/en-us/library/s0fk6z6e.aspx
Creating SQL Server 2005 Objects in Managed Code
http://msdn2.microsoft.com/en-us/library/6s0s2at1.aspx
SQL Server 2005 Debugging
http://www.sqljunkies.com/WebLog/ni...08/04/3758.aspx
Note: This response contains a reference to a third party World Wide Web
site. Microsoft is providing this information as a convenience to you.
Microsoft does not control these sites and has not tested any software or
information found on these sites; therefore, Microsoft cannot make any
representations regarding the quality, safety, or suitability of any
software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make
sure that you completely understand the risk before retrieving any software
from the Internet.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Sophie,
Not labour a point but we are talking about TSQL debugging in this part. We
understand CLR debugging is a different matter.
What about TSQL debugging?
kind regards
Greg O
Need to document your databases. Use the first and still the best AGS SQL
Scribe
http://www.ag-software.com
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:0P6LLOB8FHA.832@.TK2MSFTNGXA02.phx.gbl...
> Hello,
> I understand your concerns. However, this is how SQL server 2005 is
> designed. I suggest that you access the following web site which provide
> good information about Debugging in SQL Server 2005:
> Demystifying Debugging in SQL Server 2005
> http://www.windowsitpro.com/SQLServ...y/ms165051.aspx
> How to: Enable SQL Server 2005 Debugging
> http://msdn2.microsoft.com/en-us/library/s0fk6z6e.aspx
> Creating SQL Server 2005 Objects in Managed Code
> http://msdn2.microsoft.com/en-us/library/6s0s2at1.aspx
> SQL Server 2005 Debugging
> http://www.sqljunkies.com/WebLog/ni...08/04/3758.aspx
> Note: This response contains a reference to a third party World Wide Web
> site. Microsoft is providing this information as a convenience to you.
> Microsoft does not control these sites and has not tested any software or
> information found on these sites; therefore, Microsoft cannot make any
> representations regarding the quality, safety, or suitability of any
> software or information found there. There are inherent dangers in the use
> of any software found on the Internet, and Microsoft cautions you to make
> sure that you completely understand the risk before retrieving any
> software
> from the Internet.
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>|||Hello,
Based on my research, I didn't find the debug button in the Server
Management Studio. You can refer to the information on the following
article:
Demystifying Debugging in SQL Server 2005
http://www.windowsitpro.com/SQLServ.../SQLServer_4775
4.html
*To debug a T-SQL stored procedure in SQL Server 2000, you use the Query
Analyzer. You simply right-click the stored procedure and choose Debug. In
SQL Server 2005, SQL Server Management Studio replaces the Query Analyzer.
It's logical to assume that to debug a T-SQL stored procedure in SQL Server
2005, you simply right-click a stored procedure and select Management
Studio's debug feature. Unfortunately, it's not that straightforward. A
debug option is nowhere to be found.
To debug T-SQL stored procedures in SQL Server 2005, you use the Visual
Studio 2005 development environment.*
I suggest that you refer to the information I posted before.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||v-sguo@.online.microsoft.com (Sophie Guo [MSFT]) wrote in
news:eFNPe0B8FHA.832@.TK2MSFTNGXA02.phx.gbl:

> Hello,
> Based on my research, I didn't find the debug button in the Server
> Management Studio. You can refer to the information on the following
> article:
> Demystifying Debugging in SQL Server 2005
> http://www.windowsitpro.com/SQLServ.../47754/SQLServe
r
> _4775 4.html
> *To debug a T-SQL stored procedure in SQL Server 2000, you use the
> Query Analyzer. You simply right-click the stored procedure and choose
> Debug. In SQL Server 2005, SQL Server Management Studio replaces the
> Query Analyzer. It's logical to assume that to debug a T-SQL stored
> procedure in SQL Server 2005, you simply right-click a stored
> procedure and select Management Studio's debug feature. Unfortunately,
> it's not that straightforward. A debug option is nowhere to be found.
> To debug T-SQL stored procedures in SQL Server 2005, you use the
> Visual Studio 2005 development environment.*
>
Yup, regardless if you want to debug sp's based on CLR code or sp's
based on "pure" T-SQL you use Visual Studio 2005. Personally I think it
wasn't the best decision MS has done, but that's the way it is.
Oh BTW, there will be a follow-up article to the one mentioned above. In
this I'll discuss CLR debugging inside SQL Server.
Niels
****************************************
**********
* Niels Berglund
* http://staff.develop.com/nielsb
* nielsb@.no-spam.develop.com
* "A First Look at SQL Server 2005 for Developers"
* http://www.awprofessional.com/title/0321180593
****************************************
**********

debug a stored procedure in SQL Server 2005

Hi everyone!
How can I do to debug a Stored Procedure in SQL Server 2005 from SQL Server
Management Studio? I looked for the Debug... option when I right-clicked the
SP but it seems that in SQL Sever 2005 doesn't not exist.
Thanks.
Jaime Lucci
It's not there; you'll have to use Visual Studio.
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
"Jaime Lucci" <jaimelucci@.hotmail.com> wrote in message
news:%23UcTRTc9FHA.1440@.TK2MSFTNGP12.phx.gbl...
> Hi everyone!
> How can I do to debug a Stored Procedure in SQL Server 2005 from SQL
> Server
> Management Studio? I looked for the Debug... option when I right-clicked
> the
> SP but it seems that in SQL Sever 2005 doesn't not exist.
> Thanks.
> Jaime Lucci
>
|||Hi Jamime,
Microsoft didn't migrate the TSQL debugger into Microsoft SQL Server 2005.
The only way to debug is to use MS VS 2005 Pro or Team Suite
http://www.sqlserver.org.au/blogs/us...o/default.aspx
kind regards
Greg O
Looking to use CLR in SQL 2005. Try some pre-build CLR Functions and SP
AGS SQL 2005 Utilities, over 20+ functions
http://www.ag-software.com/?tabid=38
"Jaime Lucci" <jaimelucci@.hotmail.com> wrote in message
news:%23UcTRTc9FHA.1440@.TK2MSFTNGP12.phx.gbl...
> Hi everyone!
> How can I do to debug a Stored Procedure in SQL Server 2005 from SQL
> Server
> Management Studio? I looked for the Debug... option when I right-clicked
> the
> SP but it seems that in SQL Sever 2005 doesn't not exist.
> Thanks.
> Jaime Lucci
>
|||On Wed, 30 Nov 2005 12:43:15 -0300, Jaime Lucci wrote:

>Hi everyone!
>How can I do to debug a Stored Procedure in SQL Server 2005 from SQL Server
>Management Studio? I looked for the Debug... option when I right-clicked the
>SP but it seems that in SQL Sever 2005 doesn't not exist.
>Thanks.
> Jaime Lucci
>
Hi Jaime,
The debugging function has been removed from SQL Server 2005. You'll
have to use MS Visual Studio.
If you (like me) want to see the T-SQL debugger return to SQL Server,
then vote for this suggestion at (warning, long URL may wrap):
http://lab.msdn.microsoft.com/Produc...ckId=FDBK41174
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||On Thu, 01 Dec 2005 00:11:55 +0100, Hugo Kornelis
<hugo@.pe_NO_rFact.in_SPAM_fo> wrote:
>On Wed, 30 Nov 2005 12:43:15 -0300, Jaime Lucci wrote:
>
>Hi Jaime,
>The debugging function has been removed from SQL Server 2005. You'll
>have to use MS Visual Studio.
>If you (like me) want to see the T-SQL debugger return to SQL Server,
>then vote for this suggestion at (warning, long URL may wrap):
>http://lab.msdn.microsoft.com/Produc...ckId=FDBK41174
Done!
Would you believe, there are places where SQLServer is used with
non-MS middleware and client technologies, from Powerbuilder to
(shudder!) Java and J2EE!? Not to mention stuff like Python ...
And worse yet, there are places where there are DBA and data architect
and similar jobs, that involve SQLServer and not (by default) Visual
Studio! Gasp! But I have been there, time and again!
J.
|||!
> How can I do to debug a Stored Procedure in SQL Server 2005 from SQL
Server
> Management Studio? I looked for the Debug... option when I right-clicked
the
> SP but it seems that in SQL Sever 2005 doesn't not exist.
Does anyone know if the debugging interface is public? That way, we could
finally integrate a debugger in our database development tool :-)
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com
|||On Wed, 30 Nov 2005 15:34:32 -0800, jxstern wrote:

>On Thu, 01 Dec 2005 00:11:55 +0100, Hugo Kornelis
><hugo@.pe_NO_rFact.in_SPAM_fo> wrote:
(snip)

>Done!
Hi J.
Thanks for your vote!
Current standing: 11 votes, average rating 4.91. That works out to 10
votes at rating 5, and one vote (mine <g>) at rating 4.

>Would you believe, there are places where SQLServer is used with
>non-MS middleware and client technologies, from Powerbuilder to
>(shudder!) Java and J2EE!? Not to mention stuff like Python ...
>And worse yet, there are places where there are DBA and data architect
>and similar jobs, that involve SQLServer and not (by default) Visual
>Studio! Gasp! But I have been there, time and again!
Not to mention, places where the expense of acquiring MS Visual Studio
in addition to SQL Server is too high - none of the other features are
needed, and debugging alone isn't enough justification to splash out on
Visual Studio.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)

debug a stored procedure in SQL Server 2005

Hi everyone!
How can I do to debug a Stored Procedure in SQL Server 2005 from SQL Server
Management Studio? I looked for the Debug... option when I right-clicked the
SP but it seems that in SQL Sever 2005 doesn't not exist.
Thanks.
Jaime Lucci
[responding to one newsgroup]
You can't. You can debug T-SQL or SQLCLR procedures from Visual Studio 2005.
Cheers,
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"Jaime Lucci" <jaimelucci@.hotmail.com> wrote in message
news:%23UcTRTc9FHA.1440@.TK2MSFTNGP12.phx.gbl...
> Hi everyone!
> How can I do to debug a Stored Procedure in SQL Server 2005 from SQL
> Server
> Management Studio? I looked for the Debug... option when I right-clicked
> the
> SP but it seems that in SQL Sever 2005 doesn't not exist.
> Thanks.
> Jaime Lucci
>
|||It's not there; you'll have to use Visual Studio.
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
"Jaime Lucci" <jaimelucci@.hotmail.com> wrote in message
news:%23UcTRTc9FHA.1440@.TK2MSFTNGP12.phx.gbl...
> Hi everyone!
> How can I do to debug a Stored Procedure in SQL Server 2005 from SQL
> Server
> Management Studio? I looked for the Debug... option when I right-clicked
> the
> SP but it seems that in SQL Sever 2005 doesn't not exist.
> Thanks.
> Jaime Lucci
>
|||Hi Jamime,
Microsoft didn't migrate the TSQL debugger into Microsoft SQL Server 2005.
The only way to debug is to use MS VS 2005 Pro or Team Suite
http://www.sqlserver.org.au/blogs/us...o/default.aspx
kind regards
Greg O
Looking to use CLR in SQL 2005. Try some pre-build CLR Functions and SP
AGS SQL 2005 Utilities, over 20+ functions
http://www.ag-software.com/?tabid=38
"Jaime Lucci" <jaimelucci@.hotmail.com> wrote in message
news:%23UcTRTc9FHA.1440@.TK2MSFTNGP12.phx.gbl...
> Hi everyone!
> How can I do to debug a Stored Procedure in SQL Server 2005 from SQL
> Server
> Management Studio? I looked for the Debug... option when I right-clicked
> the
> SP but it seems that in SQL Sever 2005 doesn't not exist.
> Thanks.
> Jaime Lucci
>
|||On Wed, 30 Nov 2005 12:43:15 -0300, Jaime Lucci wrote:

>Hi everyone!
>How can I do to debug a Stored Procedure in SQL Server 2005 from SQL Server
>Management Studio? I looked for the Debug... option when I right-clicked the
>SP but it seems that in SQL Sever 2005 doesn't not exist.
>Thanks.
> Jaime Lucci
>
Hi Jaime,
The debugging function has been removed from SQL Server 2005. You'll
have to use MS Visual Studio.
If you (like me) want to see the T-SQL debugger return to SQL Server,
then vote for this suggestion at (warning, long URL may wrap):
http://lab.msdn.microsoft.com/Produc...ckId=FDBK41174
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||On Thu, 01 Dec 2005 00:11:55 +0100, Hugo Kornelis
<hugo@.pe_NO_rFact.in_SPAM_fo> wrote:
>On Wed, 30 Nov 2005 12:43:15 -0300, Jaime Lucci wrote:
>
>Hi Jaime,
>The debugging function has been removed from SQL Server 2005. You'll
>have to use MS Visual Studio.
>If you (like me) want to see the T-SQL debugger return to SQL Server,
>then vote for this suggestion at (warning, long URL may wrap):
>http://lab.msdn.microsoft.com/Produc...ckId=FDBK41174
Done!
Would you believe, there are places where SQLServer is used with
non-MS middleware and client technologies, from Powerbuilder to
(shudder!) Java and J2EE!? Not to mention stuff like Python ...
And worse yet, there are places where there are DBA and data architect
and similar jobs, that involve SQLServer and not (by default) Visual
Studio! Gasp! But I have been there, time and again!
J.
|||!
> How can I do to debug a Stored Procedure in SQL Server 2005 from SQL
Server
> Management Studio? I looked for the Debug... option when I right-clicked
the
> SP but it seems that in SQL Sever 2005 doesn't not exist.
Does anyone know if the debugging interface is public? That way, we could
finally integrate a debugger in our database development tool :-)
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com
|||On Wed, 30 Nov 2005 15:34:32 -0800, jxstern wrote:

>On Thu, 01 Dec 2005 00:11:55 +0100, Hugo Kornelis
><hugo@.pe_NO_rFact.in_SPAM_fo> wrote:
(snip)

>Done!
Hi J.
Thanks for your vote!
Current standing: 11 votes, average rating 4.91. That works out to 10
votes at rating 5, and one vote (mine <g>) at rating 4.

>Would you believe, there are places where SQLServer is used with
>non-MS middleware and client technologies, from Powerbuilder to
>(shudder!) Java and J2EE!? Not to mention stuff like Python ...
>And worse yet, there are places where there are DBA and data architect
>and similar jobs, that involve SQLServer and not (by default) Visual
>Studio! Gasp! But I have been there, time and again!
Not to mention, places where the expense of acquiring MS Visual Studio
in addition to SQL Server is too high - none of the other features are
needed, and debugging alone isn't enough justification to splash out on
Visual Studio.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)

debug a stored procedure in SQL Server 2005

Hi everyone!
How can I do to debug a Stored Procedure in SQL Server 2005 from SQL Server
Management Studio? I looked for the Debug... option when I right-clicked the
SP but it seems that in SQL Sever 2005 doesn't not exist.
Thanks.
Jaime Lucci
It's not there; you'll have to use Visual Studio.
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
"Jaime Lucci" <jaimelucci@.hotmail.com> wrote in message
news:%23UcTRTc9FHA.1440@.TK2MSFTNGP12.phx.gbl...
> Hi everyone!
> How can I do to debug a Stored Procedure in SQL Server 2005 from SQL
> Server
> Management Studio? I looked for the Debug... option when I right-clicked
> the
> SP but it seems that in SQL Sever 2005 doesn't not exist.
> Thanks.
> Jaime Lucci
>
|||Hi Jamime,
Microsoft didn't migrate the TSQL debugger into Microsoft SQL Server 2005.
The only way to debug is to use MS VS 2005 Pro or Team Suite
http://www.sqlserver.org.au/blogs/us...o/default.aspx
kind regards
Greg O
Looking to use CLR in SQL 2005. Try some pre-build CLR Functions and SP
AGS SQL 2005 Utilities, over 20+ functions
http://www.ag-software.com/?tabid=38
"Jaime Lucci" <jaimelucci@.hotmail.com> wrote in message
news:%23UcTRTc9FHA.1440@.TK2MSFTNGP12.phx.gbl...
> Hi everyone!
> How can I do to debug a Stored Procedure in SQL Server 2005 from SQL
> Server
> Management Studio? I looked for the Debug... option when I right-clicked
> the
> SP but it seems that in SQL Sever 2005 doesn't not exist.
> Thanks.
> Jaime Lucci
>
|||On Wed, 30 Nov 2005 12:43:15 -0300, Jaime Lucci wrote:

>Hi everyone!
>How can I do to debug a Stored Procedure in SQL Server 2005 from SQL Server
>Management Studio? I looked for the Debug... option when I right-clicked the
>SP but it seems that in SQL Sever 2005 doesn't not exist.
>Thanks.
> Jaime Lucci
>
Hi Jaime,
The debugging function has been removed from SQL Server 2005. You'll
have to use MS Visual Studio.
If you (like me) want to see the T-SQL debugger return to SQL Server,
then vote for this suggestion at (warning, long URL may wrap):
http://lab.msdn.microsoft.com/Produc...ckId=FDBK41174
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||On Thu, 01 Dec 2005 00:11:55 +0100, Hugo Kornelis
<hugo@.pe_NO_rFact.in_SPAM_fo> wrote:
>On Wed, 30 Nov 2005 12:43:15 -0300, Jaime Lucci wrote:
>
>Hi Jaime,
>The debugging function has been removed from SQL Server 2005. You'll
>have to use MS Visual Studio.
>If you (like me) want to see the T-SQL debugger return to SQL Server,
>then vote for this suggestion at (warning, long URL may wrap):
>http://lab.msdn.microsoft.com/Produc...ckId=FDBK41174
Done!
Would you believe, there are places where SQLServer is used with
non-MS middleware and client technologies, from Powerbuilder to
(shudder!) Java and J2EE!? Not to mention stuff like Python ...
And worse yet, there are places where there are DBA and data architect
and similar jobs, that involve SQLServer and not (by default) Visual
Studio! Gasp! But I have been there, time and again!
J.
|||!
> How can I do to debug a Stored Procedure in SQL Server 2005 from SQL
Server
> Management Studio? I looked for the Debug... option when I right-clicked
the
> SP but it seems that in SQL Sever 2005 doesn't not exist.
Does anyone know if the debugging interface is public? That way, we could
finally integrate a debugger in our database development tool :-)
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com
|||On Wed, 30 Nov 2005 15:34:32 -0800, jxstern wrote:

>On Thu, 01 Dec 2005 00:11:55 +0100, Hugo Kornelis
><hugo@.pe_NO_rFact.in_SPAM_fo> wrote:
(snip)

>Done!
Hi J.
Thanks for your vote!
Current standing: 11 votes, average rating 4.91. That works out to 10
votes at rating 5, and one vote (mine <g>) at rating 4.

>Would you believe, there are places where SQLServer is used with
>non-MS middleware and client technologies, from Powerbuilder to
>(shudder!) Java and J2EE!? Not to mention stuff like Python ...
>And worse yet, there are places where there are DBA and data architect
>and similar jobs, that involve SQLServer and not (by default) Visual
>Studio! Gasp! But I have been there, time and again!
Not to mention, places where the expense of acquiring MS Visual Studio
in addition to SQL Server is too high - none of the other features are
needed, and debugging alone isn't enough justification to splash out on
Visual Studio.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)