XSLT Stylesheet to produce developer/object oriented html report from SQL Server 2005 Upgrade Advisor xml report file. Name the script sqlupad.xsl and insert the following as the first line in the xml Upgrade Advisor report file. Place sqlupad.xsl file in same directory as the xml report. This stylesheet works against Database Server component reportonly, does not work against the DTS xml report
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:strip-space elements="*" />
<!-- stylesheet to produce developer/object oriented html report from SQL Server 2005 Upgrade Advisor xml report
insert "<?xml-stylesheet type="text/xsl" href="sqlupad.xsl"?>" as first line in the xml file and place sqlupad.xsl
in same directory. Database Server component stylesheet only, does not work against DTS xml report -->
<xsl:template match="/">
<html>
<head>
<title>SQL Server 2005 Upgrade Analysis</title>
<style type="text/css">
body {
background-color: #BED2E9;
}
table {
font-family: Tahoma, Arial, sans-serif;
font-size: 12px;
background-color: #FFFFFF;
}
.titlediv {
background-color: #FFFFFF;
}
</style>
</head>
<body>
<div class="titlediv" width="100%">
<p align="center">
SQL Server 2005 Upgrade Analysis:<br /><strong><xsl:value-of select="/AnalysisResults/ExecutionSummary/Server" /></strong>
<br /><xsl:value-of select="/AnalysisResults/TimeStamp" />
</p>
</div>
<p align="left">
<strong>Objects</strong>
<table width="100%" border="1" cellpadding="0" cellspacing="0">
<tr bgcolor="#DDDDDD">
<td width="10%">
<strong>When to fix</strong>
</td>
<td width="32%">
<strong>Description</strong>
</td>
<td width="7%">
<strong>Database</strong>
</td>
<td width="23%">
<strong>Object</strong>
</td>
<td width="2%">
<strong>Type</strong>
</td>
<td width="25%">
<strong>Comment</strong>
</td>
</tr>
<xsl:apply-templates select="/AnalysisResults/Reports/Report" />
</table>
</p>
</body>
</html>
</xsl:template>
<xsl:template match="Report">
<xsl:variable name="issueId" select="IssueId" />
<xsl:variable name="itemId" select="ItemId" />
<xsl:if test="/AnalysisResults/Items/Item[ItemId = $itemId]/ItemAttributes/ItemAttribute/Value[1] = 'Database'">
<tr bgcolor="#FFFFFF"><xsl:apply-templates select="/AnalysisResults/Issues/Issue[IssueId = $issueId]" />
<xsl:apply-templates select="/AnalysisResults/Items/Item[ItemId = $itemId]" /></tr>
</xsl:if>
</xsl:template>
<xsl:template match="Issue">
<td><xsl:value-of select="IssueType" /></td>
<td><xsl:value-of select="IssueDescription" /></td>
</xsl:template>
<xsl:template match="Item">
<xsl:apply-templates select="ItemAttributes" />
</xsl:template>
<xsl:template match="ItemAttributes">
<!-- Database -->
<td><xsl:value-of select="ItemAttribute[2]/Value" /></td>
<xsl:choose>
<!-- Workaround for xml format where object and object type are in different columns -->
<xsl:when test="normalize-space(ItemAttribute[3]/Value) = 'P'">
<!-- Object -->
<td><xsl:value-of select="ItemAttribute[4]/Value" /></td>
<!-- Object type -->
<td><xsl:value-of select="ItemAttribute[3]/Value" /></td>
</xsl:when>
<xsl:otherwise>
<!-- Object -->
<td><xsl:value-of select="ItemAttribute[3]/Value" /></td>
<!-- Object type -->
<td><xsl:value-of select="ItemAttribute[4]/Value" /></td>
</xsl:otherwise>
</xsl:choose>
<xsl:choose>
<xsl:when test="string(ItemAttribute[5]/Value)">
<!-- Comments -->
<td><xsl:value-of select="concat(ItemAttribute[5]/Value, ' ', ItemAttribute[6]/Value)" /></td>
</xsl:when>
<xsl:otherwise>
<td><xsl:text>-</xsl:text></td>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
</xsl:stylesheet> 
2007-10-02 (first published: 2002-06-20)
15,451 reads
I have always read that 8060 bytes is the maximum size. This is stated over and over again in Books Online, the MS site and numerous other sites, including this one. However a post in our forum recently questioned this. I decided to verify the problem and do a little research.
2007-10-02 (first published: 2002-02-07)
37,400 reads
The User_Defined_Functions.exe file contains the User-Defined Functions white paper. The User-Defined functions white paper outlines the characteristics of the new user-defined function (UDF) feature that is introduced in Microsoft SQL Server 2000. The white paper also summarizes how you can create your own Transact-SQL functions to extend the programmability of Transact-SQL.
2001-08-31
2,233 reads
The following stored procedure will demonstrate the use of cursor metadata. Using cursor metadata we can get information about an SQL statement and use that information to dynamically generate other code such as HTML or other stored procedures.
2001-07-27
5,203 reads
ne of the issues you face when building Web applications is handling the errors you encounter when interacting with a back-end database. I was recently working with someone to create a new Web site with SQL Server™, ActiveX® Data Objects (ADO), and ASP. Lots of little things came up that I thought were worth sharing with MIND readers, so I'll focus this column on what I learned from this experience and the solutions to many of the problems I faced.
2001-07-13
1,579 reads