Developing and Deploying SQL Sever Apps on Windows Integrity

12 of 39
• Place breakpoints in objects by double-clicking the object name in project
Explorer, then click in the left margin of the Text Editor on the lines of code
where you want to insert the breakpoint.
• A message is displayed in the Output window stating whether the object was
successfully deployed to the SQL Server database. The script in the Test.SQL
file, (or whichever file was made the default debug script), will run, and if any
of your breakpoints hit, you can debug the object.
• By repeatedly clicking Step Into from the Debug menu, you can watch how
the method result gets built. In the Locals window, open the variable value,
that contains the current store name being processed. Click the variable if it is.
The child node will be returned from this function, and it contains all of the
store names up to the current one concatenated together and separated by
commas.
• In the Text editor, double-click the variable to select it. Drag it to the Watch
window and drop it anywhere in the window. The variable is now added to the
list of watched variables.
• Step through several times as needed. The value may change each time
depending on the code. Add or remove break points as needed. Stop when you
hit the return statement. Click Continue again to finish debugging the
function.
• For more debugging details see the following Microsoft Web sites:
C# http://msdn2.microsoft.com/library/2kf0yb05.aspx
Visual Basic
http://msdn2.microsoft.com/library/0a10ws2y.aspx
C/C++
http://msdn2.microsoft.com/library/kcw4dzyf.aspx
ClickOnce deployment from Visual Studio
Like x86 and x64 applications, all SQL Server 2005 database applications developed in Visual
Studio 2005 SQL Server project
can be deployed to an Integrity server with ClickOnce. You
can develop and deploy T-SQL only applications directly on Integrity Server’s SQL Server
Management Studio.
As Microsoft recommends using .NET for all the SQL application development, the same code
base (source code) can be used across different hardware platforms, including Integrity
servers. The same .NET assembly will run under Integrity’s .NET Framework.
The behavior of VC++ managed code extension applications will be similar to any other .NET
application for Integrity. VC++ or VB6 native language can also be used to write applications
like extended stored procedures, but they require Itanium specific compilers from the Visual
studio team suite edition. This native code scenario may not be supported in future versions of
SQL Server.