Debug sproc [MSSQL stored procedures] in VS

( Source: http://aspalliance.com/1131_Understanding_Object_Pooling_in_Microsoft_NET )

In VS at the Sever Explorer pane I right-click on my data connection that I added and select Modify Connection. Then in the Modify Connection dialog I clicked Advanced... and then in the Advanced Properties dialog I changed Pooling from True to False. Now it works. Also, in the configuration file, the Enable SQL Server debugging must be checked. Also, I have to add cmd.CommandTimeout=1800 to the VB's sproc area else it will time-out while clicking thru the sproc in the debugger.

But, when not debugging, in order to get the app to run to completion without crashing with the error Error while executing 'a batch cmd' at line 0 , I have to uncheck Enable SQL Server debugging and set Pooling back to True. --Because not pooling the connections hurts performance.

(Summary: You do the above to VS so that you can step through,and see, the database while debugging the code of an app in VS.)


To export DTS package, do the following:

  1. Open MS SQL Server Enterprise Manager
  2. Go to Local Packages
  3. Open some DTS Package
  4. In the DTS Package window from menu select item Package->Save As...
  5. In the Save DTS Package dialog
    • in the Location field select Structured Storage
    • File
    • in the File Name field set destination path of saved file
  6. Press OK button


Server 2000: Query Analyzer Tips & Tricks

You probably know that SQL Server stores metadata about all of the objects in a database. The system tables contain a wealth of information about column names, data types, identity seeds, and so on. But did you know that you can get that information with a single keystroke via Query Analyzer? Highlight the object name in any SQL statement and press Alt+F1. Figure 1 shows the results for a SQL Server table. If you don't have anything highlighted, Alt+F1 will give you information about the database itself. For an equally neat trick, highlight a SQL keyword and press Shift+F1; you'll go straight to the Books Online page that describes that keyword.


Getting .dll into Registry

  1. Download the file (MSRDO20.zip) to your desktop
  2. Unzip the content of the file (a file called MSRDO20.DLL) to your desktop
  3. Right now you should have a new file called MSRDO20.DLL that resides on your desktop
  4. Copy this file to your Windows System Folder; this folder is usually found inside your 'C:\Windows' folder. It is called 'C:\Windows\System' or 'System32'...
  5. Go to 'Start Menu' and choose 'Run'
  6. A new window titled 'Run' will open; type the line 'regsvr32.exe msrdo20.dll' and hit 'Enter'.
  7. A message will show up stating that the registration was successful.


Visual Studio Short-cuts

Most of the time, you will Step Into or Step Over commands in your stored procedures. The commands below apply to a single T-SQL line:

  • Step Into (F11): Use to single step through your code. (Move the yellow arrow down one statement.)
  • Step Over (F10): Useful if you have lines of code that perhaps modify data or call other procedures that you don't care about while debugging. For example, you may want to skip code that performs auditing.
  • Step Out (SHIFT+F11): Execute the rest of the stored procedure without pause.
  • Run to Cursor (CTRL+F10): Position the cursor to a point in your code and then hit CTRL-F10 to execute all code up to that point.
  • Continue or Start Debug or Run (F5): Start Debug. Or resumes execution until completion or until the next breakpoint.
  • Toggle Bookmark (CTRL+K)
  • Help (F1)

When you provide a summary of the class using XML comments, your class displays documentation about itself in appropriate places within Visual Studio, such as in the List Members box. Open the List Members box by selecting Edit | Intellisense | List Members from the main menu bar or by clicking the Display an Object Member List icon on the Text Editor toolbar.

Command Window debugging: Getting Values

To see the value of your variable whilst in Debug mode, use the "Command Window" (View >Other Windows >Command Window). Enter this: ? myVariableName


SQL: Bulk import

Bulk import (save file.txt as csv): LOAD DATA INFILE 'file.txt' INTO TABLE 'tblFoo' (col1, col2, col3)

BULK LOAD IMPORT ('c:\file.txt') INTO TABLE 'tblFoo' (col1, col2, col3)


SQL Server 2000: make table backup with DTS

  • Right-click the table
    • choose Export Data
  • Choose a destination
    • Server: "nwdsql" and Database: NELausData
  • copy table(s)
  • UserXRef"_bkup" (Destination)

Done, then refresh explorer to view.


Install Google Search API Into Visual Studio

  • Get the Google API and unzip. Import GoogleSearch.wsdl to the Project root.
  • Right-click on the Project root.
    • Add Web Reference
      • Then type in the URL: http://localhost:1574/projectname/GoogleSearch.wsdl or http://foo.com/GoogleSearch.wsdl

Then you should see an App_WebReferences folder in your Project. And then a folder in that called localhost. And then files GoogleSearch.discomap and GoogleSearch.wsdl in that.

Test SQL Injection Attack on ASP

Username: foo
Password: abc' OR 'x' = 'x


Load a Control into Visual Studio

  • Right-click on toolbar and "Choose Items"
  • Then browse and go to your /Controls/ folder
  • Then click on it and open
  • Then click "OK"

Then it will be on your toolbar and there will be a Reference to it in your /Bin/

header adsense code