custom styles usage

I am amazed that we cannot use our own styles?. There is only a predefined set of styles in HTMViewer.css to which we cannot add our own style names and use it for a textbox?

Has anyone done this?

Thanks

Using Custom Style Sheet in SQL Reporting Services 2000

Changing the style-sheet in SQL Reporting Services is one question that I have seen commonly asked in the forums. Well yes the answer is straight forward but at times some straight answers don’t work :) .

Following is my finding on how to use your own style sheet in Reporting Services:

Prerequisite : SP2 hot fix: http://support.microsoft.com/default.aspx?scid=kb;en-us;901383

Following are the steps for using custom style sheet in Reporting Services:

1. Add <HTMLViewerStyleSheet> element in RSReportServer.config within the <configuration> element.
2. DON’T include the ".css" extension in the name of the style sheet.
3. Example: <HTMLViewerStyleSheet>htmlviewer2</HTMLViewerStyleSheet>

Following is going to fail:
<HTMLViewerStyleSheet>htmlviewer2.css</HTMLViewerStyleSheet>

Following works:
<HTMLViewerStyleSheet>htmlviewer2</HTMLViewerStyleSheet>

Make sure that the style sheet is located in the styles directory of Reporting Services (i.e. C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\Styles).

The default style sheet used by the HTML Viewer uses the font Verdana for displaying labels and dropdown values. Unfortunately, Verdana does not have full Unicode support.
SP2 (with the hot fix at http://support.microsoft.com/default.aspx?scid=kb;en-us;901383) allows you to change the stylesheet that is used by the viewer.

If you want to hide items on the Reporting Services Toolbar, you can do this by customizing each button/item individually by changing the stylesheet. Basically, you just need to change the style display:inline to display:none for the items which you don't want to show/hide on the toolbar.

Hope this should help some of you in using a custom style sheet in Reporting Services.

http://blogs.msdn.com/ketaanhs/default.aspx

cursors CPU usage

h
i started trace and found some procedures running in background
1) sp_cursorope
2) sp_cursorfetch and sp_cursorclose.
wot are these system procedures and it runs after every 2-3 mins and taking too much cpu.
any help would be appreciated
SanjayGenerally, those are SP's used by the MDAC client when a cursor is opened to
retrieve data by an application. Have a look at what application is being
used at the time. Maybe that application needs tuning.
Those 3 are Extended SP's that are shipped with SQL as standard and can not
be changed.
Cheers
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.NOSPAMepprecht.net
Specialist SQL Server Solutions and Consulting
"sanjay" <anonymous@.discussions.microsoft.com> wrote in message
news:59A038C1-4F19-4AD0-8FD2-440ECEDF008E@.microsoft.com...
> hi
> i started trace and found some procedures running in background.
> 1) sp_cursoropen
> 2) sp_cursorfetch and sp_cursorclose..
> wot are these system procedures and it runs after every 2-3 mins and
taking too much cpu..
> any help would be appreciated.
> Sanjay|||hi mike,
i checked the application..but this sp's run continously after every 2-3 mins and there are no background processes running on..
do they utilise cpu..as site is working too slow..
can we avoid them'
regards
sanjay|||These stored procedures are being called on the behalf of
the application. For instance, if your application
executes a query "select field1, field2,... from table1",
the ADO drivers are converting this to the three cursor
stored procedure calls. Essentially what is happening is
that the first one, sp_cursoropen executes the query
storing the results in a server side cursor (sort of a
temp table), and the sequence of sp_cursorfetch's return
the rows to the application on the client side.
sp_cursorclose closes the server side cursor.
This is usually the result of an application written to
use the defaults when populating an ADO recordset. It
becomes very inefficient if you have a large number of
rows to return, since the default is to return one row to
the client for each execution of the sp_cursorfetch
stored proc. If the third parameter for sp_cursorfetch
is 1 (one), then you are seeing this default behavior.
To fix this you would have to recode the application to
use non-default ADO property settings for properties like
cachesize or cursorlocation.
I hope that this helps.
Matthew Bando
BandoM@.CSCTGI(RemoveThis).com
>--Original Message--
>hi mike,
> i checked the application..but this sp's run
continously after every 2-3 mins and there are no
background processes running on..
>do they utilise cpu..as site is working too slow..
>can we avoid them'
>regards
>sanjay
>.
>