SQL
Get flash to fully experience Pearltrees
You can track your team's progress more easily by creating reports that aggregate data from Visual Studio Application Lifecycle Management (ALM) into charts and tables. For example, you can create a report that shows how many active work items are assigned to each person on the team. To create this type of report, you use Report Designer in SQL Server and the SQL Server Analysis Services cube for Visual Studio ALM.
Create an Aggregate Report using Report Designer and the Analysis Services Cube
This topic explains important differences in how rendering extensions are used and includes a list of topics that explain how each rendering extension processes a report definition. Understanding the fundamentals of report rendering and the kinds of rendering extensions that are available is necessary for making effective decisions about report design. In Reporting Services, reports are based on an XML schema called Report Definition Language (RDL). This schema provides a uniform description of a report. The schema is supported by all rendering extensions that are used to output reports in specific formats. As long as a report conforms to RDL, it can be rendered through any rendering extension that supports the RDL standard.
Design Considerations for Report Rendering
Michael Coles: Sergeant SQL : Parent-Child Build Scripts with SQLCMD
On the SQL Server public programming newsgroup someone recently posted a question about an SSMS error ( "Cannot parse script. 'System.OutOfMemoryException' thrown." ) I hadn’t encountered this error myself, but the workaround is to break up very large scripts (50+ MB) into smaller scripts. Adam Machanic posted a T-SQL Tuesday challenge to post a solution to a puzzling situation , so this actually gives me a good opportunity to share how I structure my own build scripts -- which avoids this issue entirely. When I create database build scripts, I use the SQLCMD utility to run them from the command line instead of using SSMS or another tool.
October 11, 2007 I thought Ligaya Turmelle's post on SQL joins was a great primer for novice developers. Since SQL joins appear to be set-based, the use of Venn diagrams to explain them seems, at first blush, to be a natural fit. However, like the commenters to her post, I found that the Venn diagrams didn't quite match the SQL join syntax reality in my testing. I love the concept, though, so let's see if we can make it work. Assume we have the following two tables.
