Developing and Deploying SQL Sever Apps on Windows Integrity

18 of 39
15. Open the SQL Server Management Studio on Integrity Server. Run the stored
procedure as shown below. The output “Hello World:” string is displayed.
16. If there are run time issues on Integrity Server, use the remote debugger from the
Visual studio. Set up the remote debugger as described in Section 2.3. Connect to the
sqlserver process and run the stored procedure at Integrity Server and start
debugging.
ClickOnce deployment from BI Development Studio
Integration Services
• SQL Server Integration Services packages are created from the Business Intelligence
Studio (BIDS) on windows Client and deployed to Integrity Server with either
OnceClick or through the deployment wizard. All the functionalities of the Integration
Services are available in Integrity Servers except:
¾ Script tasks
must be compiled before the package runs in a 64-bit
environment. If you do not use the default precompile option, the script is
compiled at run time and will not work on Integrity. However, run time
compile slows package execution and, except for debugging, it is not used.
¾ Debug capability
on remote Integrity server with Integration Services projects
are not fully functional. The current remote debugger cannot be used to debug
packages deployed on Integrity system. These packages will have to be
debugged on x86 or x64 systems.
¾ Package execution utility
dtexec.exe executes the same way as the Graphical
Interface Utility dtexecui.exe. This dtexecui.exe is a 32-bit process and in a
64-bit environment runs in Windows on Win32 (WOW). You should test the
commands/packages in 64-bit mode by using the 64-bit version of dtexec.exe
before deploying to a production server. Integration Services Considerations
on 64-bit Computers on the Microsoft web site gives more details about 64-bit
Runtime for SSIS packages.