VMWare vCenter and Microsoft SQL Server Reporting Services

I know this may be considered weird combination, if you ever need to install VMWare vCenter 4. 0 and MS SQL including Reporting  Service on the same machine (Windows Server 2008 64 Bit), figuring out how to control your emotions. Quote, VMWare could eventually not support this configuration, but My partner and i no difficulty that as much this really is essential.

VMWare vCenter necessitates a SQL database (SQL 2005 or SQL 2008 in the course of this writing). Some people choose to can make use of an online database we were treated to necessity for a nearby installation along with we needed SQL Server Reporting service installed. After installing the Windows based pc we did an entire install of SQL Server 2005 including SP3. We did make it happen with SQL 2008 before, but SQL 2008 is not really using IIS to do the Reporting Services and also that lasted very hard to take care of both the applictions in addition to their ports them to use (hint: overlapping ports are 80 and 443).

After you installed SQL 2005, you may install vSphere vCenter 4. All through the installation you possibly can get new ports that vCenter uses, however this doesn't work. SQL Report Services needs port 443 for internal communication. I did changed the main harbour in vCenter to 444 if you use SQL 2008, but apparently vCenter ignores that port setting but still locks port 443 later one - making Reporting Services kaput. So, install vCenter considering the default ports.

Now begin IIS (hint: SQL 2005 makes it necessary that you put in ALL IIS components in Server 2008) and alter the main harbour towards the reporting services to port 81. You'll want to to the touch port 443 to build MS SQL Reporting Services to the office. Now throw open the Report Services Configuration tool and choose the online market place Service Identity tab. Set the appPool to "Classic. NET" for your Report Server and then the Report Manager.

MS SQL Reporting services should work correctly so you specify the brand new port within the URL when accessing the reports.

Why did SQL 2008 not help me? SQL 2008 Report Services does use HTTPS traffic considerably more than SQL 2005 does. Since VMWare vcenter locks that port (although you may tell it to not ever ), SQL 2008 Reporting Services will not likely function properly. Popular plans . that the is a really higher level view around the problems linked to running VMWare vCenter and MS SQL Reporting Services in the same server.

.

URL Parameters Utilized in Reporting Services

This article tells you probably the most common reporting parameters to implement in Microsoft SQL Server Reporting Services.

When get to the [http://reportserver/reportserver/foldername/reportname]

The last command inside url is & rs: Command=Render

You could add another commands the following:

& rc: Parameters=Collapsed

This collapses the parameter bar but sends the parameters inside the URL within the browser

& rc: Parameters=true

This shows the parameter bar which is the default

& rc: Parameters=false

This prevents the parameters from being passed during the browser and expanded

& rc: toolbar=false

This hides the toolbar

& rc: format=PDF

This will start the report as being a PDF

& rs: Format=EXCEL& rc: OmitFormulas=true

This will open the report in Excel

rs: ClearSession=true

This clears the session state for any user. Used the spot where the caching belonging to the report prevents the designer from seeing their updated report and/or data.

* It's a vital parameter to recognize fat loss often these days, the report data doesn't update immediately unless parameters are changed, and also your report may show cached data via a set. & rc: StyleSheet=MyCustomStyle

Note don’ t add the. css extension. Of which this style sheet are required to be within the folder Program FilesMicrosoft SQL ServerMSSQLReporting ServicesReportServerStyles folder.

Use the HTMLViewer. css because your base template.

ReportServer Parameters:

If you add? /FolderName/ReportName as soon as the [http://servername/reportserver] you possibly can run the report.

The same applies if you would like list the reports, then just type? /FolderName as soon as the [http://servername/reportserver].

This happens to be used if the user merely has permissions along at the folder level, not the main level.

Attachments:

Disclaimer: This post is provided as it is. It is actually intended for a guide only and really should not relied on in production unless extensive testing has become done.

.