A long time ago - February and March 2006 - Eugene Asahara has posted two very intersting articles about The "KPI Cause and Effect Visio Graph" is a very useful visualization tool to diskuss KPI´s with the prospective users whereas the "KPIRelationships sample application" is a very smart tool to control if all perspectives, KPI´s, etc are developed and have the right definitions. This two articles are a really must-read and Eugene also provides the tools for download - so check it out!
Microsoft provides some useful nice stuff for download: "Keyboard shortcuts can help increase productivity when performing certain tasks within the Visual Studio 2005 IDE (Integrated Development Environment). This wall poster provides the shortcut and associated description for the default key bindings setup in the Visual Basic 2005 profile. The poster is provided here in both color and grayscale for you to print locally as a PDF file." Download, print, place it near your keyboard and save time: Visual Basic 2005 Keyboard Shortcut Reference Poster Visual C# 2005 Keyboard Shortcut Reference Poster Visual C++ 2005 Keyboard Shortcut Reference Poster Microsoft, what about providing that for the Business Intelligence Developer Studio and the SQL Server Management Studion also??
This article shows how easy it really is to write custom code for SQL Server Reporting Services
Brian Welcker has published a coding to programmatically set the page size properties of a linked report.
The feature doing linked reports worked well in Reporting Services 2000, because the linked report got the page settings from the original report but in RS 2005 this feature just was "forgotten", as Brian admits in this article.
The following content is intellectual property of Brian Welcker, the original posting can be found here:
I previously showed how you can programmatically set the page size properties (used by the print control) for a specific report on the server. I created an updated version of this sample that will set the page properties for all linked reports on your report server. It copies the relevant properties from the base report to the linked report. If you are using the rs.exe script host, you can delete the proxy methods at the top as they are handled automatically. This example uses the SQL 2000 RS SOAP endpoint but will work for SQL 2005 RS as well.
Dim rs As New ReportingService.ReportingService
Dim ci(), c As ReportingService.CatalogItem
Dim l As String
rs.Url = "http://localhost/reportserver/reportservice.asmx"
rs.Credentials = System.Net.CredentialCache.DefaultCredentials
ci = rs.ListChildren("/", True)
For Each c In ci
If c.Type = ReportingService.ItemTypeEnum.LinkedReport Then
Dim p(5) As ReportingService.Property
p(0) = New ReportingService.Property
p(0).Name = "PageHeight"
p(1) = New ReportingService.Property
p(1).Name = "PageWidth"
p(2) = New ReportingService.Property
p(2).Name = "TopMargin"
p(3) = New ReportingService.Property
p(3).Name = "BottomMargin"
p(4) = New ReportingService.Property
p(4).Name = "LeftMargin"
p(5) = New ReportingService.Property
p(5).Name = "RightMargin"
l = rs.GetReportLink(c.Path)
p = rs.GetProperties(l, p)
rs.SetProperties(c.Path, p)
End If
Next
If you would like to use the script from above with the rs Utility as a Reporting Services Script File, you will have to do some changes to the coding:
Public Sub Main()
Dim ci() as object
dim c as CatalogItem
Dim l As String
rs.Credentials = System.Net.CredentialCache.DefaultCredentials
ci = rs.ListChildren("/", True)
For Each c In ci
If c.Type = ItemTypeEnum.LinkedReport Then
try
'Console.WriteLine(c.name)
Dim p(5) As [Property]
p(0) = New [Property]
p(0).Name = "PageHeight"
p(1) = New [Property]
p(1).Name = "PageWidth"
p(2) = New [Property]
p(2).Name = "TopMargin"
p(3) = New [Property]
p(3).Name = "BottomMargin"
p(4) = New [Property]
p(4).Name = "LeftMargin"
p(5) = New [Property]
p(5).Name = "RightMargin"
l = rs.GetReportLink(c.Path)
p = rs.GetProperties(l, p)
rs.SetProperties(c.Path, p)
Catch e As SoapException
Console.WriteLine("")
Console.WriteLine("Report Error: " & c.Path & "\" & c.name)
Console.WriteLine("")
Console.WriteLine(e.Detail.InnerXml.ToString())
Console.WriteLine("")
Console.WriteLine("")
end try
End If
Next
End Sub
MSDN also includes some more usefull informations about rs.exe, like the ones mentioned below.
This one is from "Scripting Deployment and Administrative Tasks":
"The report server script host tool (rs.exe) can run custom Visual Basic code that you might write to re-create or move existing content from one report server to another. With this approach, you write script in Visual Basic, save it as an .rss file, and use rs.exe to run the script on the target report server. The script you write can call the SOAP interface to the Report Server Web service. Deployment scripts are written using this approach because it allows you to re-create a report server folder namespace and content, and re-create role-based security.
You can also use rs.exe to run custom or generated script that you create in SQL Server Management Studio. For Reporting Services, the script generation feature in Management Studio creates Visual Basic code for a very specific task (for example, creating a role, setting report properties, defining a schedule, and so on). The generated code is incomplete; it captures keyboard strokes and mouse events. To use this code, you must copy it into a larger program that you create."
This one from "Compiling and Running Code Examples":
"Reporting Services provides a scripting utility, the rs utility, which is shipped as a file named rs.exe. You can run any Visual Basic code example that is provided in the Report Server Web service library documentation using the rs utility that is included with Reporting Services.
To run a code example
-
Using a text editor, create a blank text file named sample with an .rss extension.
-
Copy and paste the following code into the blank file:
Public Sub Main()
' Your code goes here.
End Sub
-
Copy and paste the code example you want to use into the space provided in the previous code sample. Save the file. If you are copying directly from a code example provided in a reference topic, remove any import statements, module declarations and the following line of code:
Dim rs As New ReportingService2005()
The ReportingService2005 object is already declared and instantiated within the script environment. Redeclaring the object in your code will cause your script to fail. For more information about properly formed scripts, see Formatting the Reporting Services Script File.
-
Open a command prompt: On the Start menu, click Run, type cmd in the text box, and then click OK.
-
Navigate to the directory that contains your Sample.rss file. At the command prompt, type the following command to run the sample script file. Be sure to replace the given server URL with that of the report server and endpoint you are accessing. For example:
rs –i sample.rss –s http://myserver/reportserver"
Identifying the User during runtime sometimes can be usefull for your report header or footer, can be used to filter data or for parameters, and so on but it bars users from subscribing to reports, because Reporting Services is not able to identify the user from the subscription.
Brian Cooper had published a workaround for the known issue coming around using User!UserID in Reporting Services, but the content is gone...I discovered that during a discussion at the MSDN forum about the problem with User!UserID in datadriven subscriptions.
Jan Pieter Posthuma remembered the code and had the correct hint to solve this problem - many thanks!
Declare that parameter with a default value of the output of the custom code function (Code.UserName()) and thru out the report you use this parameter as replacement for the User!UserID. When scheduling this report you bind this parameter with the output from your subscription query.
In case you haven't got the custom code from the weblog:
Public Function UserName()
Try
Return Report.User!UserID
Catch
Return "System"
End Try
End Function
You surely know "Project REAL", the SQL Server 2005 reference implementation at Barnes & Noble. It contains information on all upcoming topics in a BI project.
And now...
your are not only able to read about it - you are able to download a whole subset of the project REAL data and the various parts of the implementation
Extract from the website:
"The kit contains:
1. A set of instructions for setting up the environment
2. Guidance on how to explore the implementation
3. A sample relational data warehouse database (a subset of the Project REAL data warehouse)
4. A sample source database (from which we pull incremental updates)
5. SSIS packages that implement the ETL operations
6. An SSAS cube definition and scripts for processing the cube from the sample warehouse
7. Sample SSRS reports
8. Sample data mining models for predicting out-of-stock conditions in stores
9. Sample client views in briefing books for the Proclarity and Panorama BI front-end tools
This kit will guide you through the key points to observe in the Project REAL implementation. Use it to learn and to get ideas for your own implementation. (While we believe it represents a very good design and generally follows best practices, it should not be regarded as the solution for every BI situation.) It will be helpful to see the overview presentations about the BI tools in SQL Server, or read documentation, before exploring the kit. One good source of information is to go through the tutorials that ship with SQL Server (the tutorials are installed when you select “Workstation components, Books Online and development tools” at installation time)."
"101 Code Samples for Visual Basic and C#" available for download at the Microsoft Download Center.
Extract from the website:
"This download includes a master set of Visual Basic and Visual C# code samples demonstrating various aspects of the language in the following areas: syntax, data access, Windows Forms, Web development and Web services, XML, security, the .NET Framework, file system and file I/O, interop and migration issues, COM+, ADO.NET, and advanced topics including graphics with GDI+, remoting, serialization, MSMQ, and Windows services."
Sorry, German only...
Die Slides der Student Technologie Conference 2005 stehen zum Download zur Verfügung.
If you would like to build a Wait-Screen in your own ASP.Net Application like it is for example in Reporting Services you should have a look at the posting of Daniel Fisher.
He describes every step it takes to implement it in a clear and detailed way that even I could understand it... 
Thanks, Daniel!
Sorry, German only...
Auf den Seiten des PASS Deutschland e.V. steht ein CommunityCast von Sebastian Weber zum Thema "SQL Server 2005 - CLR Entwicklung" zum Ansehen und zum Download zur Verfügung.
Am 02.03.2006 ab 19.00 Uhr wird es ebenfalls unter dieser Adresse eine Möglichkeit zum Chat mit Sebastian Weber geben, in dem entsprechende Fragen zum Thema CLR Entwicklung gestellt werden können.
Viel Spaß mit dem CommunityCast und herzlichen Dank an Sebastian Weber!
If you want to have changing colors in the background of your details of your report, for example first row grey, second white and so on, you should use this expression:
=IIF(RowNumber(Nothing) mod 2=0,"#FFFFFF","#E8E8E8")
Sam Batterman - a Business Intelligence Evangelist with Microsoft Corporation in Malvern, Pennsylvania - has posted interesting approaches for conditional formatings in his blog.
Some links to be able to understand the Smart Client Concept from Microsoft:
Sorry, German only...
IIS 6 für den Web Entwickler
"Dieser Webcast zeigt, wie man die IIS Dienste wie Web, Mail und FTP konfiguriert und zeigt mögliche Stolpersteine auf. Anhand einer üblichen ASP.NET Web Anwendung werden die notwendigen Schritte von der Installation bis zur Wartung gezeigt."
Dirk´s blog contains a real interesting entry to get started with Indigo
Here are the links:
Visual Studio .NET Web Control for Business Intelligence
This OLAP Web Control, developed by GrapeCity, Inc. brings the OLAP cubes right into your business applications allowing you to view, explore, and summarize data through your browser.
Following are some of the features provided by the control:
- Drilldown, drillup, slicing, and drillthrough
- Run-time layout designer
- Multi-language support
The MSDN Webcast Leveraging Application Blocks in Your Application Development by Aaron Suzuki will be a good intrduction to this topic
The Enterprise Library for .NET Framework 1.1 will also be a usefull resource, especially the Data Access Application Block will be worth a click...
Extract from the website:
"Application blocks help to address the common problems that developers face from one project to the next. They are designed to encapsulate the Microsoft recommended best practices for .NET applications. They can be plugged into .NET applications quickly and easily. For example, the Data Access Application Block provides access to the most frequently used features of ADO.NET, exposing them through easily-used classes. The application block also adds related functionality not directly supported by the underlying class libraries."
Starter Kits, Codes, Snippets, Tools - all available in this Download section.
Please have a special look on these two tools:
MS provides a complete Migration Guide here, which also includes a Migration Assistant.
MS also offers Migration Assistant Packages on this site for ASP, PHP and JSP
|
Copyright © 2010 Markus Fischer. All rights reserved.
DasBlog 'Portal' theme by Johnny Hughes.
Pick a theme:
|
|