Monday, March 18, 2013

National Film Awards Announced




Actor Irrfan Khan has won the best actor for his performance as athlete-turned-dacoit in Paan Singh Tomar at the 60th National Film Awards announced today.
Paan Singh Tomar, which has been produced by UTV Software communications Ltd. and directed by Tigmanshu Dhulia, also won the best Hindi feature film.
In non-feature film category, the award for the best film has been conferred to Shepherds of Paradise (Gojri and Urdu) produced and directed by Raja Shabir Khan.
In the category of best writing on cinema section, the book Silent Cinema in India - A Pictorial Journey (English) written by B.D. Garga and published by Harper Collins Publisher India has bagged the top honour, whereas P.S. Radhakrishnan has been conferred the award for the best film critic.
In the feature film category, a total of 38 films from 14 languages have been selected for the 60th National Awards. Chittagong (Hindi) and 101 Chodiyangal (Malayalam) have shared the Indira Gandhi award for the best debut film of a director.
The award for the best popular film for providing wholesome entertainment has been shared by Vicky Donor (Hindi) and Ustad Hotel (Malayalam).
The award for the best director has been conferred on Shivaji Lotan Patil for the film Dhag (Marathi).
The award for the best actor has been shared by Irrfan playing the title role in Paan Singh Tomar and Vikram Gokhale for the film Anumati (Marathi).
The award for the best actress has been conferred on Usha Jadhav for her performance in Dhag (Marathi).
The award for the best supporting actor has been conferred on Anu Kapur for the film Vicky Donor.
The award for the best supporting actress has been shared by Dolly Ahluwalia for the film Vicky Donor and Kalpana for the film ThanichallaNjan (Malyalam).
The best child artist award has been shared by Master Virendra Pratap for Dekh Indian Circus (Hindi) and Master Minon for 101 Chodiyangal (Malayalam).
The award for the best male playback singer has been conferred on Shankar Mahadevan for the song Bolo Na from the film Chittagong. The award for the best female playback singer has been conferred on Samhita for the song Palakein Naa Moon Don from the film Aarti Anklekartikekar (Marathi).
The award for the best screenplay writer (original) has been conferred on Sujoy Ghosh for the film Kahaani.
So we all know that a pregnant Vidya Balan (Vidya Bagchi) is looking for her missing husband in Kolkata. What do you think is the climax of this thriller? Guess and let us know on TwitterFacebookor... more 
1 / 6
| Photo by Rummana Ahmed
Share to FacebookShare to PinterestShare to Twitter
The award for best screenplay writer (adapted) has been conferred on Bhavesh Mandalia and Umesh Shukla for the film Oh My God.
The award for the best dialogue has been conferred on Anjali Menon for the film Ustad Hotel (Malayalam). The award for the best lyrics has been conferred on Prasoon Joshi for the song Bolo Na from the film Chittagong.
A special jury award has been conferred on Rituparno Ghosh and Nawazuddin Siddiqui for the films Chitrangadha (Bengali), Kahaani, Gangs of Wasseypur, Dekh Indian circus and Talaash (Hindi).
The award for the best choreography has been conferred on Pt. Birju Maharaj for the film Vishwaroopam (Tamil).
In the non-feature film category, Vikrant Pawar has got the best director award for the film Kaatal (Marathi). The award for the best debut film of a director has been conferred to Lipika Singh Darai for the film Eka Gachha Eka Manisa Eka Samudra (Odia).
Shumona Goel and Shai Heredia for the film I Am Micro (English) and Vasudah Joshi for Cancer Katha (English) have been selected for special jury award. Timbaktu (English) has been awarded as the best film in the environmental category and Dreaming Taj Mahal (Hindi and Urdu) has been conferred the award for the best promotional.
The national film awards jury was led this year by filmmaker Basu Chatterjee.

Three Cheers and Four Jeers


Triple figures, three fours for a victory, three wickets for Bhuvneshwar Kumar, and more in our collection of cheers and jeers from Mohali. Go figure.



Good start by Shikhar Dhawan:  A man with two pierced ear lobes got up, after making a desperate dive to get into the crease. With the 100th run in the pocket, he took his helmet off, raising his arms, with a smile aimed at the heavens. The shots that helped him enter the history books, were crisp and convincing. Dhawan’s strength is his superbly balanced stance, which ensures that he gets behind the ball at all times. The timing was excellent, and in full display, when he was essaying the cover drive, as also the ones that were driven on the up. The left-hander doesn’t play away from his body, but uses his feet to move towards the pitch of the ball. His inside-out shot against the spinners, with the feet criss-crossing like scissor blades, only added to Australia’s misery. Half-trackers and full tosses were given the respect they deserved, with the 27-year old’s gloves displaying pre-planned intent and restraint. Was he really playing his first Test?
    
Yes he was. India must be saying thanks a ton, for the fastest Test century on debut. The man with the moustache clearly deserved the Man of the Match award.

Murali Vijay Ho:
 This right-hander needs width to play his shots, and when he is offered the room, he will go to any length to hit a four. He leans into the shot right away, with the bat swinging in, in the direction of the gap between the fielders. Vijay’s flick brought up with the wrists rolling over the ball, is something special, with the left knee moving forward and receding.  Stepping out to the Aussie spinners, Vijay sent the ball flying over long on, and to cow corner with an ease and style that is truly his own.

Bhuvneshwar on top in Mohali:
 After going wicketless in the first inning, Bhuvneshwar Kumar accounted for David Warner, Ed Cowan and Steve Smith, to put India in the driver’s seat on day four. While Warner gifted his wicket to Bhuvneshwar, Cowan fell leg-before-wicket. But the best wicket was clearly his last one in the match. Right-hander Smith’s defence was opened up by a ball moving in, with the batsman’s foot nowhere near the pitch of the ball. The Aussie was stuck in the pose for a full second, as he struggled to come to terms with the dismissal.

***************************************

Jadeja vu for Michael Clarke: Ravindra Jadeja had dismissed Michael Clarke three times before he flew down to Mohali. Once the third Test got underway, three became five. Coming in at No.3 in the first inning, Clarke took one step forward, only to beaten by the late turn. Opposite number Mahendra Singh Dhoni did the rest, and the Aussie skipper was sent back for a first ball duck.  In the second inning, Clarke played across to Jadeja, with the edge going on to hit the pad only to make its way into Pujara’s hands at short leg.

Leave it to Smith: While he might have scored 92 (first inning) with the bat, Steven Smith clearly had trouble getting a decent grip behind the cricket ball. The leg spinner bowled half-trackers that Shikhar Dhawan managed to paddle sweep without having to get down on one knee. His full tosses too were promptly put away to the fence. So when the man managed to snare Sachin Tendulkar on the following day, he did surprise everyone.

Not out at No.3:  Coming in at No.3 in India’s first inning, Cheteshwar Pujara wasn’t very happy when he was given out leg-before-wicket to Peter Siddle, off what was a big inside edge. Phillip Hughes, who came in at one drop, in Australia’s second inning, was also given out lbw, when the ball was hitting the pad, with the stance on impact outside leg stump.  On both occasions, the umpire in question was Aleem Dar. 

Three fours from Dhoni:  India made a mess of what should have been a straightforward chase by losing four wickets. When Sachin Tendulkar ran himself out, it was left to Ravindra Jadeja and Mahendra Singh Dhoni to take India home.  The duo survived some anxious moments, before Dhoni struck three fours off Starc to give his side a 3-0 lead in the series.

The death of a Rivalry


Gone are the characters, missing are the mouth-watering contests. The great India-Australia rivalry is dead.


On their on-going tour of India, the biggest event in the Australian camp has occurred off the field and did not even involve the opposition. Australia’s bizarre axing of Shane Watson, Mitchell Johnson, James Pattinson and Usman Khawaja did inject some interest in the series. But it has reduced the fading rivalry to a farce.  

In 1996, the Border-Gavaskar Trophy began on a dustbowl in Delhi, paving the way for one of the most gripping rivalries in international Test cricket. It enriched the game in general. The early legacy of the rivalry was shaped by the promise of a challenge: while both teams were nearly unbeatable at home, the challenge was to prevail in foreign conditions. From the fast, bouncy tracks in Brisbane and Perth to the sandpits or minefields in Mumbai and Chennai, the contests between the two nations redefined modern cricket in a way that few have. 

At home, India were incredibly tough to beat. Australia had to wait 35 years for a series win in India when, in 2004, Adam Gilchrist’s men finally conquered what they called the ‘final frontier’. For India, there was an emerging cricketing narrative to confront – they wanted to challenge one of the greatest cricket teams ever assembled, first led by Steve Waugh and then by Ricky Ponting. Apart from England in 2005, India were the undisputed challenger to Australia’s era of unparalleled domination.

While India raised their game each time they met Australia, the other classic rivalry – the Ashes – had watered down to an incredibly one-sided affair. England struggled to find their personality against the all-conquering Australians unflinching in their desire to assert themselves, and in doing so, take the p*ss off. The India-Australia rivalry was a worthy break from a boring yet-another-Aussie-win phase, solely thriving on the quality of cricket it managed to produce over the span, and along the way, providing the Australians with a hard challenge and fresh problems to crack.

***

THERE WERE characters. At times the dynamics of the series would be reduced to personalities. The consummate genius of Shane Warne against the powers of Sachin Tendulkar; Sourav Ganguly and Steve Waugh consuming themselves in a gripping tactical battle to outwit each other, through pure cricket, at times art. Here was an Indian team, in the mid stages of its evolution as a purely cricketing, not commercial force, deeply motivated by its own history of failures in that country, turned challenger. There was much at stake. They fought, they even won that odd game there. Levelling a series was as good as a triumph, so much so that "winning in Australia" became an integral part of a captain's legacy.

On the other side, India was the final frontier. Today, it's just another frontier. The buzz seems to be severely lacking, the anticipation and the sheer thrill of a big series seems to have evaporated. Today, it's just another series, having its place in Test cricket, but gradually fading away into irrelevance.

The ongoing series, along with the previous one in Australia had nothing exciting. For the heart on the sleeve fan on the Indian side, it’s an been an unbelievable series, easy as you like, an opposition terribly unsure of its own abilities in these conditions succumbing to everything India have thrown at them. For the connoisseur, anything but that. A damp squib of a series, moving away from its promise of producing quality cricket that we’ve all grown up to admire, respect and love. We’ve been witness to a couple of Test matches, laden with sessions that are invariably dull, uneventful (minus the Dhoni onslaught, maybe) and with set patterns that somehow make Test cricket look rather predictable, when it shouldn’t be that. And mind you, this was the best time to play India, a side reeling from what was a humiliating home defeat to England. The proverbial s*it had hit the fan, a few seniors were admittedly dropped and not rested, there were selections that raised some eyebrows, and some familiar names lacking form. Instead, it’s been an absolute mismatch. Also, the disappointing bit is that this is an Indian team playing in third gear.

***

BEFORE INDIA'S home season began, I marked Australia as probably the tougher of the two visitors - a team that could ask India a few questions and probably grind them out if required. I was wrong. The last two Tests have featured by far the most underwhelming performances I’ve seen from an Australian team in India. They look scared, even scarred by their own failings or the inability to turn promise into performances. Their technique seems rather pedestrian and even from a common sense point of view, it is astounding to see them play spin with feet firmly rooted to the crease, hard hands and a scrambled head, unsure and unclear of what to expect from the Indian spinners. Of course playing spin isn’t as easy as writing columns might be, but the disappointment is that, unlike England, they haven’t made an honest effort to rectify some of those mistakes and technical deficiencies. No batsman, barring Michael Clarke and to some extent the likes of Henriques have shown the skill or the resolve to play spin. Teams that have come to India in the last few years, successful or not, have fought, possibly found a way that works, and not fallen apart. The Australians are crumbling.

England’s successful tour last year might just have the blueprint for visiting teams to excel and possibly triumph on Indian soil. And it’s not that difficult to figure out - a good mixture of skills, discipline, the acumen and the resolve that these conditions demand. Not to forget, some knowledge would help too, the little things like a Mushtaq Ahmed helping the English spinners find the right pace on a particular wicket. It required England to play a different kind of a game, an approach that demands an austere approach, primarily cutting down on flair and in doing so, eliminate certain shots from their armoury until their practice and confidence in those shots were near perfect. Can Australia do that? On the evidence on offer, it’s hard to be sure with the impatience of their batsmen. The difference between England and Australia, barring the fact that the former had two quality spinners, is the fact that England had players who executed their plans to perfection. Australia look like a side without a plan, and even if they had one, the players seem incapable of executing them.

The narrative seems clearer as this rivalry fades away - both teams, mediocre at best, will convincingly thrash each other at home, while in foreign conditions - India in Australia and vice-versa, the very desire of a fair, intense contest between bat and ball seems a distant dream. Australian cricket looks to be in a state of irreversible decline and it is equally disappointing to note that Indian cricket isn’t necessarily on the ascendancy. 

There is always the transition argument that a lot of people make for the Australian team. But Australia have been in transition forever. There always will be chatter about how India has over the years has turned into a distraction for the Australians, given that regaining the Ashes seems to be the highest on their priority list. The mess that they find themselves in today, England’s defence of the Ashes looks like a formality waiting to happen come the summer. Even there, the hopes of a contest seem to fade away as things blow up in that dressing room. It’s just disappointing all around.

For a generation which grew up watching Test cricket, this was a series you’d mark your schedules and watch every ball of. As a cricketer, playing against Australia or India was one of the biggest Tests of your career and you’d almost do anything to be a part of these contests. As a fan, you’d bunk lectures, give your work a good old slip to watch the action. Today, you can afford to not watch the game and yet know how it is shaping up. I might be exaggerating about its glorious demise, but if this rivalry has to light up once again, the onus is on both teams to produce the quality of cricket befitting its legacy. Sadly, that may never happen. 

India squeeze out another win Over Australia in 3rd Test At Mohali


A six-wicket victory over Australia at Mohali gives the hosts a 3-0 lead in the series.


MOHALI: Australia resisted like a girl with an attitude, but gave in eventually to a relentless suitor as India won the third Test by six wickets to go 3-0 up in the series. The fourth and last match will be played in New Delhi from March 22 when India will attempt to win four Tests in a series for the first time in their history.

Set a target of 133 in a minimum of 27 overs, India hit the promised land for the loss of Murali Vijay (26), Cheteshwar Pujara (28) and Virat Kohli (34) and Sachin Tendulkar (21). For a brief while it appeared that Australia may confine India to a draw. Thirty were needed in fifty-six balls when Kohli flicked Peter Siddle to short mid-wicket.

Tendulkar and MS Dhoni (18*) played through a phase of quiet as the requirement escalated, and the maestro’s sharp run-out by David Warner gave Australia another look-in to enforce a draw. But Ravindra Jadeja walked in to cream boundaries against Siddle, setting an example for his skipper to follow: Dhoni decided things with three fours off Mitchell Starc and then uprooted a stump as a souvenir.

The win at Mohali was largely set up by Shikhar Dhawan’s blazing 187 on debut that was scored across two sessions on Saturday and made up for the time lost on account of the first-day washout. Dhawan was named Man of the Match, but did not come out to bat on Monday as he has injured his hand while fielding. India were also served well by Jadeja's left-arm spin, that claimed six wickets - three in each innings - in the match. Jadeja has dismissed Michael Clarke five times in this series.

Australia fight

Australia were effectively 79 for eight at lunch, with 52 overs remaining, and were rescued by two stubborn alliances: thirty-six in 16.1 overs between Starc and Haddin, and 44 in 18 overs between Starc and Xavier Doherty for the last wicket. Ravichandran Ashwin deceived Haddin with a ‘carrom’ ball immediately after lunch. 

Starc and Doherty stretched the lead to 132 before the first innings scorer of 99 was done in by Jadeja for 35. This meant that India had 90 minutes plus a minimum of 15 mandatory overs to reach the target. The hosts got there, not in a tearing hurry, but well within the time stipulated, and will head to Delhi soaring on a first-ever 3-0 cushion over Australia.

Spun out

Earlier, Australia resumed in the morning three down on 75, sixteen ahead, and were all out for 223 mid-way into the second session. They suffered the first jolt when night-watchman Nathan Lyon edged Pragyan Ojha to Dhoni.  Australia’s spasm-wreaked captain, Clarke, lasted for 49 deliveries before Jadeja dismissed him for the fifth time this series – via an inside-edged bat-pad that was gobbled up by Pujara at short-leg.

The next dismissal was rather unfortunate. Phil Hughes (69) who had infinitely multiplied his series gains in the course of one attacking knock, was given out ‘lbw’ to Ashwin when the delivery seemed likely to miss leg-stump. All-rounder Moises Henriques (2) lasted ten balls before Jadeja flung himself to his left to accept a blinding return-catch. Siddle had his off-stump knocked back by Ojha, clearing the way for Haddin and Starc to delay the inevitable.

Tuesday, March 12, 2013

Adding an Image to the Report


Adding an Image to the Report

You may want to add a static image to the report, for example, a company or department logo.
To add an image to the report
1.   Open the Toolbox, click the Image item, and drag it onto the design area. The Image Properties dialog box appears.
2.   In the Image Properties dialog box, provide a name for the image (which will not be displayed), and an optional tooltip (displayed when the users hovers the pointer over the image). The Select the image source box has the following three options:
·      External: For images that exist on the report server or another external source. If you select this option, you must provide a URL to the image location in the Use this image field. If the image is changed at its source, the image in the report will change dynamically.
·      Embedded: For images that do not have to be changed. Click the Import button and browse to the image location. The image is embedded in the report and will not change dynamically.
·      Database: For images stored in the database. Provide the path of the image in the Use this field box. In the Use this MIME type box, select the appropriate MIME type for the image.
3.   The Size, Visibility, Action, and Border tabs in the Image Properties dialog box enable you to change the appearance of the image in the report, and also enable you to set the image as a link to another report or URL.
For more information about how to use images in reports, see Images in SQL Server Books Online (http://go.microsoft.com/fwlink/?LinkID=207938)
Adding an Additional Dataset to the Report
You may want to add another set of data to the same report, using a different dataset. This lets you consolidate reports into a single document for ease of reference.
To add an additional dataset to the report
1.   In the Report Data window, click New, and then click Dataset. The Dataset Properties dialog box appears.
2.   In the Name field, enter a name for the dataset or use the default.
3.   In the Data source field, select the data source, usually DataWarehouseMain.
4.   In the Query field, enter the query. This can  either a query created earlier or click the Query Designer button to create a query. When you have finished, click OK.
5.   A second dataset will appear in the Report Data window. From the Toolbox, select a Table, Matrix, Chart, or Gauge, depending on how you want to represent the data. Drag the selected control onto the design surface, and a new data item will appear in the report.
6.   From the Report Data window, drag the desired data fields onto the Table, Matrix, Chart, or Gauge tool, as appropriate.

Changing the Data in the Report


Changing the Data in the Report

To change the data that’s displayed in the report, you must change the query.
To change the query
1.   In the Report Data tree, right-click the dataset, by default this is DataSet1, and then select Query. This starts the Query Designer.
2.   Within the Query Designer, click the Edit As Text button to edit the query directly in the window. Click the Import… button to use a query that you saved previously. The ! button runs the query and displays the results in the lower pane of the Query Designer. If the report does not show the data that you expected, you can revise the query and test it without recreating the report.
Changing the Appearance of the Report
Within the report dataset, you can change the rows, columns, or individual cells. When you click any cell in the dataset, borders will appear around the table. You can click the border to select a row or a column. To select a specific cell in the table, click in that cell. The properties for the row, column, or cell you selected are displayed in the Properties window. By default, this window is located at the lower-right corner of the interface.
To change the name of a column, click in the column heading and edit the text in the text box. You can also change the font, background color, text color, and many other properties of the text box with the Properties window. Drag the borders of the column to change the column’s size. Reorder the columns by dragging them to the new desired position.
To enable sorting in table columns
1.   Right-click the column to which you want to add sorting, and click Text Box Properties. The Text Box Properties window opens.
2.   Click the Interactive Sorting tab. Select the check box Enable interactive sorting on this text box. You can select to sort by detail rows or by groups. Select the column to sort by, and then click OK.
Note: If you want the report to sort on a particular field by default, add an ORDER BY clause to the query.
Adding a Chart to the Report
Instead of, or in addition to, the table or matrix you may want to include a chart in the report for a visual representation of the data.
To add a chart to the report
1.   You may need to expand the report area to provide sufficient room for the chart by using the resize handles.
2.   Click View, and then click Toolbox. The toolbox dialog box opens; you may want to pin the toolbox in place. In the toolbox, click Chart, and then click in the report to place the chart, or drag to size the chart in the report space.
3.   The Select Chart Type dialog box appears, giving you various chart choices. Select the type of chart you want to add, and then click OK. The chart appears on the design surface.
4.   Drag the chart in the report to move it or use the resize controls to resize it.
5.   Click the area labeled Axis Title to change the text on the axis.
6.   To add data fields to the report, select the Report Data pane (click View, and then Report Data if the Report Data pane is no longer visible), and expand the dataset to show the data fields the query retrieves. On the design surface, click the chart that you added. This reveals three areas around the border of the chart as follows:
a.   Drop data fields here: Drag data fields here that you want to represent as values in the chart (for example, the height of the bars in a bar graph).
b.   Drop category fields here: Drag data fields here for which you want to present the values (for example, the items on the x-axis in a bar graph).
c.   Drop series fields here: These fields are optional. Drag data fields here to add an extra dimension to the chart (for example, if a bar graph has multiple data fields for a single category field).
7.   With the chart selected, the Properties window lets you define the properties of the chart itself, such as the colors, borders, and size.

Thursday, March 7, 2013

Using a Report Builder


After you have a query that retrieves the data that you need, you are ready to create a report. There are several tools that can be used to create a report: Microsoft Business Intelligence Development Studio (BIDS), Microsoft Visual Studio, Report Builder, or Microsoft Excel. This guide uses BIDS because it is already installed with Microsoft SQL Server and integrates seamlessly with Microsoft SQL Server Reporting Services (SSRS).
Creating a New Report Project
The easiest way to create a new report is to use the report wizard, which creates a simple report and populates it with a basic data display that you select. You can also create a report server project, which creates a blank report project that you then populate with a report and the data that you want to display.
To create a new report project by using the report wizard
1.   Open BIDS, click File, click New, and then click Project.
2.   In the New Project window, in the Project Types pane, make sure that Business Intelligence Projects is selected. In the Templates pane, select Report Server Project Wizard. Enter a name for the project, and then click OK.
3.   The Report Wizard starts. On the welcome page, click Next.
4.   On the Select the Data Source page, enter DataWarehouseMain as the name, leave the Type as Microsoft SQL Server, and make sure that you select the Make this a shared data source check box. Click the Edit button.
5.   The Connection Properties dialog box appears. In the Server Name field, enter the name of the server. In the Log on to the server box, enter the appropriate credentials, as discussed in Setting up the Environment. In the Connect to a database box, select the Select or enter a database name option. In the drop-down box, select the OperationsManagerDW database, and then click OK. The wizard will reappear with the Connection String box filled in. Click Next.
6.   The Design the Query page of the wizard appears. In the Query string box, if you have created the query already, as described in Creating Custom Queries, paste the query into the Query String field. If you have not yet created a query, click the Query Builder button to start the Query Designer.
7.   Within the Query Designer, the default view is the graphical query designer. For more information about how to design a query visually, see the guide to Query Designer (http://go.microsoft.com/fwlink/?LinkID=207899). Click the Edit As Text button to edit the query directly in the window. Click the Import… button to use a query that you saved previously. The ! button runs the query and displays the results in the lower pane of the Query Designer. If the report does not show the data that you expected, you can revise the query and test it without recreating the report. After you have created the query, click OK.
8.   You are returned to the Design the Query page of the wizard. Click Next.
9.   On the Select the Report Type page of the wizard, select Tabular or Matrix. A tabular report returns columns; a matrix report uses an intersection of columns and rows for a more precise view of the data. Click Next.
10.  On the Design the Table page of the wizard, select how you want the data in the table to be organized. The options are as follows:
·      The Page option indicates the fields that appear at the page level of the report.
·      The Group option indicates the fields by which to group the data in the table.
·      The Details option indicates the fields that are displayed in the details section of the table.
To change the order of the fields in any group, select a field, and then click the up button or the down button. You can also accept the defaults by clicking Next.
11.  On the Choose the Table Style page of the wizard there is a list of several styles that affect color and layout choices. Select the visual style you prefer for the table. Click Next.
12.  On the Choose the Deployment Location page of the wizard, select where the report will be deployed. By default, the URL for the Operations Manager reporting server is entered. However, you should confirm that this URL is correct. Enter a name for the Deployment folder or accept the default.
13.  On the Completing the Wizard page, enter a name for the report. This will be displayed on the report page. You can review the report summary data on this page. If you want to adjust any of the settings, click the Back button and make the appropriate changes. If you select the Preview report check box, the editor will open in the Preview tab instead of the Design tab. Click Finish to continue.
14.  The basic layout of the report appears in the main window of BIDS. You will see the following two tabs:
·      The Design tab, which shows the layout of the report with the fields returned from the query in place
·      The Preview tab, which shows what the data looks like in the report

To create a report without using the report wizard
1.   Open BIDS, click File, and then click New Project.
2.   In the New Project window, in the Project Types pane, make sure that Business Intelligence Projects is selected. In the Templates pane, select Report Server Project. Enter a name for the project, and then click OK.
3.   The project is created, but still shows the Start page as there is no report in the project yet. In the menu bar, click Project, and then click Add New Item. The Add New Item dialog box appears. In the Templates pane, select Report, and then click Add. The design surface appears in the main window with the Design tab selected, which shows a blank report.
4.   You must add a data source and a dataset to your report in order to display any data. In the Report Data pane, click New, and then click Data Source. The Data Source Properties dialog box appears. Provide a name for the data source (DataWarehouseMain is recommended) or accept the default. If you have not created a shared data source, select Embedded connection; for the Type, select Microsoft SQL Server, and for the Connection string enter the connection information for the OperationsManagerDW database. If you created a shared data source previously, as discussed in Setting up the Environment, select Use shared data source reference, and then select the shared data source in the box. Click OK.
5.   In the Report Data pane, click New, and then click Dataset. Enter a name for the dataset or use the default. Select the Data source, usually DataWarehouseMain, and then enter the query. This can either a query created earlier, or click the Query Designer button and create the query using the Graphical Query Designer. When you have finished, click OK.
6.   The dataset appears in the Report Data window with the available dataset fields retrieved by the query displayed below the dataset name.
7.   Click View, and then click Toolbox to display the Toolbox dialog box. The Toolbox contains several standard items that can be used in reports. From the Toolbox, select a Table, Matrix, Chart, or Gauge, depending on how you want to represent the data, and drag it onto the design surface of the report. From the Report Data window, drag the desired fields onto the Table, Matrix, Chart, or Gauge tool, as appropriate.
8.   Check the appearance of the report by clicking the Preview tab.

The Performance Report


The Performance Report

The Performance report is similar to the Availability report in that it retrieves data for a specified time period on specific entities and retrieves the information from various views. The purpose of the Performance report is to report on the change of a value over time.
The query retrieves some basic information from the vPerfDaily view, which, in this query, has the alias of vPerf:
SELECT  
vPerf.DateTime,
vPerf.SampleCount,
vPerf.AverageValue,
vPerf.MinValue,
vPerf.MaxValue,
vPerf.StandardDeviation,
The query also retrieves the performance rules located in the vPerformanceRuleInstance view:
vPerformanceRuleInstance.RuleRowId,
vPerformanceRuleInstance.InstanceName,
As in the other queries, data is retrieved from the vManagedEntity view, in particular the ManagedEntityRowId, although the GUID, default name, and path are also retrieved:
vManagedEntity.ManagedEntityRowId,
vManagedEntity.ManagedEntityGuid,
vManagedEntity.ManagedEntityDefaultName,
vManagedEntity.Path,
As in the Availability query, the query retrieves a display name if it exists:
ISNULL(vDisplayString.Name,vManagedEntityType.ManagedEntityTypeDefaultName)
AS DisplayName,
To display management group information, the query accesses the vManagementGroup view:
vManagementGroup.ManagementGroupGuid,
vManagementGroup.ManagementGroupDefaultName,
The query also accesses the vRule and vPerformanceRule views:
vRule.RuleGuid,
ISNULL(vDisplayStringRule.Name,vRule.RuleDefaultName) AS RuleDisplayName,
vPerformanceRule.MultiInstanceInd,
The query also retrieves group information from the temporary table #OptionList:
OptionList.[Group],
OptionList.GroupTitle,
OptionList.Position,
OptionList.ChartScale,
OptionList.ChartType,
OptionList.ChartColor,
OptionList.OptionXml,
vManagedEntityTypeImage.Image
The FROM clause in the Performance query is more complex than in the Alert or Availability queries. It begins with the information retrieved from vPerfDaily:
FROM Perf.vPerfDaily as vPerf
The query joins that to the performance rule view, using PerformanceRuleInstanceRowId as the foreign key:
INNER JOIN   vPerformanceRuleInstance
ON vPerformanceRuleInstance.PerformanceRuleInstanceRowId = vPerf.PerformanceRuleInstanceRowId
The query then joins that to the vManagedEntity view, again using ManagedEntityRowId as the key:
INNER JOIN   vManagedEntity
ON vPerf.ManagedEntityRowId = vManagedEntity.ManagedEntityRow
Once joined to the vManagedEntity view, the query joins to the vManagedEntityType view to retrieve the type for the managed entity:
INNER JOIN   vManagedEntityType
ON vManagedEntityType.ManagedEntityTypeRowId = vManagedEntity.ManagedEntityTypeRowId

The query also joins to the vManagementGroup view using the ManagementGroupRowId as the key:
INNER JOIN   vManagementGroup
ON vManagementGroup.ManagementGroupRowId = vManagedEntity.ManagementGroupRowId
To retrieve performance information, the query needs to join the vRule and vPerformanceRule views to the vPerformanceRuleInstance view using the RuleRowId as the key in each case.
INNER JOIN   vRule
ON vPerformanceRuleInstance.RuleRowId = vRule.RuleRowId
INNER JOIN   vPerformanceRule
ON vPerformanceRuleInstance.RuleRowId = vPerformanceRule.RuleRowId
The query needs to join to the #InstanceList:
INNER JOIN   #InstanceList AS InstanceList
ON (vPerformanceRuleInstance.PerformanceRuleInstanceRowId = InstanceList.PerformanceRuleInstanceRowId)
The query needs to join to the #OptionList:
INNER JOIN   #OptionList As OptionList
ON (InstanceList.Position = OptionList.Position)
Finally, the query joins the ObjectList to the InstanceList and to the vManagedEntity view using the ManagedEntityRowId as the key:
INNER JOIN   #ObjectList AS ObjectList
ON (InstanceList.Position = ObjectList.Position)
AND (vManagedEntity.ManagedEntityRowId = ObjectList.ManagedEntityRowId)
The query then retrieves the image to use for the entity type:
LEFT OUTER JOIN  vManagedEntityTypeImage
ON vManagedEntity.ManagedEntityTypeRowId = vManagedEntityTypeImage.ManagedEntityTypeRowId
AND  vManagedEntityTypeImage.ImageCategory = N'u16x16Icon'
Finally, the query joins the vDisplayString and vDisplayStringRule views to retrieve the necessary display strings for the report. The @LanguageCode is a parameter specified by the report designer.
LEFT OUTER JOIN   vDisplayString
ON vManagedEntityType.ManagedEntityTypeGuid = vDisplayString.ElementGuid
AND vDisplayString.LanguageCode = @LanguageCode

LEFT OUTER JOIN  vDisplayString vDisplayStringRule
ON vRule.RuleGuid = vDisplayStringRule.ElementGuid
AND vDisplayStringRule.LanguageCode = @LanguageCode
The WHERE clause is similar to the one in the Availability report. It retrieves all the data that falls between the two dates specified in the date picker:
WHERE   (vPerf.DateTime >= DATEADD(hh, DATEPART(hh, @StartDate), convert(varchar(8), @StartDate, 112)))
AND (vPerf.DateTime < DATEADD(hh, DATEPART(hh, @EndDate), convert(varchar(8), @EndDate, 112)))

The important points to note in this query are that the ManagedEntityRowId is a useful foreign key, and the format of the WHERE clause is similar to that used in the Availability report.
Here’s what the complete query looks like
SELECT  
vPerf.DateTime,
vPerf.SampleCount,
vPerf.AverageValue,
vPerf.MinValue,
vPerf.MaxValue,
vPerf.StandardDeviation,
vPerformanceRuleInstance.RuleRowId,
vPerformanceRuleInstance.InstanceName,
vManagedEntity.ManagedEntityRowId,
vManagedEntity.ManagedEntityGuid,
vManagedEntity.ManagedEntityDefaultName,
vManagedEntity.Path,
ISNULL(vDisplayString.Name,vManagedEntityType.ManagedEntityTypeDefaultName)
AS DisplayName,
vManagementGroup.ManagementGroupGuid,
vManagementGroup.ManagementGroupDefaultName,
vRule.RuleGuid,
ISNULL(vDisplayStringRule.Name,vRule.RuleDefaultName) AS RuleDisplayName,
vPerformanceRule.MultiInstanceInd,
OptionList.[Group],
OptionList.GroupTitle,
OptionList.Position,
OptionList.ChartScale,
OptionList.ChartType,
OptionList.ChartColor,
OptionList.OptionXml,
vManagedEntityTypeImage.Image
FROM     Perf.vPerfDaily as vPerf
INNER JOIN   vPerformanceRuleInstance
ON vPerformanceRuleInstance.PerformanceRuleInstanceRowId = vPerf.PerformanceRuleInstanceRowId
INNER JOIN   vManagedEntity
ON vPerf.ManagedEntityRowId = vManagedEntity.ManagedEntityRowId
INNER JOIN   vManagedEntityType
ON vManagedEntityType.ManagedEntityTypeRowId = vManagedEntity.ManagedEntityTypeRowId
INNER JOIN   vManagementGroup
ON vManagementGroup.ManagementGroupRowId = vManagedEntity.ManagementGroupRowId
INNER JOIN   vRule
ON vPerformanceRuleInstance.RuleRowId = vRule.RuleRowId
INNER JOIN   vPerformanceRule
ON vPerformanceRuleInstance.RuleRowId = vPerformanceRule.RuleRowId
INNER JOIN   #InstanceList AS InstanceList
ON (vPerformanceRuleInstance.PerformanceRuleInstanceRowId = InstanceList.PerformanceRuleInstanceRowId)
INNER JOIN   #OptionList As OptionList
ON (InstanceList.Position = OptionList.Position)
INNER JOIN   #ObjectList AS ObjectList
ON (InstanceList.Position = ObjectList.Position)
AND (vManagedEntity.ManagedEntityRowId = ObjectList.ManagedEntityRowId)
LEFT OUTER JOIN  vManagedEntityTypeImage
ON vManagedEntity.ManagedEntityTypeRowId = vManagedEntityTypeImage.ManagedEntityTypeRowId
AND  vManagedEntityTypeImage.ImageCategory = N'u16x16Icon'
LEFT OUTER JOIN   vDisplayString
ON vManagedEntityType.ManagedEntityTypeGuid = vDisplayString.ElementGuid
AND vDisplayString.LanguageCode = @LanguageCode
LEFT OUTER JOIN  vDisplayString vDisplayStringRule
ON vRule.RuleGuid = vDisplayStringRule.ElementGuid
AND vDisplayStringRule.LanguageCode = @LanguageCode
WHERE   (vPerf.DateTime >= DATEADD(hh, DATEPART(hh, @StartDate), convert(varchar(8), @StartDate, 112)))
AND (vPerf.DateTime < DATEADD(hh, DATEPART(hh, @EndDate), convert(varchar(8), @EndDate, 112)))