Accessing jobs in EM

Hello!
I would like to allow non-admin users seeing all jobs (including ones
they do now own) in Enterpise Manager.SQL Profiler displays execution of
exec msdb..sp_help_job when querying job list. According to BOL: ' A user
who is not a member of the sysadmin fixed role can use sp_help_job to view
only the jobs he/she owns.'. I suppose xp_sqlagent_proxy_account wouldn't be
of any help in this case. Is this possible for non-admin users to see all
jobs?
Thanks,
IgorThere is no supported way to do this with Enterprise
Manager. The proxy account doesn't really come in to play
here. The system stored procedures involved in displaying
the job info in Enterprise Manager have checks for job owner
or sysadmin server role membership.
-Sue
On Fri, 21 Jan 2005 14:46:12 -0800, "Igor Marchenko"
<igormarchenko@.hotmail.com> wrote:

>Hello!
>
> I would like to allow non-admin users seeing all jobs (including ones
>they do now own) in Enterpise Manager.SQL Profiler displays execution of
>exec msdb..sp_help_job when querying job list. According to BOL: ' A user
>who is not a member of the sysadmin fixed role can use sp_help_job to view
>only the jobs he/she owns.'. I suppose xp_sqlagent_proxy_account wouldn't b
e
>of any help in this case. Is this possible for non-admin users to see all
>jobs?
>
>Thanks,
>Igor
>|||Thanks,Sue. I have found another way:
1.. Grant access to MSDB
2.. Add users to the member of TargetServerRole.
Regards,
Igor
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:lvnav0d2r3c3n64s620e9me5o0o7t1pdl6@.
4ax.com...
> There is no supported way to do this with Enterprise
> Manager. The proxy account doesn't really come in to play
> here. The system stored procedures involved in displaying
> the job info in Enterprise Manager have checks for job owner
> or sysadmin server role membership.
> -Sue
> On Fri, 21 Jan 2005 14:46:12 -0800, "Igor Marchenko"
> <igormarchenko@.hotmail.com> wrote:
>
>|||Okay but just remember it's not supported though and how
this works with this role depends on what service pack you
are on.
-Sue
On Tue, 25 Jan 2005 10:39:09 -0800, "Igor Marchenko"
<igormarchenko@.hotmail.com> wrote:

>Thanks,Sue. I have found another way:
> 1.. Grant access to MSDB
> 2.. Add users to the member of TargetServerRole.
>Regards,
>Igor
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:lvnav0d2r3c3n64s620e9me5o0o7t1pdl6@.
4ax.com...
>|||Thanks a lot,Sue.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:5f5dv0d14fq7ajas3r6qq577is20d0gn57@.
4ax.com...
> Okay but just remember it's not supported though and how
> this works with this role depends on what service pack you
> are on.
> -Sue
> On Tue, 25 Jan 2005 10:39:09 -0800, "Igor Marchenko"
> <igormarchenko@.hotmail.com> wrote:
>
>

Accessing config file from delivery extension

I'm running into a problem with reading a config file with my own custom
entries in it from within a delivery extension. I've tried putting it in the
ReportServer web.config and RSReportServer.config, and my code doesn't seem
to be able to find it.
When I use the configuration file .Net framework classes from within a
delivery extension, which config file is it looking at?
Thanks,
Mike SandwickMike,
Subscriptions are run in an unattended mode by the Report Server Windows
service (ReportingServicesService.exe) not the Report Server. So, try
putting your config settings in ReportingServicesService.exe.config.
--
Hope this helps.
----
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
----
"Mike Sandwick" <MikeSandwick@.discussions.microsoft.com> wrote in message
news:8BF4DD62-2EBE-491E-AB21-12BCFF53AA8E@.microsoft.com...
> I'm running into a problem with reading a config file with my own custom
> entries in it from within a delivery extension. I've tried putting it in
the
> ReportServer web.config and RSReportServer.config, and my code doesn't
seem
> to be able to find it.
> When I use the configuration file .Net framework classes from within a
> delivery extension, which config file is it looking at?
> Thanks,
> Mike Sandwick|||Hi Teo:
The delivery extension also has to provide GUI functionality in the
Report Server process, which will pull settings from
RSWebApplication.config. Depending on when the settings are used -
they might have to appear in both.
--
Scott
http://www.OdeToCode.com/
On Tue, 5 Oct 2004 21:57:50 -0400, "Teo Lachev [MVP]"
<teo.lachev@.nospam.prologika.com> wrote:
>Mike,
>Subscriptions are run in an unattended mode by the Report Server Windows
>service (ReportingServicesService.exe) not the Report Server. So, try
>putting your config settings in ReportingServicesService.exe.config.|||That was it, I put my configuration file entry in the
ReportingServicesService.exe.config, and it now works.
Thanks!
Mike
"Teo Lachev [MVP]" wrote:
> Mike,
> Subscriptions are run in an unattended mode by the Report Server Windows
> service (ReportingServicesService.exe) not the Report Server. So, try
> putting your config settings in ReportingServicesService.exe.config.
> --
> Hope this helps.
> ----
> Teo Lachev, MVP [SQL Server], MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com: http://shrinkster.com/eq
> Home page and blog: http://www.prologika.com/
> ----
> "Mike Sandwick" <MikeSandwick@.discussions.microsoft.com> wrote in message
> news:8BF4DD62-2EBE-491E-AB21-12BCFF53AA8E@.microsoft.com...
> > I'm running into a problem with reading a config file with my own custom
> > entries in it from within a delivery extension. I've tried putting it in
> the
> > ReportServer web.config and RSReportServer.config, and my code doesn't
> seem
> > to be able to find it.
> >
> > When I use the configuration file .Net framework classes from within a
> > delivery extension, which config file is it looking at?
> >
> > Thanks,
> > Mike Sandwick
>
>|||Scott,
You are right. In general, a custom extension should store its config
settings in the Configuration element in the RSWebApplication.config. This
will allow the Report Server (or Report Manager) to push these settings to
the extension.
Perhaps, I should have started my reply with this side note. I assumed that
in Mike's case this wasn't acceptable. Thanks for pointing this out.
--
Hope this helps.
----
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
----
"Scott Allen" <bitmask@.[nospam].fred.net> wrote in message
news:6g07m0ttch61feklpro0dueks5a301o6d7@.4ax.com...
> Hi Teo:
> The delivery extension also has to provide GUI functionality in the
> Report Server process, which will pull settings from
> RSWebApplication.config. Depending on when the settings are used -
> they might have to appear in both.
> --
> Scott
> http://www.OdeToCode.com/
> On Tue, 5 Oct 2004 21:57:50 -0400, "Teo Lachev [MVP]"
> <teo.lachev@.nospam.prologika.com> wrote:
> >Mike,
> >
> >Subscriptions are run in an unattended mode by the Report Server Windows
> >service (ReportingServicesService.exe) not the Report Server. So, try
> >putting your config settings in ReportingServicesService.exe.config.
>

Access to SQL guidance?

OK I have been trying on my own to move from Access to SQL express/Developer. I have not found much in the way of guidence. Any suggestions? I would rank myself as fairly advanced with Access but just a newby to the SQL products... I keep blasting into walls and issues in the SQL world and would rather learn from someone elses' hardship rather than re-invent what has been undoubtably been already discovered.

I do fairly advanced reports and Large imports, Hence the need for developer rather than express, since the express import facility is hopelessly crippled. Even the developer SSIS is not well doccumented and seems pretty buggy and hard to use, even with the wizzards, As for reports.... well I'm expecting that to be a fairly had road to climb also...

Your are in a common position so rest assured many of us have been there. One of the easiest things I tend to do in this situation is learn as the need arises.

For example, creating relationships in access is very easy. You will find no such "GUI" way in sql server to create relationships. You can instead use management studio to do the same thing, but you just won't have the pretty layout that access has.

Also, if you are familiar with access you probably are aware of using an access project (intended I think for an SQL server type database situation).

So I would jump around this forum and other forums and find out the answers to the questions you need as these issues arise. You may want to pickup and intro to sql server book just to get an overview of the tools in sql server, but if you are the hands on type you may just want to jump right in. When you do install the dev edition you will (or may be -- I was) overwhelemd by the number of features installed. Keep it simple and focus on one task at a time.

E.g. create a simple db and run some queries and forget about configuring remote access and things like that at first.

I hope some of this was helpful. Do you have any specific questions about the change?

Ranginald|||

Thanks for the reply. Indeed that is exactly what I'm doing, jumping in that is. Its the way I've always learned the next new thing, in fact I've been involved with computers for more than 20 years now...Generally books are for sissies!

But on the other hand do you have any you would particularly single out as being good?

Here is some of my experience which may help the next person on this trail....I still don't get why someone has not addressed the topic more comprehensively since it seems that this is a path that many will be embarking on....

Actually I find the GUI table relationship thing to be fairly transferable to SQL management studio, so far. I miss being able to use vb in queries though...

so far I have a basic import going using ssis, (boy that wasn't easy) The SSIS tool seems very poorly supported, for instance I created an import job (via wizard), and just opened it and closed it with no modifications and it generated errors that it did not generate when first created by the wizard! Not to mention the terminations for truncated fields that there is no ready documentation how to accept rather than terminate.. So an import that took 5 minutes to do in Access took Hours to do in SSIS from a basic Flat text file.

I have imported a bunch of tables from access (easier)

I have done some derived tables and views, (not too hard) but I'm not to the advanced stuff yet.

Written one report, pretty basic and I'm thinking the SQL tool looks pretty hard relative to advanced reports in Access.

|||Glad I could help. I've always liked Wrox books. They are well written and to the point. I'm sure you know this already but whenever I want to buy a book I look on amazon for the user rating first to see if it's worth it.

Good luck.
Ranginald