I have just set up SQL Reporting Services in our Development environment and
want to set all users with browser or read-only access to our reports but do
not see how. I am going in through the web interface and it tells me that I
must have a valid domain group or interface. Any idea on how to just select
"Everyone"?DomainName\Everyone
ComputerName\Everyone
HTH, Jens Süßmeyer
--
http://www.sqlserver2005.de
--
"Charles Collins" <Charles Collins@.discussions.microsoft.com> schrieb im
Newsbeitrag news:234DF76B-A041-4989-A116-6CADDEB19E9B@.microsoft.com...
>I have just set up SQL Reporting Services in our Development environment
>and
> want to set all users with browser or read-only access to our reports but
> do
> not see how. I am going in through the web interface and it tells me that
> I
> must have a valid domain group or interface. Any idea on how to just
> select
> "Everyone"?|||Currently Reporting Services only supports Windows Authentication. Which
means you need to create a network group (with everyone you want) in it and
then give that network group access to the reports. Reporting Services
security is extensible though if you want to create your own security
extension (Not an easy task). Here is link to a microsoft example of
creating your own security extension...
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp
"Charles Collins" wrote:
> I have just set up SQL Reporting Services in our Development environment and
> want to set all users with browser or read-only access to our reports but do
> not see how. I am going in through the web interface and it tells me that I
> must have a valid domain group or interface. Any idea on how to just select
> "Everyone"?|||When I try that I get:
The user or group name '(domain or computer name)\everyone' is not
recognized. (rsUnknownUserName)
"Jens Sü�meyer" wrote:
> DomainName\Everyone
> ComputerName\Everyone
> HTH, Jens Sü�meyer
> --
> http://www.sqlserver2005.de
> --
> "Charles Collins" <Charles Collins@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:234DF76B-A041-4989-A116-6CADDEB19E9B@.microsoft.com...
> >I have just set up SQL Reporting Services in our Development environment
> >and
> > want to set all users with browser or read-only access to our reports but
> > do
> > not see how. I am going in through the web interface and it tells me that
> > I
> > must have a valid domain group or interface. Any idea on how to just
> > select
> > "Everyone"?
>
>|||Is there an way to assign mulitple users an role at once?
"Jens Sü�meyer" wrote:
> DomainName\Everyone
> ComputerName\Everyone
> HTH, Jens Sü�meyer
> --
> http://www.sqlserver2005.de
> --
> "Charles Collins" <Charles Collins@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:234DF76B-A041-4989-A116-6CADDEB19E9B@.microsoft.com...
> >I have just set up SQL Reporting Services in our Development environment
> >and
> > want to set all users with browser or read-only access to our reports but
> > do
> > not see how. I am going in through the web interface and it tells me that
> > I
> > must have a valid domain group or interface. Any idea on how to just
> > select
> > "Everyone"?
>
>
Showing posts with label read-only. Show all posts
Showing posts with label read-only. Show all posts
Monday, March 19, 2012
Wednesday, March 7, 2012
New indexes not shipped to secondary server
I am running SQL 2k on WinS2003 servers. We are using Log Shipping,
leaving our secondary in a Read-Only state to be used for reporting. I
have a need to get a new index on the secondary server (to decrease the
14 hour run time for a report). Our primary is in Full Recovery mode
as well.
I have created the index on my primary and expected it to be created on
the secondary when the logs were shipped this morning, only to find
that the Index was not created on the secondary.
I am not very familiar with Log Shipping and our in house expert is
unavailable.
Any thoughts on what gives?
I would even take pointers on where to start looking to find the
problem.
Meredith Ryan> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
>
You need the logs shipped AND applied for this to occur.
"mryan" <coffegrl@.gmail.com> wrote in message
news:1143761656.789619.3450@.v46g2000cwv.googlegroups.com...
> I am running SQL 2k on WinS2003 servers. We are using Log Shipping,
> leaving our secondary in a Read-Only state to be used for reporting. I
> have a need to get a new index on the secondary server (to decrease the
> 14 hour run time for a report). Our primary is in Full Recovery mode
> as well.
> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
> I am not very familiar with Log Shipping and our in house expert is
> unavailable.
> Any thoughts on what gives?
> I would even take pointers on where to start looking to find the
> problem.
> Meredith Ryan
>|||The logs had been applied. I guess I should have been a bit more
specific.
leaving our secondary in a Read-Only state to be used for reporting. I
have a need to get a new index on the secondary server (to decrease the
14 hour run time for a report). Our primary is in Full Recovery mode
as well.
I have created the index on my primary and expected it to be created on
the secondary when the logs were shipped this morning, only to find
that the Index was not created on the secondary.
I am not very familiar with Log Shipping and our in house expert is
unavailable.
Any thoughts on what gives?
I would even take pointers on where to start looking to find the
problem.
Meredith Ryan> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
>
You need the logs shipped AND applied for this to occur.
"mryan" <coffegrl@.gmail.com> wrote in message
news:1143761656.789619.3450@.v46g2000cwv.googlegroups.com...
> I am running SQL 2k on WinS2003 servers. We are using Log Shipping,
> leaving our secondary in a Read-Only state to be used for reporting. I
> have a need to get a new index on the secondary server (to decrease the
> 14 hour run time for a report). Our primary is in Full Recovery mode
> as well.
> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
> I am not very familiar with Log Shipping and our in house expert is
> unavailable.
> Any thoughts on what gives?
> I would even take pointers on where to start looking to find the
> problem.
> Meredith Ryan
>|||The logs had been applied. I guess I should have been a bit more
specific.
New indexes not shipped to secondary server
I am running SQL 2k on WinS2003 servers. We are using Log Shipping,
leaving our secondary in a Read-Only state to be used for reporting. I
have a need to get a new index on the secondary server (to decrease the
14 hour run time for a report). Our primary is in Full Recovery mode
as well.
I have created the index on my primary and expected it to be created on
the secondary when the logs were shipped this morning, only to find
that the Index was not created on the secondary.
I am not very familiar with Log Shipping and our in house expert is
unavailable.
Any thoughts on what gives?
I would even take pointers on where to start looking to find the
problem.
Meredith Ryan
> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
>
You need the logs shipped AND applied for this to occur.
"mryan" <coffegrl@.gmail.com> wrote in message
news:1143761656.789619.3450@.v46g2000cwv.googlegrou ps.com...
> I am running SQL 2k on WinS2003 servers. We are using Log Shipping,
> leaving our secondary in a Read-Only state to be used for reporting. I
> have a need to get a new index on the secondary server (to decrease the
> 14 hour run time for a report). Our primary is in Full Recovery mode
> as well.
> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
> I am not very familiar with Log Shipping and our in house expert is
> unavailable.
> Any thoughts on what gives?
> I would even take pointers on where to start looking to find the
> problem.
> Meredith Ryan
>
|||The logs had been applied. I guess I should have been a bit more
specific.
leaving our secondary in a Read-Only state to be used for reporting. I
have a need to get a new index on the secondary server (to decrease the
14 hour run time for a report). Our primary is in Full Recovery mode
as well.
I have created the index on my primary and expected it to be created on
the secondary when the logs were shipped this morning, only to find
that the Index was not created on the secondary.
I am not very familiar with Log Shipping and our in house expert is
unavailable.
Any thoughts on what gives?
I would even take pointers on where to start looking to find the
problem.
Meredith Ryan
> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
>
You need the logs shipped AND applied for this to occur.
"mryan" <coffegrl@.gmail.com> wrote in message
news:1143761656.789619.3450@.v46g2000cwv.googlegrou ps.com...
> I am running SQL 2k on WinS2003 servers. We are using Log Shipping,
> leaving our secondary in a Read-Only state to be used for reporting. I
> have a need to get a new index on the secondary server (to decrease the
> 14 hour run time for a report). Our primary is in Full Recovery mode
> as well.
> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
> I am not very familiar with Log Shipping and our in house expert is
> unavailable.
> Any thoughts on what gives?
> I would even take pointers on where to start looking to find the
> problem.
> Meredith Ryan
>
|||The logs had been applied. I guess I should have been a bit more
specific.
New indexes not shipped to secondary server
I am running SQL 2k on WinS2003 servers. We are using Log Shipping,
leaving our secondary in a Read-Only state to be used for reporting. I
have a need to get a new index on the secondary server (to decrease the
14 hour run time for a report). Our primary is in Full Recovery mode
as well.
I have created the index on my primary and expected it to be created on
the secondary when the logs were shipped this morning, only to find
that the Index was not created on the secondary.
I am not very familiar with Log Shipping and our in house expert is
unavailable.
Any thoughts on what gives?
I would even take pointers on where to start looking to find the
problem.
Meredith Ryan> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
>
You need the logs shipped AND applied for this to occur.
"mryan" <coffegrl@.gmail.com> wrote in message
news:1143761656.789619.3450@.v46g2000cwv.googlegroups.com...
> I am running SQL 2k on WinS2003 servers. We are using Log Shipping,
> leaving our secondary in a Read-Only state to be used for reporting. I
> have a need to get a new index on the secondary server (to decrease the
> 14 hour run time for a report). Our primary is in Full Recovery mode
> as well.
> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
> I am not very familiar with Log Shipping and our in house expert is
> unavailable.
> Any thoughts on what gives?
> I would even take pointers on where to start looking to find the
> problem.
> Meredith Ryan
>|||The logs had been applied. I guess I should have been a bit more
specific.
leaving our secondary in a Read-Only state to be used for reporting. I
have a need to get a new index on the secondary server (to decrease the
14 hour run time for a report). Our primary is in Full Recovery mode
as well.
I have created the index on my primary and expected it to be created on
the secondary when the logs were shipped this morning, only to find
that the Index was not created on the secondary.
I am not very familiar with Log Shipping and our in house expert is
unavailable.
Any thoughts on what gives?
I would even take pointers on where to start looking to find the
problem.
Meredith Ryan> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
>
You need the logs shipped AND applied for this to occur.
"mryan" <coffegrl@.gmail.com> wrote in message
news:1143761656.789619.3450@.v46g2000cwv.googlegroups.com...
> I am running SQL 2k on WinS2003 servers. We are using Log Shipping,
> leaving our secondary in a Read-Only state to be used for reporting. I
> have a need to get a new index on the secondary server (to decrease the
> 14 hour run time for a report). Our primary is in Full Recovery mode
> as well.
> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
> I am not very familiar with Log Shipping and our in house expert is
> unavailable.
> Any thoughts on what gives?
> I would even take pointers on where to start looking to find the
> problem.
> Meredith Ryan
>|||The logs had been applied. I guess I should have been a bit more
specific.
Subscribe to:
Posts (Atom)