Most dynamic sites have a database search of some variety. Stored procedures are much more desirable in a web application for many reasons, yet when it comes to performing searches, the stored procedure is not as easily implemented. In a scripted web application, you can create dynamic SQL statements on the fly, putting conditional logic into your WHERE clauses and making the SQL statement fit the situtation. In a stored procedure, it's not so easy. This article will show one way to pass parameters conditionally to your SQL stored procedure. The technique applies to SQL Server, with code provided for ASP and ColdFusion.

In this session, we will see how to use and integrate various Office components with the Business Intelligence features of SQL Server 2000 Analysis services. We will use Excel to access an OLAP cube, then define and display the data with PivotTables. We will also show basic SQL Server Analysis services, simple views, and provide an overview of Analysis Services. We will look at how the data analyzer can be used to show relationships in data elements. We'll showcase the UI, and specifically comparison, and drilldown capabilities combined with Data Analyzer views. Finally we'll take the data we brought into Excel, and combine that with MapPoint data to get rich geographic detail for our data using the MapPoint OLAP add-in. We'll take the data and pull a MapPoint graph into PowerPoint to show how we'd easily make a nice presentation, and then we'll go back to Excel and see how MapPoint data can be brought directly into Excel.

Microsoft SQL Server uses a variant of SQL called T-SQL, or Transact-SQL, an implementation of SQL-92 (the ISO standard for SQL, certified in 1992) with some extensions. T-SQL mainly adds additional syntax for use in stored procedures, and affects the syntax of transaction support. (Note that SQL standards require Atomic, Consistent, Isolated, Durable or "ACID" transactions.) Microsoft SQL Server and Sybase/ASE both communicate over networks using an application-level protocol called Tabular Data Stream (TDS). The TDS protocol has also been implemented by the FreeTDS project [2] in order to allow more kinds of client applications to communicate with Microsoft SQL Server and Sybase databases. Microsoft SQL Server also supports Open Database Connectivity (ODBC). The latest release SQL Server 2005 also supports the ability to deliver client connectivity via the Web Services SOAP[3] protocol. This allows non-Windows Clients to communicate cross platform with SQL Server. Microsoft has also released a certified JDBC[4] driver to let Java Applications like BEA and IBM WebSphere communicate with Microsoft SQL Server 2005.

Using SQL Server 2000 and above versions you can retrieve data from SQL Server in XML format directly from the database. Many XML related features were incorporated in the SQL Server database. This enables the development of XML enabled applications very easy and it makes exchange of data over internet easy. In this article we will discuss about how to use SQLXML to retrieve data directly from SQL server database in XML format.

There are some SQL commands and clauses that help you to retrieve data from the SQL Server in the XML format. Syntax for such is given below: