Report of every user for every database on server

For auditing purposes, I create a list of all the users who have access to
my databases. I do this by issuing this:
exec sp_MSForEachDB sp_helpuser
However, this doesn't include the name of the database that the list of
users is for. How can I include this info?
Thanks."Joshua Campbell" <Joshua.Campbell@.nospam.nospam> wrote in message
news:%23vGdjyRmFHA.2080@.TK2MSFTNGP10.phx.gbl...
> For auditing purposes, I create a list of all the users who have access to
> my databases. I do this by issuing this:
> exec sp_MSForEachDB sp_helpuser
> However, this doesn't include the name of the database that the list of
> users is for. How can I include this info?
> Thanks.
>
I use some dynamic sql and a cursor for this. In Query Analyzer, set your
output to Text (as opposed to grid).
BEGIN
SET NOCOUNT ON
-- Create some variables
DECLARE @.currentdb sysname, -- Current database that we are working with
@.sql varchar(4000) -- Dynamic SQL statement
-- Load the cursor with the current list of database names. Exclude SQL
Server databases.
DECLARE dbnames CURSOR FOR
SELECT [name]
FROM master.dbo.sysdatabases
WHERE [name] NOT IN ('master', 'model', 'msdb', 'tempdb', 'Northwind',
'pubs')
ORDER BY [name] ASC
-- For each database, perform your query
OPEN dbnames
FETCH NEXT
FROM dbnames
INTO @.currentdb
WHILE @.@.FETCH_STATUS = 0
BEGIN
-- The @.sql statement should be in the form of:
SET @.sql = @.currentdb + '.dbo.sp_helpuser'
-- Print a header to the messages tab
PRINT '=======================================
=================='
PRINT @.currentdb
PRINT ''
-- Execute the sql statement
EXECUTE(@.sql)
PRINT ''
PRINT '=======================================
=================='
PRINT ''
PRINT ''
-- Get the next database name
FETCH NEXT
FROM dbnames
INTO @.currentdb
END
-- Cleanup
CLOSE dbnames
DEALLOCATE dbnames
END
Rick Sawtell|||Nice script! However, it seems to have an issue with databases that begin
with the number zero (0). I get the folowing error:
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near '0'.
Any ideas?
Thanks.|||"Joshua Campbell" <Joshua.Campbell@.nospam.nospam> wrote in message
news:uykxweSmFHA.572@.TK2MSFTNGP15.phx.gbl...
> Nice script! However, it seems to have an issue with databases that begin
> with the number zero (0). I get the folowing error:
> Server: Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near '0'.
> Any ideas?
> Thanks.
>
Ummm.. Find a better naming convention.. <wink>
I was under the impression that all object qualifiers in SQL Server 2000
require a letter as the first character, followed by numbers and some
symbols...
Guess I was wrong.
You could modify the script to include the square brackets. That may fix
it.
So adjust as follows:
Old line
SET @.sql = @.currentdb + '.dbo.sp_helpuser'
New line
SET @.sql = '[' + @.currentdb + '].dbo.sp_helpuser'
I should have probably done that in the first place for those who insist on
putting spaces etc. in their naming conventions.
Rick Sawtell|||Use QUOTENAME(@.currentdb) instead of @.currentdb
Steve Kass
Drew University
Joshua Campbell wrote:

>Nice script! However, it seems to have an issue with databases that begin
>with the number zero (0). I get the folowing error:
>Server: Msg 170, Level 15, State 1, Line 1
>Line 1: Incorrect syntax near '0'.
>Any ideas?
>Thanks.
>
>|||It's not sufficient. Because I had to something very similar but including
all the permissions per each user using sp_helpuser
"Steve Kass" wrote:

> Use QUOTENAME(@.currentdb) instead of @.currentdb
> Steve Kass
> Drew University
> Joshua Campbell wrote:
>
>|||I'm sorry, but I don't understand you. If there is problem with
QUOTENAME, could you show sample code where it doesn't
work as expected?
SK
Enric wrote:
>It's not sufficient. Because I had to something very similar but including
>all the permissions per each user using sp_helpuser
>"Steve Kass" wrote:
>
>

Report Model is generating without data

I have been generating report models for users to use with Report Builder and there is no data when they select the model. I noticed that the tables I chose did not have a primary key and when I chose a different table, with a primary key, and generated a model from it, then there was data for the user to use in Report Builder.

Is there a documented work around or will I need to set a primary key on each table?

You don't need a physical PK on each of your tables. Instead, open up the DSV in your Report Model project, right click each table, and choose "Set Logical Primary Key" and the appropriate field. You'll then need to rebuild the model. See if this works for you!|||Thanks Russell! That worked just fine after I rebuilt the model.

Report Model Generating Out of Memory Error

I am creating a report model of a large database with a few hundred tables, the idea being that the users can report on any part of the database and create perspectives for the areas they want users to have access to (In the past the users have moaned about report models in a CA product called Eureka as the models are too small, perspectives seemed a way of allowing one large model but limiting each perspective to a set of users?). Unfortunately presumably due to the size of the model visual studio is giving me an out of memory error when adding new tables. I have a two dual core xeons with 4Gig of ram and I'm running XP Pro 64bit with the developer edition of 2005 with service pack 1 and VS2005 is using around 1/2 a Gb. Is this a known issue and will there be a work around?

Seems to occur when removing anything from the report model. Can reproduce by deleting calculated fields and selecting save.|||This sounds like a bug. Can you describe a list of steps that would repro the issue?|||Its fairly simple I only have to delete a few fields or tables from my report model and it triggers an out of memory error. I can forward the report model if thats helpful? I would like to regenerate the fields from the report model by using the autogenerate/get rid of some of the autogenerated calculated fields bu can't as I get this error each time.|||

yes, the model and the list of steps would help almineev tata microsoft todtod moc

|||

Alexandre Mineev MSFT wrote:

yes, the model and the list of steps would help almineev tata microsoft todtod moc

? noticed the error location button so heres some more info, pls contact direct when you need the model and files, you should have my email. Cool signature!

===================================

Exception of type 'System.OutOfMemoryException' was thrown. (Microsoft Visual Studio)

Program Location:

at System.String.GetStringForStringBuilder(String value, Int32 startIndex, Int32 length, Int32 capacity)
at System.Text.StringBuilder.GetNewString(String currentString, Int32 requiredLength)
at System.Text.StringBuilder.Append(Char value)
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.BufferTextWriter.Write(Char ch)
at System.IO.TextWriter.Write(Char[] buffer, Int32 index, Int32 count)
at System.Xml.XmlEncodedRawTextWriter.FlushBuffer()
at System.Xml.XmlEncodedRawTextWriter.RawText(Char* pSrcBegin, Char* pSrcEnd)
at System.Xml.XmlEncodedRawTextWriter.RawText(String s)
at System.Xml.XmlEncodedRawTextWriterIndent.WriteIndent()
at System.Xml.XmlEncodedRawTextWriterIndent.WriteStartElement(String prefix, String localName, String ns)
at System.Xml.XmlWellFormedWriter.WriteStartElement(String prefix, String localName, String ns)
at System.Xml.XmlWriter.WriteStartElement(String localName, String ns)
at Microsoft.ReportingServices.Modeling.AttributeRefNode.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.Expression.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.Expression.Microsoft.ReportingServices.Modeling.IXmlWriteable.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelingXmlWriter.WriteCollectionElement[T](String elementName, ICollection`1 items)
at Microsoft.ReportingServices.Modeling.FunctionNode.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.Expression.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelAttribute.WriteXmlElements(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.Microsoft.ReportingServices.Modeling.IXmlWriteable.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelingXmlWriter.WriteCollectionElement[T](String elementName, ICollection`1 items)
at Microsoft.ReportingServices.Modeling.ModelAttribute.WriteXmlElements(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.Microsoft.ReportingServices.Modeling.IXmlWriteable.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelingXmlWriter.WriteCollectionElement[T](String elementName, ICollection`1 items)
at Microsoft.ReportingServices.Modeling.ModelEntity.WriteXmlElements(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.Microsoft.ReportingServices.Modeling.IXmlWriteable.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelingXmlWriter.WriteCollectionElement[T](String elementName, ICollection`1 items)
at Microsoft.ReportingServices.Modeling.ModelEntityFolder.WriteXmlElements(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.Microsoft.ReportingServices.Modeling.IXmlWriteable.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelingXmlWriter.WriteCollectionElement[T](String elementName, ICollection`1 items)
at Microsoft.ReportingServices.Modeling.SemanticModel.WriteXmlElements(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.SemanticModel.WriteTo(XmlWriter xw, ModelingSerializationOptions options)
at Microsoft.ReportingServices.ModelDesigner.Serialization.ModelDesignerSerializer.SerializeComponent(IDesignerSerializationManager manager, IComponent component, Object serializationStream)
at Microsoft.DataWarehouse.Serialization.DesignerComponentSerializer.Serialize(IDesignerSerializationManager manager, Object value)
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.DataWarehouseDesignerLoader.Serialize()
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.BaseDesignerLoader.Flush(Boolean forceful)
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.BaseDesignerLoader.Flush()
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.DataWarehouseContainerManager.OnBeforeSave(UInt32 docCookie)

|||Hi Phil, I did not get an email from you|||Where do I send the email?|||almineev tata microsoft todtod moc

Report Model Generating Out of Memory Error

I am creating a report model of a large database with a few hundred tables, the idea being that the users can report on any part of the database and create perspectives for the areas they want users to have access to (In the past the users have moaned about report models in a CA product called Eureka as the models are too small, perspectives seemed a way of allowing one large model but limiting each perspective to a set of users?). Unfortunately presumably due to the size of the model visual studio is giving me an out of memory error when adding new tables. I have a two dual core xeons with 4Gig of ram and I'm running XP Pro 64bit with the developer edition of 2005 with service pack 1 and VS2005 is using around 1/2 a Gb. Is this a known issue and will there be a work around?

Seems to occur when removing anything from the report model. Can reproduce by deleting calculated fields and selecting save.|||This sounds like a bug. Can you describe a list of steps that would repro the issue?|||Its fairly simple I only have to delete a few fields or tables from my report model and it triggers an out of memory error. I can forward the report model if thats helpful? I would like to regenerate the fields from the report model by using the autogenerate/get rid of some of the autogenerated calculated fields bu can't as I get this error each time.|||

yes, the model and the list of steps would help almineev tata microsoft todtod moc

|||

Alexandre Mineev MSFT wrote:

yes, the model and the list of steps would help almineev tata microsoft todtod moc

? noticed the error location button so heres some more info, pls contact direct when you need the model and files, you should have my email. Cool signature!

===================================

Exception of type 'System.OutOfMemoryException' was thrown. (Microsoft Visual Studio)

Program Location:

at System.String.GetStringForStringBuilder(String value, Int32 startIndex, Int32 length, Int32 capacity)
at System.Text.StringBuilder.GetNewString(String currentString, Int32 requiredLength)
at System.Text.StringBuilder.Append(Char value)
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.BufferTextWriter.Write(Char ch)
at System.IO.TextWriter.Write(Char[] buffer, Int32 index, Int32 count)
at System.Xml.XmlEncodedRawTextWriter.FlushBuffer()
at System.Xml.XmlEncodedRawTextWriter.RawText(Char* pSrcBegin, Char* pSrcEnd)
at System.Xml.XmlEncodedRawTextWriter.RawText(String s)
at System.Xml.XmlEncodedRawTextWriterIndent.WriteIndent()
at System.Xml.XmlEncodedRawTextWriterIndent.WriteStartElement(String prefix, String localName, String ns)
at System.Xml.XmlWellFormedWriter.WriteStartElement(String prefix, String localName, String ns)
at System.Xml.XmlWriter.WriteStartElement(String localName, String ns)
at Microsoft.ReportingServices.Modeling.AttributeRefNode.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.Expression.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.Expression.Microsoft.ReportingServices.Modeling.IXmlWriteable.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelingXmlWriter.WriteCollectionElement[T](String elementName, ICollection`1 items)
at Microsoft.ReportingServices.Modeling.FunctionNode.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.Expression.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelAttribute.WriteXmlElements(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.Microsoft.ReportingServices.Modeling.IXmlWriteable.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelingXmlWriter.WriteCollectionElement[T](String elementName, ICollection`1 items)
at Microsoft.ReportingServices.Modeling.ModelAttribute.WriteXmlElements(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.Microsoft.ReportingServices.Modeling.IXmlWriteable.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelingXmlWriter.WriteCollectionElement[T](String elementName, ICollection`1 items)
at Microsoft.ReportingServices.Modeling.ModelEntity.WriteXmlElements(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.Microsoft.ReportingServices.Modeling.IXmlWriteable.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelingXmlWriter.WriteCollectionElement[T](String elementName, ICollection`1 items)
at Microsoft.ReportingServices.Modeling.ModelEntityFolder.WriteXmlElements(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.Microsoft.ReportingServices.Modeling.IXmlWriteable.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelingXmlWriter.WriteCollectionElement[T](String elementName, ICollection`1 items)
at Microsoft.ReportingServices.Modeling.SemanticModel.WriteXmlElements(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.SemanticModel.WriteTo(XmlWriter xw, ModelingSerializationOptions options)
at Microsoft.ReportingServices.ModelDesigner.Serialization.ModelDesignerSerializer.SerializeComponent(IDesignerSerializationManager manager, IComponent component, Object serializationStream)
at Microsoft.DataWarehouse.Serialization.DesignerComponentSerializer.Serialize(IDesignerSerializationManager manager, Object value)
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.DataWarehouseDesignerLoader.Serialize()
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.BaseDesignerLoader.Flush(Boolean forceful)
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.BaseDesignerLoader.Flush()
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.DataWarehouseContainerManager.OnBeforeSave(UInt32 docCookie)

|||Hi Phil, I did not get an email from you|||Where do I send the email?|||almineev tata microsoft todtod moc

Report Model Generating Out of Memory Error

I am creating a report model of a large database with a few hundred tables, the idea being that the users can report on any part of the database and create perspectives for the areas they want users to have access to (In the past the users have moaned about report models in a CA product called Eureka as the models are too small, perspectives seemed a way of allowing one large model but limiting each perspective to a set of users?). Unfortunately presumably due to the size of the model visual studio is giving me an out of memory error when adding new tables. I have a two dual core xeons with 4Gig of ram and I'm running XP Pro 64bit with the developer edition of 2005 with service pack 1 and VS2005 is using around 1/2 a Gb. Is this a known issue and will there be a work around?

Seems to occur when removing anything from the report model. Can reproduce by deleting calculated fields and selecting save.|||This sounds like a bug. Can you describe a list of steps that would repro the issue?|||Its fairly simple I only have to delete a few fields or tables from my report model and it triggers an out of memory error. I can forward the report model if thats helpful? I would like to regenerate the fields from the report model by using the autogenerate/get rid of some of the autogenerated calculated fields bu can't as I get this error each time.|||

yes, the model and the list of steps would help almineev tata microsoft todtod moc

|||

Alexandre Mineev MSFT wrote:

yes, the model and the list of steps would help almineev tata microsoft todtod moc

? noticed the error location button so heres some more info, pls contact direct when you need the model and files, you should have my email. Cool signature!

===================================

Exception of type 'System.OutOfMemoryException' was thrown. (Microsoft Visual Studio)

Program Location:

at System.String.GetStringForStringBuilder(String value, Int32 startIndex, Int32 length, Int32 capacity)
at System.Text.StringBuilder.GetNewString(String currentString, Int32 requiredLength)
at System.Text.StringBuilder.Append(Char value)
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.BufferTextWriter.Write(Char ch)
at System.IO.TextWriter.Write(Char[] buffer, Int32 index, Int32 count)
at System.Xml.XmlEncodedRawTextWriter.FlushBuffer()
at System.Xml.XmlEncodedRawTextWriter.RawText(Char* pSrcBegin, Char* pSrcEnd)
at System.Xml.XmlEncodedRawTextWriter.RawText(String s)
at System.Xml.XmlEncodedRawTextWriterIndent.WriteIndent()
at System.Xml.XmlEncodedRawTextWriterIndent.WriteStartElement(String prefix, String localName, String ns)
at System.Xml.XmlWellFormedWriter.WriteStartElement(String prefix, String localName, String ns)
at System.Xml.XmlWriter.WriteStartElement(String localName, String ns)
at Microsoft.ReportingServices.Modeling.AttributeRefNode.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.Expression.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.Expression.Microsoft.ReportingServices.Modeling.IXmlWriteable.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelingXmlWriter.WriteCollectionElement[T](String elementName, ICollection`1 items)
at Microsoft.ReportingServices.Modeling.FunctionNode.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.Expression.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelAttribute.WriteXmlElements(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.Microsoft.ReportingServices.Modeling.IXmlWriteable.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelingXmlWriter.WriteCollectionElement[T](String elementName, ICollection`1 items)
at Microsoft.ReportingServices.Modeling.ModelAttribute.WriteXmlElements(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.Microsoft.ReportingServices.Modeling.IXmlWriteable.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelingXmlWriter.WriteCollectionElement[T](String elementName, ICollection`1 items)
at Microsoft.ReportingServices.Modeling.ModelEntity.WriteXmlElements(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.Microsoft.ReportingServices.Modeling.IXmlWriteable.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelingXmlWriter.WriteCollectionElement[T](String elementName, ICollection`1 items)
at Microsoft.ReportingServices.Modeling.ModelEntityFolder.WriteXmlElements(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.Microsoft.ReportingServices.Modeling.IXmlWriteable.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelingXmlWriter.WriteCollectionElement[T](String elementName, ICollection`1 items)
at Microsoft.ReportingServices.Modeling.SemanticModel.WriteXmlElements(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.ModelItem.WriteTo(ModelingXmlWriter xw)
at Microsoft.ReportingServices.Modeling.SemanticModel.WriteTo(XmlWriter xw, ModelingSerializationOptions options)
at Microsoft.ReportingServices.ModelDesigner.Serialization.ModelDesignerSerializer.SerializeComponent(IDesignerSerializationManager manager, IComponent component, Object serializationStream)
at Microsoft.DataWarehouse.Serialization.DesignerComponentSerializer.Serialize(IDesignerSerializationManager manager, Object value)
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.DataWarehouseDesignerLoader.Serialize()
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.BaseDesignerLoader.Flush(Boolean forceful)
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.BaseDesignerLoader.Flush()
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.DataWarehouseContainerManager.OnBeforeSave(UInt32 docCookie)

|||Hi Phil, I did not get an email from you|||Where do I send the email?|||almineev tata microsoft todtod moc

Report Manager Site Title Isn't Visible For Some Users

The Report Manager site title (default "SQL Server Reporting Services")
isn't visible for some users. It may be coincidental that only admins can
see it.
TIAUsers must have "View Site Properties" right.
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23ZVgpCz3FHA.2504@.TK2MSFTNGP10.phx.gbl...
> The Report Manager site title (default "SQL Server Reporting Services")
> isn't visible for some users. It may be coincidental that only admins can
> see it.
> TIA
>

Report Manager Default Look

People are really very happy with the reports I'm creating using SQL 2005
Reporting Services. Great stuff!
One question though. When users go to the Report Manager:
http://MyServer/Reports/Pages/Report.aspx
They see "SQL Server Reporting Services" at the top of the form. Is there
any way to change that to a company name and perhaps a jpg company logo?
Thanks,
--
RandyYes, click on the Site link at the upper right hand side and change the
wording.
Next, from what I understand, you can change the site -> just take a look at
the CSS files in the ReportManager folder under: C:\Program Files\Microsoft
SQL Server\MSSQL.2\Reporting Services\ReportManager
Mine is stored under MSSQL.2 - but you might be using MSSQL.1 -> just look
around.
You will probably want to change the style sheet located under the Styles
folder.
Put your logo into the images folder.
=-Chris
"randy1200" <randy1200@.newsgroups.nospam> wrote in message
news:01EFDDDC-14C3-478A-B1D0-0886433470F7@.microsoft.com...
> People are really very happy with the reports I'm creating using SQL 2005
> Reporting Services. Great stuff!
> One question though. When users go to the Report Manager:
> http://MyServer/Reports/Pages/Report.aspx
> They see "SQL Server Reporting Services" at the top of the form. Is there
> any way to change that to a company name and perhaps a jpg company logo?
> Thanks,
> --
> Randy|||Hmm, I don't see a "site" link on my installation of SQL Reporting Services
2005, are there other instructions for customizing the sql report server home
page? In particular I want to add a block of text describing how people can
request to join a particular Microsoft security group to view certain reports.

Report manager

Hello,

How can I make my sub-reports invisible in the report manager, I do not want users click them and try to run.

Thanks,

There are some basic security features. It is possible to limit access to certain roles. There's plenty of info here: Thttp://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_security_v1_3hia.asp

Report Hit Counts

This is gonna be simple - but not for me!!
I need to record the number of hits each report gets from users. As a bonus,
also the parameter values passed would be usefull also.
What would be the simplist and most efficient way of achieving the above
please.
Thanks and Happy New Year
TonyThe report server automatically logs all Report Executions. Look at the
Execution Log table. More info can be found here:
http://msdn2.microsoft.com/en-us/library/ms155836.aspx
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tony Scott" <TonyScott@.discussions.microsoft.com> wrote in message
news:43FF9683-CA87-414F-890A-5D1F310F8E5B@.microsoft.com...
> This is gonna be simple - but not for me!!
> I need to record the number of hits each report gets from users. As a
> bonus,
> also the parameter values passed would be usefull also.
> What would be the simplist and most efficient way of achieving the above
> please.
> Thanks and Happy New Year
> Tony|||More than what Daniel has said, there is a sample package with reports, and
SSIS package which parses the logs, moves the data into a table, and provides
about 6 reports against them... It is exactly what you need.
Look for it in the samples for SQL..
(The reports are really nice!>)
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"Tony Scott" wrote:
> This is gonna be simple - but not for me!!
> I need to record the number of hits each report gets from users. As a bonus,
> also the parameter values passed would be usefull also.
> What would be the simplist and most efficient way of achieving the above
> please.
> Thanks and Happy New Year
> Tony

Report Headers in Report Services

Is there a way to "freeze" the report headers in Report Services? I'd like to have it work like Excel does when you freeze panes. My users complain that when they scroll down the report page, they lose the column headers and lose track of which column is which.

In your Layout section for table settings properties. Set the FixedHeader setting to True to keep the headers visible as you scroll down

|||

So-called fixed headers are available starting with Reporting Services 2005.

They are supported for matrix (see: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=167377&SiteID=1) and table.

Matrix: you can either have it on the row groups or column groups.

Table:
a) you can have a fixed table header (select it in the table properties dialog)
b) or you can have left-most or right-most fixed table columns (select an entire table column, and look for the "FixedHeader" property in the VS properties window of report designer).

-- Robert

|||

HI Robert,

I want to create a report with SQL Server Reporting Service 2000 where I need to have a fixed header and one fixed coloumn containg names of row items. I tried to find "Fixed Header" property in table region of toolbox but could not locate it anywhere.Can you please kindly tell me where should i look for it?

Thank you in advance.

Bharat Gadhia.

Report Headers in Report Services

Is there a way to "freeze" the report headers in Report Services? I'd like to have it work like Excel does when you freeze panes. My users complain that when they scroll down the report page, they lose the column headers and lose track of which column is which.

In your Layout section for table settings properties. Set the FixedHeader setting to True to keep the headers visible as you scroll down

|||

So-called fixed headers are available starting with Reporting Services 2005.

They are supported for matrix (see: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=167377&SiteID=1) and table.

Matrix: you can either have it on the row groups or column groups.

Table:
a) you can have a fixed table header (select it in the table properties dialog)
b) or you can have left-most or right-most fixed table columns (select an entire table column, and look for the "FixedHeader" property in the VS properties window of report designer).

-- Robert

|||

HI Robert,

I want to create a report with SQL Server Reporting Service 2000 where I need to have a fixed header and one fixed coloumn containg names of row items. I tried to find "Fixed Header" property in table region of toolbox but could not locate it anywhere.Can you please kindly tell me where should i look for it?

Thank you in advance.

Bharat Gadhia.

|||In the Grouping and Sorting Properties pop-up window that you get to when you click on Edit Group, that is where you will find (under the General tab) the following check box:
"Group header should remain visible while scrolling."
Note that one of the entries said it is a property of the GROUP.|||HOWEVER, that is in Reporting Services 2005. Also, in a matrix I froze a header on a column group, and in the Preview it was of frozen (although it did not function very elegantly), but when it got over to EXCEL it was not frozen at all. So, does anyone know: can you freeze a column header or row header in a matrix in Reporting Services and have it still be frozen after you EXPORT the report to EXCEL?

Report generation time between users and admin

Hi,

When we generate a report with an account that is in the admin group it takes 2-3 seconds but when we do it with another user it takes over 2 minutes... any reason for this?

(The "Report is being generated" thing, by the way)

Not sure if my question is clear, I've been looking and searching for the past 2 hours but can't find anything remotly close to that problem... any help would be appreaciated!

Thanks

Wacky guess:

Are temp files for the two accounts going to different places, for example there is a "home" drive for normal users that is not local?

>L<

Report Formatting in Excel 2007

I am currently developing a report for users who insist on exporting to Excel 2007. When I export to Excel on my PC, the report formatting is fine (I am using Excel 2003), however, font sizing as applied in the report is lost when exported to Excel 2007 (i.e. font size 9 in the report is actually 10 in excel 2007). In Excel 2007, the data which runs onto two lines does not show up correctly - the second line is squashed below the first.

Any ideas on how I could resolve this?

Strange, I tried on mine but did not experience this. I tried exporting to Excel 2003 and then opening it in Excel 2007 it worked perfectly fine.

Then I also tried extracting the report from a PC which has Excel 2007 and then exporting the report in that PC, even this worked perfectly fine.