During this monsoon, I captured few moments from my office terrace using my Motorola Milestone Mobile camera. Here are those pics.
[tweetmeme source=”sudevgandhi” only_single=false style=”compact”]
Last Sunday(13th June) evening I was comming back from Gandhinagar to Ahmedabad by road and watched the Sun setting. It was clean sky and really hot weather. We stand by the bridge over Narmada Canal near Adalaj and captured the Sun in my HTC Tattoo mobile camera. Here are few pics.
A deep depression over Arabian sea which has intensified into a cyclone storm has caused sudden change in climate in Ahmedabad. Its effect of cyclone “Phet” hitting western part of Inda.
Here are few photographs I took today at around 1:30 PM using my cell phone.
Location: Ahmedabad, Gujarat, India
Helsinki city transport ferries have resumed trips to Suomenlinna now by breaking the ice after a long winter!
It was an amazing experience of standing on the dock of the ferry while it was making its way to other shore by breaking ice. Some sort of Titanic 😉
SQL Server Reporting Services, due to its robust but user friendly architecture, is an obvious choice for Enterprise or in-house reporting, for product management, sales, and human resource and finance departments. Its flexibility makes it an ideal for usage in applications as well (Deliver User-Friendly Reports from Your Application with SQL Server Reporting Services – MSDN Magazine August 2004). Reporting Services offer various delivery methods, from ftp to email and it provides various rendering formats therefore it makes adds easiness to business to business reporting. Similarly because of its flexibility and industry standard security model, it makes extranet and secure internet reporting easily achievable.
The reporting system comprises for following main components.
Report Server & Report Server Database
Report Server is an integrated web service which controls report generation and management. Report Server database is a SQL server database which is used as data dictionary about reports (catalogue, groups) and caching. SQL server agent is used for scheduling the reports.
An ASP.NET based Web interface for managing the reports, setting security and user permissions.
Report Designer is considered as a part of reporting services in Microsoft documentation but because RDL (Report definition language) is an XML based open standard, any vendor can implement it and therefore a single tool can’t be categorized as report designer. However, Microsoft provides a graphical report authoring tool with Visual Studio.NET 2003 or later for creating reports which automatically creates RDL markup at the backend.
Reporting services were designed with concept of disparate data sources in mind. A single report can retrieve data from multiple heterogeneous databases and render it to make it look like it’s from a single source. It provides built-in windows authentication security however one can write custom security wrapper to fit particular enterprise needs.
With SQL Server reporting services, multiple delivery methods and formats work like a charm. You design a generic report and reporting server takes care of exporting it into HTML, Excel, PDF, WAR(web archive), TIFF, CSV and XML format. As always, one can write his own custom format writer wrapper class for any custom format.
Reporting Services Delivery Formats
Reporting Services provide four distinct formats of report delivery also known as subscription in Reporting Services arena; Individual subscription, data driven subscription, SMTP delivery and file share directory (FTP) based subscriptions.
Reporting Services Architecture
Above diagram schematically explains Reporting services architecture
Beside the code segments which can be written within a report in VB.NET, these API provides makes it more programmable. The application program interface can be classified into following categories.
- Data processing extension application programming interface (API)
- Delivery extension API
- Rendering extension API
- Security extension API
- Web service API
- Windows Management Instrumentation (WMI) configuration API
Interactive interfaces are another salient feature of SQL Server Reporting Services. Reports designed in SQL server reporting services supports charts, document map, freeform, cross tab matrix, sub reports and tables. Reports can also be parameterized and event driven (supports actions). Management is one of the most important parts in any reporting system; SQL server reporting services has it all planned. It manages jobs from a user friendly console, provides personalization "my reports", tracks report history, manage shared data sources, provide search, subscription and snapshot features with shared subscription from one stop shop, the management console. Reporting Services supports report caching and stores reports execution data in execution logs,
Report Generation and Publishing
As defined in the diagram above, the process of report generation and publishing consists of the following main steps.
- Reporting server engine (Report Processor) receives the request for a particular report. A request includes parameters and formatting instructions.
- Report Processor retrieves the report definition on the basis of request.
- For the corresponding RDL, the report processor then retrieves the report data for specified data sources.
- Report Processor performs transformation on reporting data and sends the document data along with schema to rendering engine (rendering extension).
- The extension publishes the final rendered report.
- The following steps are basics of how reporting services work. The extensions (data processing extensions, rendering extensions etc) can be custom built and wrap around the existing set of API to provide extended functionality.
SSRS Integration with SharePoint 2007
- SQL Server 2005 SP2 is installed on report server in Native mode along with WSS Object Model (farm install)
- SSRS Configuration Tool creates a new Report Server database in “SharePoint Integration mode”
- SSRS Add-In is installed on WSS 2007
- WSS Central Admin web pages register SSRS web service and windows service with WSS farm
Database Integration Points
- WSS Content Database stores the master copy of SSRS items
- Schedules, caching, and subscriptions are stored in SSRS database only
I’d like to share a typical problem recently I faced with WSS 3.0 configuration on a Windows 2003 Server.
I created a virtual machine with Windows 2003 OS and named it “myvpc” in a hypothetical workgroup viz. “WKGP” (I initially planned to use it in stand-alone mode). Then I installed all available updates to the Windows Server and .Net framework 3.5 with IIS followed by Stand-alone installation of Latest WSS 3.0. The default team site and central administration site were working smooth. I even created another application using central administration.
Later I changed my mind and thought that it would be better if I include this virtual machine into our company’s local intranet Domain. At this point of time I had to change the PC name from “myvpc” to “SUDEV-VPC” due to some or other reasons.
Now, suddenly none of the SharePoint sites were accessible even from the “localhost“! I opened IIS console and noticed that “SharePoint Admin” site was stopped!!! I checked the systems log and found many errors stating “Cannot connect to SQL Server. MYVPC\Microsoft##SSEE not found“. I was surprised to see this, why SharePoint did not understand the change in name of computer.
I just thought lets run the “Configuration Wizard” again for the WSS. I did it but it failed too at the step-5 saying “Could not access search service configuration database“.
I uninstalled the WSS 3.0 completely and restarted the OS. I noticed that IIS don’t have the sites I created using WSS anymore.
I installed the WSS again, ran the configuration wizard but just to get a disappointment. The error continues to occur. This time I checked IIS and found that the sites I created with previous installation have been created again on the same port (sounds strange again, how new installation of SP came to know about it?)
The WSS 3.0 was using same database (Windows Internal Database aka SQL Server Embedded Edition). But at some location it was using previous computer name and at other it was using new name. (Surprised?)
So I thought lets re-install the Windows Internal Database itself. There is no direct way to uninstall it. So I uninstall the WSS 3.0 first. And then with help of MSDN link (http://technet.microsoft.com/en-us/library/cc708610.aspx) I uninstalled the Windows Internal Database as well. I removed the data files from “%windir%\SYSMSI\SSEE” as per their suggestion followed by a system restart.
Now I installed the WSS 3.0 in stand-alone mode, ran the configuration wizard and guess what? The configuration wizard ran successfully and I was able to access the default team site and admin site again.
It took quite some time to figure out this solution but it worked for me. In your case you may need to retain the backup of the content database and configuration database before un-install and install of WSS.