interface supported: user

Showing posts with label user. Show all posts

Friday, March 30, 2012

Not A Trusted Connection

I set up my SQLExpress server using Windows Authentication only. Now when I
try to create a user account using Username and Password, the connection
returns the error: Not a trusted connection. Does this have something to do
with my previous server setup or is there a general setting somewhere I need
to change?
Regards,
Fred Chateau
http://hotelmotelnow.com
Never mind... I found the setting.
Regards,
Fred Chateau
http://hotelmotelnow.com
"Fred Chateau" <webmaster@.hotelmotelnow.com> wrote in message
news:u323BNenHHA.588@.TK2MSFTNGP06.phx.gbl...
>I set up my SQLExpress server using Windows Authentication only. Now when I
>try to create a user account using Username and Password, the connection
>returns the error: Not a trusted connection. Does this have something to do
>with my previous server setup or is there a general setting somewhere I
>need to change?
> --
> Regards,
> Fred Chateau
> http://hotelmotelnow.com
>

Not A Trusted Connection

I set up my SQLExpress server using Windows Authentication only. Now when I
try to create a user account using Username and Password, the connection
returns the error: Not a trusted connection. Does this have something to do
with my previous server setup or is there a general setting somewhere I need
to change?
Regards,
Fred Chateau
http://hotelmotelnow.comNever mind... I found the setting.
Regards,
Fred Chateau
http://hotelmotelnow.com
"Fred Chateau" <webmaster@.hotelmotelnow.com> wrote in message
news:u323BNenHHA.588@.TK2MSFTNGP06.phx.gbl...
>I set up my SQLExpress server using Windows Authentication only. Now when I
>try to create a user account using Username and Password, the connection
>returns the error: Not a trusted connection. Does this have something to do
>with my previous server setup or is there a general setting somewhere I
>need to change?
> --
> Regards,
> Fred Chateau
> http://hotelmotelnow.com
>

Wednesday, March 28, 2012

NoRows Property in Matrix does not work

I wanted to set the NoRows property for a matrix on a report to inform
the user when this condition occurs. I run the report by supplying
parameters that I am sure returns no data. Specifically, I am
determining the table to query based on user inputs. I provide inputs
that will look for a non existent table. I do an existence check on
the table to see if it is there to prevent a sql server error. If it
finds no table the query is not run. However, given that nothing is
returned the norows property is ignored and I get the error "Invalid
attempt to read when no data is present."
Could it be because the matrix requires an empty dataset back?That is what it was. I now ensure I return an empty dataset if the
table does not exist.

Friday, March 23, 2012

non-updatable views

can i create a non-updatable view?
i cannot use user level restrictions.Check out the "CREATE VIEW" page in SQL Server 2000 Books Online, which
outlines some rules to make views updatable, and see if you can use one of
those rules to make your views non-updatable. For example, if the view
definition contains a derived column, that view cannot be updated. Here's a
quick example:
CREATE VIEW MyView AS SELECT Col1, Col2, 'X' AS NotUpdatable FROM MyTable
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
<mcourter@.mindspring.com> wrote in message
news:1122910718.612379.166500@.g44g2000cwa.googlegroups.com...
can i create a non-updatable view?
i cannot use user level restrictions.

Non-SysAdmins have been denied permission to run CmdExec job steps

Is there a certain role or permission that a user must be given to run jobs?
Thanks.
Ron
Per BOL, under "jobs, running/ Transact SQL".
Permissions
Execute permissions default to the public role in the msdb database. A user
who can execute this procedure and is a member of the sysadmin fixed role can
start any job. A user who is not a member of the sysadmin role can use
sp_start_job to start only the jobs he/she owns.
ChrisR
"Ron" wrote:

> Is there a certain role or permission that a user must be given to run jobs?
> Thanks.
> Ron
|||Under properties of SQL Server Agent there's a setting under the job system
tab:
"Non-sysadmin job step proxy account" - I checked this off and users were OK.
Ron
"Ron" wrote:

> Is there a certain role or permission that a user must be given to run jobs?
> Thanks.
> Ron

Non-SysAdmins have been denied permission to run CmdExec job steps

Is there a certain role or permission that a user must be given to run jobs?
Thanks.
RonPer BOL, under "jobs, running/ Transact SQL".
Permissions
Execute permissions default to the public role in the msdb database. A user
who can execute this procedure and is a member of the sysadmin fixed role can
start any job. A user who is not a member of the sysadmin role can use
sp_start_job to start only the jobs he/she owns.
--
ChrisR
"Ron" wrote:
> Is there a certain role or permission that a user must be given to run jobs?
> Thanks.
> Ron|||Under properties of SQL Server Agent there's a setting under the job system
tab:
"Non-sysadmin job step proxy account" - I checked this off and users were OK.
Ron
"Ron" wrote:
> Is there a certain role or permission that a user must be given to run jobs?
> Thanks.
> Ron

Non-SysAdmins have been denied permission to run CmdExec job steps

Is there a certain role or permission that a user must be given to run jobs?
Thanks.
RonPer BOL, under "jobs, running/ Transact SQL".
Permissions
Execute permissions default to the public role in the msdb database. A user
who can execute this procedure and is a member of the sysadmin fixed role ca
n
start any job. A user who is not a member of the sysadmin role can use
sp_start_job to start only the jobs he/she owns.
ChrisR
"Ron" wrote:

> Is there a certain role or permission that a user must be given to run job
s?
> Thanks.
> Ron|||Under properties of SQL Server Agent there's a setting under the job system
tab:
"Non-sysadmin job step proxy account" - I checked this off and users were OK
.
Ron
"Ron" wrote:

> Is there a certain role or permission that a user must be given to run job
s?
> Thanks.
> Ronsql

Non-SysAdmins ... proxy account

Error:
Non-SysAdmins have been denied permission to run
replication jobsteps without a proxy account. The step
failed.
&&
Executed as user: Jobz. Replication-agentclassname: agent
cb-desktop\cbx-NEWBIE-NEWBIE_pub-CB-DESKTOP\CBX-9 failed.
Non-SysAdmins have been denied permission to run
replication jobsteps without a proxy account. The step
failed. [SQLSTATE 42000] (Error 14151). The step failed.
What I have:
Calling a Job with user 'Jobz', 'Jobz' owns this job so it
IS getting called.
2 of the 3 steps are failing because 'Non-SysAdmins have
been denied permission to run replication jobsteps without
a proxy account'
How do I configure this proxy account so that running
replication jobsteps will succeed with a user other then
sa ?
Thanks,
John C.See the following kb for more info.
818552 BUG: Replication Agent Might Run Continuously Even When the
Replication
http://support.microsoft.com/?id=818552
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Running the stored proc worked for a bit, but then when
back to: "Non-SysAdmins have been denied permission to run
replication jobsteps without a proxy account. The step
failed."
I don't think http://support.microsoft.com/?id=818552 is
the solution to this problem.
How do you make it so that Non-SysAdmins are allowed
permission to call replication jobsteps ?
(sql server 2000 sp3)
is this the best way for a client to invoke a merge agent ?

Monday, March 12, 2012

Non-Admin user can't create a linked report in My Reports...

A Non-Admin user can't create a linked report in his My Reports folder.
Reporting Services is set up with My Reports enabled with the default tasks
assigned to the My Reports role (this includes Create linked reports). This
same user can create sub-folders but not linked reports.
----
aspnet_wp!library!164!10/07/2004-17:42:44:: i INFO: Call to
CreateLinkedReport( '20041007 1742 SimpleReport', '/My
Reports/Submitted/Test', '/Standard Reports/Test/SimpleReport',
'Microsoft.ReportingServices.Library.Soap.Property[]' )
aspnet_wp!library!164!10/07/2004-17:42:44:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The
permissions granted to user 'LABTM\RSFinancialAnalyst' are insufficient for
performing this operation., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The
permissions granted to user 'LABTM\RSFinancialAnalyst' are insufficient for
performing this operation.Does the user have Read Properties permission to the report /Standard
Reports/Test/SimpleReport?
-Lukasz|||I discovered the problem... The Browser Role is not associated with the
"Create linked reports" task by default. Once I assigned the Create linked
reports task to the Browser Role the non-admin user could create linked
reports.
Thanks for the hint Lukasz.
Garry Lenz
"Garry Lenz" <glenz@.thoughtmill.com> wrote in message
news:%231hAadLrEHA.2136@.TK2MSFTNGP14.phx.gbl...
> A Non-Admin user can't create a linked report in his My Reports folder.
> Reporting Services is set up with My Reports enabled with the default
tasks
> assigned to the My Reports role (this includes Create linked reports).
This
> same user can create sub-folders but not linked reports.
> ----
> aspnet_wp!library!164!10/07/2004-17:42:44:: i INFO: Call to
> CreateLinkedReport( '20041007 1742 SimpleReport', '/My
> Reports/Submitted/Test', '/Standard Reports/Test/SimpleReport',
> 'Microsoft.ReportingServices.Library.Soap.Property[]' )
> aspnet_wp!library!164!10/07/2004-17:42:44:: e ERROR: Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException:
The
> permissions granted to user 'LABTM\RSFinancialAnalyst' are insufficient
for
> performing this operation., ;
> Info:
> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException:
The
> permissions granted to user 'LABTM\RSFinancialAnalyst' are insufficient
for
> performing this operation.
>

non-admin user and SSIS (integration services)

I wish to grant access to SSIS (e.g., register server in mssms) for a
user _without_ making that user an administrator of the host.
How can this be done--if at all?
horseradish,
A login that can use SSIS needs no special server rights. In terms of
server roles, my developers are in 'public'. There are decisions that you
need to make, of course, and these are outlined here:
http://technet.microsoft.com/en-us/library/ms137833.aspx
FWIW, I (despite the pitch for how good it is to store packages in msdb)
keep my stored on the file system. For one thing, on the file system more
than one team member can edit the package.
RLF
"horseradish" <dontcallme@.illcallu.net> wrote in message
news:OgC5bzRMIHA.5240@.TK2MSFTNGP04.phx.gbl...
>I wish to grant access to SSIS (e.g., register server in mssms) for a user
>_without_ making that user an administrator of the host.
> How can this be done--if at all?
|||You can follow this procedure to give access to SSIS to users who are not
local Administrators (look for the 'Access is Denied' section').
http://technet.microsoft.com/en-us/library/aa337083.aspx
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"horseradish" wrote:

> I wish to grant access to SSIS (e.g., register server in mssms) for a
> user _without_ making that user an administrator of the host.
> How can this be done--if at all?
>
|||Ben,

> You can follow this procedure to give access to SSIS to users who are not
> local Administrators (look for the 'Access is Denied' section').
> http://technet.microsoft.com/en-us/library/aa337083.aspx
BINGO. This solved the issue. Thanks for the assist!

non-admin user and SSIS (integration services)

I wish to grant access to SSIS (e.g., register server in mssms) for a
user _without_ making that user an administrator of the host.
How can this be done--if at all?horseradish,
A login that can use SSIS needs no special server rights. In terms of
server roles, my developers are in 'public'. There are decisions that you
need to make, of course, and these are outlined here:
http://technet.microsoft.com/en-us/library/ms137833.aspx
FWIW, I (despite the pitch for how good it is to store packages in msdb)
keep my stored on the file system. For one thing, on the file system more
than one team member can edit the package.
RLF
"horseradish" <dontcallme@.illcallu.net> wrote in message
news:OgC5bzRMIHA.5240@.TK2MSFTNGP04.phx.gbl...
>I wish to grant access to SSIS (e.g., register server in mssms) for a user
>_without_ making that user an administrator of the host.
> How can this be done--if at all?|||You can follow this procedure to give access to SSIS to users who are not
local Administrators (look for the 'Access is Denied' section').
http://technet.microsoft.com/en-us/library/aa337083.aspx
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"horseradish" wrote:
> I wish to grant access to SSIS (e.g., register server in mssms) for a
> user _without_ making that user an administrator of the host.
> How can this be done--if at all?
>|||Ben,
> You can follow this procedure to give access to SSIS to users who are not
> local Administrators (look for the 'Access is Denied' section').
> http://technet.microsoft.com/en-us/library/aa337083.aspx
BINGO. This solved the issue. Thanks for the assist!

non-admin user and SSIS (integration services)

I wish to grant access to SSIS (e.g., register server in mssms) for a
user _without_ making that user an administrator of the host.
How can this be done--if at all?horseradish,
A login that can use SSIS needs no special server rights. In terms of
server roles, my developers are in 'public'. There are decisions that you
need to make, of course, and these are outlined here:
http://technet.microsoft.com/en-us/...y/ms137833.aspx
FWIW, I (despite the pitch for how good it is to store packages in msdb)
keep my stored on the file system. For one thing, on the file system more
than one team member can edit the package.
RLF
"horseradish" <dontcallme@.illcallu.net> wrote in message
news:OgC5bzRMIHA.5240@.TK2MSFTNGP04.phx.gbl...
>I wish to grant access to SSIS (e.g., register server in mssms) for a user
>_without_ making that user an administrator of the host.
> How can this be done--if at all?|||You can follow this procedure to give access to SSIS to users who are not
local Administrators (look for the 'Access is Denied' section').
http://technet.microsoft.com/en-us/...y/aa337083.aspx
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"horseradish" wrote:

> I wish to grant access to SSIS (e.g., register server in mssms) for a
> user _without_ making that user an administrator of the host.
> How can this be done--if at all?
>|||Ben,

> You can follow this procedure to give access to SSIS to users who are not
> local Administrators (look for the 'Access is Denied' section').
> http://technet.microsoft.com/en-us/...y/aa337083.aspx
BINGO. This solved the issue. Thanks for the assist!

Non sa running jobs?

Is there a way for a user to manage ( run, delete, add ) a job if he has not
got sa permission?
Thanks
AlexAlex,
Yes if the user is a member of the SYSADMIN fixed server role. Note however
that membership of this role should be limited as the role enables a user to
do pretty much anything in SQL Server.
HTH
Jerry
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> Is there a way for a user to manage ( run, delete, add ) a job if he has
> not
> got sa permission?
> Thanks
> Alex|||Thanks for this. But the problem we have is SOX compliance !. Us dba's have
been stripped off sa/SYSADMIN fixed role permission so we can't modify data.
The side effect of this is that there are loads of admin tasks we cannot now
do.
Alex
"Jerry Spivey" wrote:
> Alex,
> Yes if the user is a member of the SYSADMIN fixed server role. Note however
> that membership of this role should be limited as the role enables a user to
> do pretty much anything in SQL Server.
> HTH
> Jerry
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> > Is there a way for a user to manage ( run, delete, add ) a job if he has
> > not
> > got sa permission?
> >
> > Thanks
> >
> > Alex
>
>|||Hmmm...that doesn't sound right. You're a DBA but you're not a member of
the SYSADMIN fixed server role? How can you do your job?
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
> Thanks for this. But the problem we have is SOX compliance !. Us dba's
> have
> been stripped off sa/SYSADMIN fixed role permission so we can't modify
> data.
> The side effect of this is that there are loads of admin tasks we cannot
> now
> do.
> Alex
>
> "Jerry Spivey" wrote:
>> Alex,
>> Yes if the user is a member of the SYSADMIN fixed server role. Note
>> however
>> that membership of this role should be limited as the role enables a user
>> to
>> do pretty much anything in SQL Server.
>> HTH
>> Jerry
>> "Alex" <Alex@.discussions.microsoft.com> wrote in message
>> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
>> > Is there a way for a user to manage ( run, delete, add ) a job if he
>> > has
>> > not
>> > got sa permission?
>> >
>> > Thanks
>> >
>> > Alex
>>|||Since we don't want SA running jobs (or being in the Sysadmin group), I set
up a login with win authent, sysadmin to run jobs. No one needs the password
to use; just set this user up as the proxy account (under agent properties,
job system), and if any job owner is not a sysadmin, it defaults to this guy.
HTH, mary
"Alex" wrote:
> Thanks for this. But the problem we have is SOX compliance !. Us dba's have
> been stripped off sa/SYSADMIN fixed role permission so we can't modify data.
> The side effect of this is that there are loads of admin tasks we cannot now
> do.
> Alex
>
> "Jerry Spivey" wrote:
> > Alex,
> >
> > Yes if the user is a member of the SYSADMIN fixed server role. Note however
> > that membership of this role should be limited as the role enables a user to
> > do pretty much anything in SQL Server.
> >
> > HTH
> >
> > Jerry
> > "Alex" <Alex@.discussions.microsoft.com> wrote in message
> > news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> > > Is there a way for a user to manage ( run, delete, add ) a job if he has
> > > not
> > > got sa permission?
> > >
> > > Thanks
> > >
> > > Alex
> >
> >
> >|||Yes, try telling this to the auditors!
We are very frustrated. If we need to add a job we will need to apply for
permission to log in as sa, after going through multilevel of sign off from
the senior management - all for running a SQL Profile, or creating
maintenance plan !!
and then all actions will be be logged as well.
Alex
"Jerry Spivey" wrote:
> Hmmm...that doesn't sound right. You're a DBA but you're not a member of
> the SYSADMIN fixed server role? How can you do your job?
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
> > Thanks for this. But the problem we have is SOX compliance !. Us dba's
> > have
> > been stripped off sa/SYSADMIN fixed role permission so we can't modify
> > data.
> > The side effect of this is that there are loads of admin tasks we cannot
> > now
> > do.
> >
> > Alex
> >
> >
> > "Jerry Spivey" wrote:
> >
> >> Alex,
> >>
> >> Yes if the user is a member of the SYSADMIN fixed server role. Note
> >> however
> >> that membership of this role should be limited as the role enables a user
> >> to
> >> do pretty much anything in SQL Server.
> >>
> >> HTH
> >>
> >> Jerry
> >> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> >> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> >> > Is there a way for a user to manage ( run, delete, add ) a job if he
> >> > has
> >> > not
> >> > got sa permission?
> >> >
> >> > Thanks
> >> >
> >> > Alex
> >>
> >>
> >>
>
>|||Curious, if the is a reason to suddenly restore a db in the middle of the day
so production activities can resume, is the same process to log in as SA
required?
--
ChrisR
"Alex" wrote:
> Yes, try telling this to the auditors!
> We are very frustrated. If we need to add a job we will need to apply for
> permission to log in as sa, after going through multilevel of sign off from
> the senior management - all for running a SQL Profile, or creating
> maintenance plan !!
> and then all actions will be be logged as well.
> Alex
> "Jerry Spivey" wrote:
> > Hmmm...that doesn't sound right. You're a DBA but you're not a member of
> > the SYSADMIN fixed server role? How can you do your job?
> > "Alex" <Alex@.discussions.microsoft.com> wrote in message
> > news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
> > > Thanks for this. But the problem we have is SOX compliance !. Us dba's
> > > have
> > > been stripped off sa/SYSADMIN fixed role permission so we can't modify
> > > data.
> > > The side effect of this is that there are loads of admin tasks we cannot
> > > now
> > > do.
> > >
> > > Alex
> > >
> > >
> > > "Jerry Spivey" wrote:
> > >
> > >> Alex,
> > >>
> > >> Yes if the user is a member of the SYSADMIN fixed server role. Note
> > >> however
> > >> that membership of this role should be limited as the role enables a user
> > >> to
> > >> do pretty much anything in SQL Server.
> > >>
> > >> HTH
> > >>
> > >> Jerry
> > >> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> > >> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> > >> > Is there a way for a user to manage ( run, delete, add ) a job if he
> > >> > has
> > >> > not
> > >> > got sa permission?
> > >> >
> > >> > Thanks
> > >> >
> > >> > Alex
> > >>
> > >>
> > >>
> >
> >
> >|||I don't recall anything in SOX that states that a DBA can not have sa
rights. Someone is taking the wording way beyond it's intent. SQL2005 will
have roles specifically for this but in 2000 it is not that easy.
--
Andrew J. Kelly SQL MVP
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
> Thanks for this. But the problem we have is SOX compliance !. Us dba's
> have
> been stripped off sa/SYSADMIN fixed role permission so we can't modify
> data.
> The side effect of this is that there are loads of admin tasks we cannot
> now
> do.
> Alex
>
> "Jerry Spivey" wrote:
>> Alex,
>> Yes if the user is a member of the SYSADMIN fixed server role. Note
>> however
>> that membership of this role should be limited as the role enables a user
>> to
>> do pretty much anything in SQL Server.
>> HTH
>> Jerry
>> "Alex" <Alex@.discussions.microsoft.com> wrote in message
>> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
>> > Is there a way for a user to manage ( run, delete, add ) a job if he
>> > has
>> > not
>> > got sa permission?
>> >
>> > Thanks
>> >
>> > Alex
>>|||Thanks Mary. This could be the escape route we have been looking for!
Alex
"Mary" wrote:
> Since we don't want SA running jobs (or being in the Sysadmin group), I set
> up a login with win authent, sysadmin to run jobs. No one needs the password
> to use; just set this user up as the proxy account (under agent properties,
> job system), and if any job owner is not a sysadmin, it defaults to this guy.
> HTH, mary
> "Alex" wrote:
> > Thanks for this. But the problem we have is SOX compliance !. Us dba's have
> > been stripped off sa/SYSADMIN fixed role permission so we can't modify data.
> > The side effect of this is that there are loads of admin tasks we cannot now
> > do.
> >
> > Alex
> >
> >
> > "Jerry Spivey" wrote:
> >
> > > Alex,
> > >
> > > Yes if the user is a member of the SYSADMIN fixed server role. Note however
> > > that membership of this role should be limited as the role enables a user to
> > > do pretty much anything in SQL Server.
> > >
> > > HTH
> > >
> > > Jerry
> > > "Alex" <Alex@.discussions.microsoft.com> wrote in message
> > > news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> > > > Is there a way for a user to manage ( run, delete, add ) a job if he has
> > > > not
> > > > got sa permission?
> > > >
> > > > Thanks
> > > >
> > > > Alex
> > >
> > >
> > >|||Andrew
We can run sa tasks, but we need authorisation every time we need to. its
like working with one of your hands tied.
Alex
"Andrew J. Kelly" wrote:
> I don't recall anything in SOX that states that a DBA can not have sa
> rights. Someone is taking the wording way beyond it's intent. SQL2005 will
> have roles specifically for this but in 2000 it is not that easy.
> --
> Andrew J. Kelly SQL MVP
>
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
> > Thanks for this. But the problem we have is SOX compliance !. Us dba's
> > have
> > been stripped off sa/SYSADMIN fixed role permission so we can't modify
> > data.
> > The side effect of this is that there are loads of admin tasks we cannot
> > now
> > do.
> >
> > Alex
> >
> >
> > "Jerry Spivey" wrote:
> >
> >> Alex,
> >>
> >> Yes if the user is a member of the SYSADMIN fixed server role. Note
> >> however
> >> that membership of this role should be limited as the role enables a user
> >> to
> >> do pretty much anything in SQL Server.
> >>
> >> HTH
> >>
> >> Jerry
> >> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> >> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> >> > Is there a way for a user to manage ( run, delete, add ) a job if he
> >> > has
> >> > not
> >> > got sa permission?
> >> >
> >> > Thanks
> >> >
> >> > Alex
> >>
> >>
> >>
>
>

Non sa running jobs?

Friday, March 9, 2012

Non domain user receive access denied error

I am trying to run a VBScript that uses a SQL user to access a 2000 SQL SP4
clustered instance.
The script runs successfully only when I am logged on with a domain account.
What can the reason for this be?
Thanks in advance,
Ido Friedman
My first thought is that the VBScript is using NT authentication instead of
SQL Authentication.
Can you post the script?
Keith Kratochvil
"Ido friedman" <Idofriedman@.discussions.microsoft.com> wrote in message
news:A1B97509-42C7-4EBB-9BA3-786FA81E682F@.microsoft.com...
>I am trying to run a VBScript that uses a SQL user to access a 2000 SQL SP4
> clustered instance.
> The script runs successfully only when I am logged on with a domain
> account.
> What can the reason for this be?
>
> Thanks in advance,
> Ido Friedman

Non Admin user error on Reporting Services

I am very new to reporting services. I have completed the SQL Tutorials that come with however I am stuck on something.

My network here consists of a 2003 AD Controlled Domain, various servers yadda yadda. I obviously am a Domain admin as well as a Normal Administrator. I have deployed my report and when I, or any other member on the domain who is in the same groups as me tries to access the report it works perfectly however, when a normal Domain User tries to access the report from http://servername/reports they get the following message :-

An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DashboardSQL-2K5'. (rsErrorOpeningConnection)
For more information about this error navigate to the report server on the local server machine, or enable remote errors

What on earth does this mean. Once I have deployed the report I am going into Reporting Services manager and reapplying the security permissions for the Data Source but it appears to make no difference.

Anybody able to shed some light on this?

Regards

It sounds like you have configured the data source 'DashboardSQL-2K5' to use Windows credentials. In this case RS will use the credentials of the user who is running the report to connect to the data source. Do your non-admin users have permission to login to your SQL Server?

-Albert

Saturday, February 25, 2012

No. of User Accounts in SQL SERVER 2000 and SQL SERVER 2005 ..plz

I want to know the maximum number of users that can be created in SQL SERVER 2005 and the previous version...?

Yorker:

I am going to assume that you will hit the limitations of the "uid" field. This field is a SMALLINT datatype; however, it appears that groups begin @. 16384 and that this field must be non-negative. Therefore, it appears that a user database MIGHT be limited to 16384 distinct users. However, on a serverwide database you can have many databases therefore leading to at least N x 16384 distinct users. There does not look to be any "variable size" limitation on the LOGIN side because this is based now on SIDs whereas in much older versions of sql server it was formerly based on "SUID"s -- The cardinality of the number of SIDs appears to be enormous.

Would someone please check me on this?

Dave

|||The maximum number of logins in 2000 was 35,365, in 2005 it was increased to 65,000 (I think).

However, I would HIGHLY recommend using windows authentication and group membership for rights, instead of 35,000+ SQL logins.|||any evidence to prove your numbers... ? Gentleman ?|||See this: http://msdn2.microsoft.com/en-us/library/ms187376.aspx

This says in 2005 "you can create more than 32,767 users". I was slightly off with my number in 2000. I thought I read somewhere else about the 64k limit in 2005, but I might be mistaken.

I still it is a nighmare to manage 32k logins.|||From http://msdn2.microsoft.com/en-us/library/ms187376.aspx, it infers that SQL2K can only have 32767 SQL users, but SQL2K5 can have more. How much more, I don't know off-hand.

But this doesn't say how many logins there could be (although I would guess it would be the same). http://msdn2.microsoft.com/en-us/library/ms174355.aspx doesn't give many clues.

I would strongly recommend using Active Directory, where the limit doesn't actually apply in the same way. Plus, do you really want to have your DBAs managing this type of thing?

Rob|||But... it turns out that http://support.microsoft.com/default.aspx/kb/303879 quite clearly states that SQL2000 can only have 16K users.

But I guess the types used in sys.sysusers will cater for more.|||

I think that is refering to "database logins" and not "server logins".

The other one does say "This is because, in SQL Server 2005, you can create more than 32,767 users, groups, and roles, and 32,767 data types." This kind of implies, users/groups/roles use the same id counter, so combined you can't have more than 32,767.

MS added more than 16k of users for a reason, although I find it hard to believe someone requested that to be added because they ran out of logins. I have a hard enough time managing 100 SQL logins (excluding AD Groups), I can't imagine the headache I would have with more than that. :)

No User Folders

The RS Administrators are able to see all folders except the users.
Why is it that users are unable to see their folders?
Please help!Does this happen in the report manager?
Perhaps the users don't have the permission to see those folders. Take a
look to the security tab on the problematic folders.|||Thanks!
However, the user did not have the proper permission to access the folder.
Again, thanks!
"F. Dwarf" wrote:
> Does this happen in the report manager?
> Perhaps the users don't have the permission to see those folders. Take a
> look to the security tab on the problematic folders.

Friday, March 30, 2012

Not A Trusted Connection

Not A Trusted Connection

Wednesday, March 28, 2012

NoRows Property in Matrix does not work

Friday, March 23, 2012

non-updatable views

Non-SysAdmins have been denied permission to run CmdExec job steps

Non-SysAdmins have been denied permission to run CmdExec job steps

Non-SysAdmins have been denied permission to run CmdExec job steps

Non-SysAdmins ... proxy account

Monday, March 12, 2012

Non-Admin user can't create a linked report in My Reports...

non-admin user and SSIS (integration services)

non-admin user and SSIS (integration services)

non-admin user and SSIS (integration services)

Non sa running jobs?

Non sa running jobs?

Non sa running jobs?

Friday, March 9, 2012

Non domain user receive access denied error

Non Admin user error on Reporting Services

Saturday, February 25, 2012

No. of User Accounts in SQL SERVER 2000 and SQL SERVER 2005 ..plz

No User Folders

interface supported

Blog Archive

About Me