Hi,

I'm using Analysis Services on a SQL Server 2000 system.

I'm using a DTS package to update the dimensions to process the cubes. This
works fine as long as I start the package myself (as an admin user). But the
package seems to require some DLLs or other environmental files which are not
available on the "usual" co-workers' computers: If some non-admin with no
AS-Services installed starts the package via the .NET-user-interface, the
method "DTS.Package2Class.LoadFromSQLServer" fails by stating "unknown class
identifier" (or likewise; the message is in German as I use the German
version).

This means, either I have to start the package myself as soon as anybody in
the company yells for an update, or many "datareaders" would have to get all
the AS developing software they're not supposed to fool around with :-)

I need a "central" trigger which can and will update all the dimensions and
cubes in his own name as soon as triggered by a valid "datareader". But how?

Thx for your hints
Martin

The Analysis Services tasks in DTS (SQL 2000) - require 2 things.

1) The DSO library needs to be installed on the computer(s) executing
the package. (I thought that the DSO files were re-distributable, but I
could not locate a download apart from the Microsoft SQL Server 2005
Backward Compatibility Components which are part of the SQL 2005 feature
pack http://www.microsoft.com/downloads/d...lyid=d09c1d60-
a13c-4479-9b91-9e8b9d835cdc&displaylang=en )

2) The user executing the package needs to be a member of the OLAP
Administrators role.

Another approach, is to setup a scheduled job on the server to execute
the package. This means that the SQL Agent process needs to be running
under a domain account which is a member of the OLAP Administrators
group and the DSO library only needs to be install on the server.

There is an article here on running DTS packages as a scheduled job:
http://support.microsoft.com/default...269074&sd=tech

The drawback here is that only sysadmins on the SQL Server can launch or
re-schedule SQL Agent jobs, so you are still stuck if you want to get
ordinary users to kick off a job on an ad-hoc basis.

One approach I have seen suggested is to have the job run on a frequent
basis and have the first step in the job check the status of a record in
a table. If a user has set a specific value in the table the package
will continue executing, otherwise it will exit.

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <FED3E20F-0747-4350-AAD6-4D8060DB9FA8 (AT) microsoft (DOT) com>,
Atrus2711 (AT) discussions (DOT) microsoft.com says...

Hi Darren,

thanks for your response. I guess I will implement the "trigger table" and
have a regular job check this table every 5 minutes .

Regards
Martin


"Darren Gosbell" wrote: