User talk:DeepakChourasiya

Hi,

I want to contribute to wiki. This is just a starting point. As and when I get chance to update things here, I will update this page. There will be variety of sections where I want to write, these can be

=Technology=

Debugging SQL Stored procedures
I wanted to talk about the use of SQL Debugger as a tool for debugging stored procs. For the recent project that we were working on, we were required to write many stored procedures in SQL Server. The traditional approach of writing print statements and return at various points is a real trouble. I am sure you all will agree to it. I thought if there was a Debugger exactly the way we get in .NET, C++ etc would be a great tool to facilitate development and troubleshooting the issues. I thought of finding out the ways one can do it. Initially just to see the various inputs and then to find out the output of queries fired based on the inputs. Then, watch these variables as they processed and finally check what the output was fascinating. I saw two possible solutions to do this.


 * SQL Debugger provided in Query Analyzer.
 * SQL Debugger provided by .NET environment.

I started finding out how I can get this thing working. One of the pre requisite was being a Database administrator for the database where we want to debug the sp. I managed to get the DBA level access to the desired development server. After this I started debugging the stored proc. At this part of time my machine was a Windows 2000 server. I got the thing working. Some time later when I was supposed to use a Windows XP machine, I started setting up I was having a Windows XP machine (with Service Pack 2), which I later got to know that is a big problem for debugging stored procedures. There were a number of issues listed at the links below as possible causes for not being able to debug the stores procedures from a XP machine. After all settings that were needed in the DCOM portion, I found out that these were not applicable at least in my case. After this I got Service Pack 3 for SQL Server. This service pack was required to be installed at the Server as well as the client. I got this service pack installed and started my work, a lot more easier then the normal print statements. One of the Microsoft link said that I cannot debug stored procedure if I am connected through Terminal Services. To my surprise I am now capable of doing this as well.

Some links to which I went thru, that may be of use while setting up the SQL Debugger: http://support.microsoft.com/kb/839280 http://support.microsoft.com/kb/328151 http://support.microsoft.com/kb/280100/EN-US/ http://support.microsoft.com/kb/280099/EN-US/ http://support.microsoft.com/kb/175868/EN-US/ http://support.microsoft.com/default.aspx?scid=kb;en-us;280101

As a next attempt I will try to find out how can I enable the same on .NET environment as well. Actually, I found the Visual Studio as a good way of editing, and managing stored proc. Also, there are a number of limitations on Query Analyzer debugger which I think shall not be applicable on Visual Studio. I think that the whole architecture for debugging on Visual Studio is different then that of Query Analyzer. Hence, the components involved are also different. If any one succeeds in debugging thru Visual studio then please update this talk so that I can follow those steps.

=Visual Studio Designer bug=

I was facing an issue very frequently with Visual Studio 2005 in ASP.NET application. I found the resolution today, so thought will share with you all.

The issue is as follows:

Consider a scenario where you have a container contained within another container in an ASP.NET page Either such two or three levels of nesting is present The innermost container has a lot of ASP.NET UI controls present in it Now you switch from HTML mode to Designer mode Visual Studio will crash most of the times saying System.OutOfMemoryException Interestingly, system is not running out of memory but still the page will not open (For me it used to open after 3-4 attempts) I found the resolution to this:

Upgrade the file Microsoft.VisualStudio.Web.dll (path: C:\Program Files\Microsoft Visual Studio 8\Common7\IDE) to some version which has modified date later than September 2006 (Contact me, if you need the file) Upgrade the file HTMED.DLL (path: C:\Program Files\Microsoft Visual Studio\Common\IDE\IDE98) to some version which has modified date later than October 2006 Register both the file using Regsvr32 The problem for me was solved. The same page which was consuming close to 1.2 GB of RAM and used to take minimum 3-4 min to load in designer (for successful load, I had at least a few crashes every time I used to open it, so practically 10 min) now opens in few seconds and negligible memory consumption.

=Biology= =Human Body= =Other Sciences=