jwcolby
jwcolby at colbyconsulting.com
Thu Jan 29 16:09:36 CST 2009
I am not on the SQL list, and have no intention of ever again being on the SQL list. Thanks for the reply though. John W. Colby www.ColbyConsulting.com Francisco Tapia wrote: > replied on sql list... > -Francisco > http://sqlthis.blogspot.com | Tsql and More... > > > On Thu, Jan 29, 2009 at 1:49 PM, jwcolby <jwcolby at colbyconsulting.com>wrote: > >> I see nothing there about debugging stored procedures. I >> Googled and found that IF you happen to own the advanced >> versions of VS you could use them to do debugging. >> Unfortunately I only own the standard edition. >> >> According to what I read, the debugging was migrated out to >> VS in 2005, and the standard edition of VS would NOT do it. >> >> John W. Colby >> www.ColbyConsulting.com >> >> >> Francisco Tapia wrote: >>> Debugging of stored procedures is available in Sql Server 2000 and Sql >>> Server 2005, in fact it's quite robust. >>> -Francisco >>> http://sqlthis.blogspot.com | Tsql and More... >>> >>> >>> On Thu, Jan 29, 2009 at 6:58 AM, jwcolby <jwcolby at colbyconsulting.com> >> wrote >>> <SNIP> >>> >>>> <Rant Mode> >>>> >>>> My problem in all of this is that I very much a novice at >>>> SQL Server. I have been forced to dig in but, like Access, >>>> there is just so much to know. If I sit here just >>>> "experimenting" trying this and that I get nowhere. There >>>> is no "debugger" for SPs so it is "try something, run and >>>> see". Worse yet the totality of the feedback is "error near >>>> XXX in line YYY", not exactly stellar help. >>>> >>> </SNIP> >> -- >> AccessD mailing list >> AccessD at databaseadvisors.com >> http://databaseadvisors.com/mailman/listinfo/accessd >> Website: http://www.databaseadvisors.com >>