Production release methodology

Hi,

Our DBA group is debating production release methodology. We always
perfect our deployment package (typically a script) against the
database in a Staging environment, before executing the package
against Production. One side argues that the safest approach is to
create a script containing all schema changes, data changes, stored
procs, functions, etc. Run that script against Staging until it is
error-free. Then, when you run it against Production on Release Night
you know it will also be error-free, since Staging is a copy of
Production. However, any changes to the deployment, such as updates
to procs (and there are always a bunch in the pre-deployment period)
must be manually implemented on the script.

The other side wants to take advantage of the .NET environment. We
keep all procs, views, and functions in a Release folder on VSS,
execute a Get Latest Version (Recursive) from VisualStudio, and run
against Staging/Production. Any changes to the procs are
automatically propagated from VSS to VS, and there is no manual
editing of the script. You still need a script for table and data
changes. The "script everything" side of the debate feels this method
is not as reliable, especially since when views are nested, you will
get compile errors and must execute the run-on several times until all
the views compile. The "script" side feels that any errors are
unacceptable in a Production environment.

What is the opinion out there?

Thanks!"Theodore Feldman" <theodore.feldman@.fmglobal.com> wrote in message
news:26032dec.0401090715.1721f762@.posting.google.c om...
> Hi,
> Our DBA group is debating production release methodology. We always
> perfect our deployment package (typically a script) against the
> database in a Staging environment, before executing the package
> against Production. One side argues that the safest approach is to
> create a script containing all schema changes, data changes, stored
> procs, functions, etc. Run that script against Staging until it is
> error-free. Then, when you run it against Production on Release Night
> you know it will also be error-free, since Staging is a copy of
> Production. However, any changes to the deployment, such as updates
> to procs (and there are always a bunch in the pre-deployment period)
> must be manually implemented on the script.
> The other side wants to take advantage of the .NET environment. We
> keep all procs, views, and functions in a Release folder on VSS,
> execute a Get Latest Version (Recursive) from VisualStudio, and run
> against Staging/Production. Any changes to the procs are
> automatically propagated from VSS to VS, and there is no manual
> editing of the script. You still need a script for table and data
> changes. The "script everything" side of the debate feels this method
> is not as reliable, especially since when views are nested, you will
> get compile errors and must execute the run-on several times until all
> the views compile. The "script" side feels that any errors are
> unacceptable in a Production environment.
> What is the opinion out there?
> Thanks!

One other possible approach is to prepare your Staging database with the
latest tables and other objects, taken from VSS, then use a DB comparison
tool to generate a sync script for deployment to production. This can save a
lot of time in deployment, and also makes it much harder to 'forget' any
minor or last minute changes.You would still need a script for data
modifications, of course. I use the Red Gate tools in more or less that way,
and they work well:

http://www.red-gate.com/sql/summary.htm

But there are plenty of other ways to deploy code, so it's probably going to
come down to whatever works best for your team, given the tools and
knowledge you have available.

Simon|||"Theodore Feldman" <theodore.feldman@.fmglobal.com> wrote in message
news:26032dec.0401090715.1721f762@.posting.google.c om...
> Hi,
> Our DBA group is debating production release methodology. We always
> perfect our deployment package (typically a script) against the
> database in a Staging environment, before executing the package
> against Production. One side argues that the safest approach is to
> create a script containing all schema changes, data changes, stored
> procs, functions, etc. Run that script against Staging until it is
> error-free. Then, when you run it against Production on Release Night
> you know it will also be error-free, since Staging is a copy of
> Production. However, any changes to the deployment, such as updates
> to procs (and there are always a bunch in the pre-deployment period)
> must be manually implemented on the script.
> The other side wants to take advantage of the .NET environment. We
> keep all procs, views, and functions in a Release folder on VSS,
> execute a Get Latest Version (Recursive) from VisualStudio, and run
> against Staging/Production. Any changes to the procs are
> automatically propagated from VSS to VS, and there is no manual
> editing of the script. You still need a script for table and data
> changes. The "script everything" side of the debate feels this method
> is not as reliable, especially since when views are nested, you will
> get compile errors and must execute the run-on several times until all
> the views compile. The "script" side feels that any errors are
> unacceptable in a Production environment.
> What is the opinion out there?

The database is still central and will always be so.
The application environment changes every season.
It might have been VB last year but this year its .net.
This is history.

It is for ever a compromise under current methodologies,
but my opinion is that applications should be written with
more and more of the code outside the application and in
the database environment.

In the end, there will only be the database. The application
environment external to the rdbms is a redundancy. I would
not be fuelling a redundancy unless you dont have any other
options.

Pete Brown
Falls Creek
Oz|||We keep all SQL scripts under source control and build release packages
based on only labeled versions. This provides more control over what gets
promoted. We use a custom .Net program to run the scripts, control the
execution sequence and provide enhanced logging. One can achieve similar
results with OSQL.

I suggest you treat database implementation script development like you do
code - as an iterative build process. If you find errors, correct the
source controlled scripts, create another release package build and try
again against a fresh staging database until you get it right. This
discipline will ensure that the same stuff that was blessed in your QA/UAT
environment is the same that gets promoted.

Also, check out http://www.abaris.se/abaperls/index.html for a public domain
configuration management toolset. Even if you choose not to use it, it may
give you some ideas for automating the CM process.

--
Hope this helps.

Dan Guzman
SQL Server MVP

"Theodore Feldman" <theodore.feldman@.fmglobal.com> wrote in message
news:26032dec.0401090715.1721f762@.posting.google.c om...
> Hi,
> Our DBA group is debating production release methodology. We always
> perfect our deployment package (typically a script) against the
> database in a Staging environment, before executing the package
> against Production. One side argues that the safest approach is to
> create a script containing all schema changes, data changes, stored
> procs, functions, etc. Run that script against Staging until it is
> error-free. Then, when you run it against Production on Release Night
> you know it will also be error-free, since Staging is a copy of
> Production. However, any changes to the deployment, such as updates
> to procs (and there are always a bunch in the pre-deployment period)
> must be manually implemented on the script.
> The other side wants to take advantage of the .NET environment. We
> keep all procs, views, and functions in a Release folder on VSS,
> execute a Get Latest Version (Recursive) from VisualStudio, and run
> against Staging/Production. Any changes to the procs are
> automatically propagated from VSS to VS, and there is no manual
> editing of the script. You still need a script for table and data
> changes. The "script everything" side of the debate feels this method
> is not as reliable, especially since when views are nested, you will
> get compile errors and must execute the run-on several times until all
> the views compile. The "script" side feels that any errors are
> unacceptable in a Production environment.
> What is the opinion out there?
> Thanks!|||theodore.feldman@.fmglobal.com (Theodore Feldman) wrote in message news:<26032dec.0401090715.1721f762@.posting.google.com>...
> Hi,
> Our DBA group is debating production release methodology. We always
> perfect our deployment package (typically a script) against the
> database in a Staging environment, before executing the package
> against Production. One side argues that the safest approach is to
> create a script containing all schema changes, data changes, stored
> procs, functions, etc. Run that script against Staging until it is
> error-free. Then, when you run it against Production on Release Night
> you know it will also be error-free, since Staging is a copy of
> Production. However, any changes to the deployment, such as updates
> to procs (and there are always a bunch in the pre-deployment period)
> must be manually implemented on the script.
> The other side wants to take advantage of the .NET environment. We
> keep all procs, views, and functions in a Release folder on VSS,
> execute a Get Latest Version (Recursive) from VisualStudio, and run
> against Staging/Production. Any changes to the procs are
> automatically propagated from VSS to VS, and there is no manual
> editing of the script. You still need a script for table and data
> changes. The "script everything" side of the debate feels this method
> is not as reliable, especially since when views are nested, you will
> get compile errors and must execute the run-on several times until all
> the views compile. The "script" side feels that any errors are
> unacceptable in a Production environment.
> What is the opinion out there?
> Thanks!

We use www.red-gate.com to generate a script that would update
production to the current version of the staging database. This only
applies to the schema (and some static data tables).

The rest, ie procs, views, functions, etc comes direct from
SourceSafe. If there are dependencies, we either use alpabetical
ordering (default) or a custom script that applies inner
functions/views etc first.

We have also setup an nightly batch process that does a trial upgrade
from staging to production every night to pick up errors as soon as
possible.

To me it sounds like your DBAs are trying to keep themselves in a job.
Manually creating these scripts can be a time consuming, laborious and
uninteresting process. They used to use this process at a previous
role and we changed|||[posted and mailed, please reply in news]

Theodore Feldman (theodore.feldman@.fmglobal.com) writes:
> Our DBA group is debating production release methodology. We always
> perfect our deployment package (typically a script) against the
> database in a Staging environment, before executing the package
> against Production. One side argues that the safest approach is to
> create a script containing all schema changes, data changes, stored
> procs, functions, etc. Run that script against Staging until it is
> error-free. Then, when you run it against Production on Release Night
> you know it will also be error-free, since Staging is a copy of
> Production. However, any changes to the deployment, such as updates
> to procs (and there are always a bunch in the pre-deployment period)
> must be manually implemented on the script.
> The other side wants to take advantage of the .NET environment. We
> keep all procs, views, and functions in a Release folder on VSS,
> execute a Get Latest Version (Recursive) from VisualStudio, and run
> against Staging/Production. Any changes to the procs are
> automatically propagated from VSS to VS, and there is no manual
> editing of the script. You still need a script for table and data
> changes. The "script everything" side of the debate feels this method
> is not as reliable, especially since when views are nested, you will
> get compile errors and must execute the run-on several times until all
> the views compile. The "script" side feels that any errors are
> unacceptable in a Production environment.

I just finished another posting on CM issues, see the topic "Script
Question", which gives an outline of how we work in our shop. Here
I will just supplement with your specific issues.

Basically, we go the script way, but we have a tool which is smart enough
to permit regeneration of the script as well as manual tweaks. This gives
the best of both worlds.

A completely manually maintained script is a fragile solution, which is
open to casual mistakes, and risky.

If I did not have a tool at hand, I would probably start from your
..Net alternative, and then find solutions to problems like nested views.

I recall that there is a stored procedure builder that comes with the
SQL Server 2000 Resource Kit. I have never came around to evaluate it,
but I know it works from SourceSafe.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Product level is insufficient error

Configuration: Windows XP Pro with SQL 2005 Workgroup Sp2

Hi, we have a package that runs fine in BI Studio but fails with the following error when executing it using DTExec.

Code: 0xC00470FE
Source: Data Flow Task DTS.Pipeline
Description: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Derived Column" (10660).

The package imports a CSV into a table mapping some columns. The MSDN article at http://msdn2.microsoft.com/en-us/library/ms143761.aspx describes features supported by different versions.

The article says OLE DB source/destination adapters are supported in WG edition but a couple of lines later seems to imply that all source/destination adapters are not supported in WG.

Could you clarify whether stuff like import of a csv into a table with some column mappings should work in WG edition? Also if we have a legacy SQL 2K package doing the same thing, will that work in WG edition? Thx.

Features/Integration Services Enhancements EE (32-bit) DE (32-bit) EE (64-bit) DE (64-bit) SE (32-bit) WG (32-bit) SSE (32-bit) SSEA (32-bit) SE (64-bit)

SQL Server Import and Export Wizard and supporting connections, source and destination adapters, and tasks

Yes

Yes

Yes

No

Yes

Execute SQL Task

Yes

Yes

Yes

No

Yes

OLE DB Source and Destination Adapters

Yes

Yes

Yes

No

Yes

SSIS command prompt tools

Yes

Yes

Yes

No

Yes

SSIS Package Designer

Yes

Yes

Yes

No

Yes

Legacy support for DTS packages

Yes

Yes

Yes

Yes

Yes

SSIS Service

Yes

Yes

No

No

Yes

All other source and destination adapters, tasks, and transformations, except for those listed below

Yes

Yes

No

No

Yes

You might want to be sure that you have actually installed the full SSIS client.|||

As Phil wrote, most likely you've only Workstation components installed and need to install full SSIS.

See Books Online and my blog for details:

http://msdn2.microsoft.com/en-US/library/aa337371.aspx

http://blogs.msdn.com/michen/archive/2006/11/11/ssis-product-level-is-insufficient.aspx

Product Level is Insufficient

I am receiving the following error when I try to execute an SSIS package that is saved to a structured file. I am using DTExec to execute the package.

Description: The task "Initialize Variables" cannot run on this edition of Integration Services. It requires a higher level edition.

After some research, I was able to find a supporting article in SQL Server 2005 BOL at http://msdn2.microsoft.com/en-us/library/aa337371.aspx

The issue was resolved by installing the Enterprise Edition of SQL Server Integration Services (Windows Service) on the local server (server where the package is saved and executed from). However, this goes against my original anticipation that the SSIS Windows Service would only need to be installed on a machine where I needed to store packages and/or monitor package execution. Not if I wanted to execute packages.

Unfortunately, my package is using advanced options (as identified in the BOL article previously referenced).

Am I missing something?

Sincerely,

Sean Fitzgerald

You are trying to execute these packages from a remote machine (such as your desktop and not the SQL Server), correct? You need to have a matching edition of the SSIS client tools loaded on your desktop to be able to run those packages remotely.|||You do need the SSIS installed where the packages runs.
It does not matter where the package is stored.

See my blog entries about this:
http://blogs.msdn.com/michen/archive/2006/08/11/package-exec-location.aspx
http://blogs.msdn.com/michen/archive/2006/11/11/ssis-product-level-is-insufficient.aspx

Processing of AS2005 cube from Integration Services package: Operation completed with 882 proble

Hi!

I did not now if I should post it in the Integration Services forum, but I believe this post is more AS related. Anyway, I am processing my cubes in SSIS after some loading of data. I use the SSIS log provider for SQL Server to log errors, and I get the following error message in the message column of a row in sysdtslog90:

"Server: Operation completed with 882 problems logged."

I wonder, where can I find this log? Is there some default location in AS or do I have to enable another log event than OnError or OnWarning in SSIS?

Thanks!

I'm guessing I'm looking for the Dimension key error log path when it is set for (default).

I found something here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1284202&SiteID=1

Seems like you have to set the location in C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Config\msmdsrv.ini. Now I get a key error logfile, but it is empty =/. I've restarted the AS service and set the ErrorLog elements in the ini to:

<ErrorLog>
<ErrorLogFileName>OLAPErrorLog.log</ErrorLogFileName>
<ErrorLogFileSize>4</ErrorLogFileSize>
<KeyErrorAction>0</KeyErrorAction>
<KeyErrorLogFile>KeyErrorLogFile.log</KeyErrorLogFile>
<KeyErrorLimit>0</KeyErrorLimit>
<KeyErrorLimitAction>0</KeyErrorLimitAction>
<LogErrorTypes>
<KeyNotFound>1</KeyNotFound>
<KeyDuplicate>0</KeyDuplicate>
<NullKeyConvertedToUnknown>0</NullKeyConvertedToUnknown>
<NullKeyNotAllowed>1</NullKeyNotAllowed>
</LogErrorTypes>
<IgnoreDataTruncation>0</IgnoreDataTruncation>
</ErrorLog>

I've also tested the following without success:

<ErrorLog>
<ErrorLogFileName>OLAPErrorLog.log</ErrorLogFileName>
<ErrorLogFileSize>4000000</ErrorLogFileSize>
<KeyErrorAction>1</KeyErrorAction>
<KeyErrorLogFile>KeyErrorLogFile.log</KeyErrorLogFile>
<KeyErrorLimit>1</KeyErrorLimit>
<KeyErrorLimitAction>1</KeyErrorLimitAction>
<LogErrorTypes>
<KeyNotFound>1</KeyNotFound>
<KeyDuplicate>1</KeyDuplicate>
<NullKeyConvertedToUnknown>1</NullKeyConvertedToUnknown>
<NullKeyNotAllowed>1</NullKeyNotAllowed>
</LogErrorTypes>
<IgnoreDataTruncation>0</IgnoreDataTruncation>
</ErrorLog>

More info here, but it does not get you that much wiser: http://technet.microsoft.com/en-us/library/ms174827.aspx

Seems like you do have to set the ErrorLog properties manually for each cube (Process > Change Settings > Use custom error configuration).

Processing cubes on a different server, using SSIS package run by a SQL Agent job from another s

Hi,

I am faced with this issue in a production environment. I have to implement an architecture where the Analysis Services database is in a server different from the server on which the SQL Serever database it accesses for data is.

I have changed the connection string for the data source in the Analysis Services database to point to the other server's SQL Server database. Log on to this server has been set to use SQL Server Authentication.

Then I created an SSIS package on the server containing SQL Server database, to process a dimension in the other server's Analysis Services database. The Analysis Services connection manager in this package was set to log on to the Analysis Services database on the other server using 'Specific User name and Password'. This user is a part of the administrator group on the server containing Analysis Services database. The package executed fine when executed from the Business Intelligence Studio.

The problem came when I tried to execute this package through a SQL agent job. The job is created on the server containing the SQL Server database. The step in the job meant to execute the package uses 'SQL Agent Service Account' for the 'Run as' option. The package was deployed as 'File System'.

I missed out posting the error message I am getting. It is as follows:

Code: 0x00000000 Description: A connection cannot be made. Ensure that the server is running.

Hope this helps to give a better understanding of the problem.

Thanks.

|||

Hi,

The problem was resolved by changing the LOG ON for the SSIS service to that of an user who is administrator on both the machines.

|||

Did you have to create a Credential and Proxy? I had to create one and set the Run As parameter for the step in Agent to the Proxy name. The job has to write a file to a network directory and from what I read it seems that the only way for an SSIS job to access anything outside SQL Server was by using a proxy. I am not sure if the same applied in your situation.

|||

Hmm.... I was helped by the fact that the OS was installed with a network administrator id. So no new credentials or proxy was required. The run as parameter for my job's step remained as "SQL Agent Service Account" and changed the Log On for SSIS service to use network administrator account. Hope this helps.

I would like to know how you created a proxy and made the Run As parameter to point to it.

Regards,

Emil

Processing cubes on a different server, using SSIS package run by a SQL Agent job from another s

Hi,

I am faced with this issue in a production environment. I have to implement an architecture where the Analysis Services database is in a server different from the server on which the SQL Serever database it accesses for data is.

I have changed the connection string for the data source in the Analysis Services database to point to the other server's SQL Server database. Log on to this server has been set to use SQL Server Authentication.

Then I created an SSIS package on the server containing SQL Server database, to process a dimension in the other server's Analysis Services database. The Analysis Services connection manager in this package was set to log on to the Analysis Services database on the other server using 'Specific User name and Password'. This user is a part of the administrator group on the server containing Analysis Services database. The package executed fine when executed from the Business Intelligence Studio.

The problem came when I tried to execute this package through a SQL agent job. The job is created on the server containing the SQL Server database. The step in the job meant to execute the package uses 'SQL Agent Service Account' for the 'Run as' option. The package was deployed as 'File System'.

I missed out posting the error message I am getting. It is as follows:

Code: 0x00000000 Description: A connection cannot be made. Ensure that the server is running.

Hope this helps to give a better understanding of the problem.

Thanks.

|||

Hi,

The problem was resolved by changing the LOG ON for the SSIS service to that of an user who is administrator on both the machines.

|||

Did you have to create a Credential and Proxy? I had to create one and set the Run As parameter for the step in Agent to the Proxy name. The job has to write a file to a network directory and from what I read it seems that the only way for an SSIS job to access anything outside SQL Server was by using a proxy. I am not sure if the same applied in your situation.

|||

Hmm.... I was helped by the fact that the OS was installed with a network administrator id. So no new credentials or proxy was required. The run as parameter for my job's step remained as "SQL Agent Service Account" and changed the Log On for SSIS service to use network administrator account. Hope this helps.

I would like to know how you created a proxy and made the Run As parameter to point to it.

Regards,

Emil

Processing cubes on a different server, using SSIS package run by a SQL Agent job from another s

Hi,

I am faced with this issue in a production environment. I have to implement an architecture where the Analysis Services database is in a server different from the server on which the SQL Serever database it accesses for data is.

I have changed the connection string for the data source in the Analysis Services database to point to the other server's SQL Server database. Log on to this server has been set to use SQL Server Authentication.

Then I created an SSIS package on the server containing SQL Server database, to process a dimension in the other server's Analysis Services database. The Analysis Services connection manager in this package was set to log on to the Analysis Services database on the other server using 'Specific User name and Password'. This user is a part of the administrator group on the server containing Analysis Services database. The package executed fine when executed from the Business Intelligence Studio.

The problem came when I tried to execute this package through a SQL agent job. The job is created on the server containing the SQL Server database. The step in the job meant to execute the package uses 'SQL Agent Service Account' for the 'Run as' option. The package was deployed as 'File System'.

I missed out posting the error message I am getting. It is as follows:

Code: 0x00000000 Description: A connection cannot be made. Ensure that the server is running.

Hope this helps to give a better understanding of the problem.

Thanks.

|||

Hi,

The problem was resolved by changing the LOG ON for the SSIS service to that of an user who is administrator on both the machines.

|||

Did you have to create a Credential and Proxy? I had to create one and set the Run As parameter for the step in Agent to the Proxy name. The job has to write a file to a network directory and from what I read it seems that the only way for an SSIS job to access anything outside SQL Server was by using a proxy. I am not sure if the same applied in your situation.

|||

Hmm.... I was helped by the fact that the OS was installed with a network administrator id. So no new credentials or proxy was required. The run as parameter for my job's step remained as "SQL Agent Service Account" and changed the Log On for SSIS service to use network administrator account. Hope this helps.

I would like to know how you created a proxy and made the Run As parameter to point to it.

Regards,

Emil

Processing AS2000 Cubes from SSIS

Hi All,

I have a scenario where I want to execute AS 2000 Cubes from a SSIS package. In my Prod environment I have two servers one with the SQL 2000 database and the AS2000 cubes on it and the other with SSIS installed on it.

What I am doing here is I have a DTS package with a process cube task in it, this DTS package is saved as a structured file and then I call this DTS package from SSIS using the Execurte 2000 package task. Just FYI the process cubes task is using local as the server reference. I want to know how this will work when I execute this DTS package from within an SSIS package running on a different server? Appreciate all help.

Thanks

The "normal" way to process AS 2000 from DTS was to use the OLAP Processing task for the job, but that only gets installed as part of AS 2000, and hence will not be available on your SSIS/DTS machine. Using local as the server reference will also fail, unless you run the DTS package on the AS server, as quite obviously the local server is not the AS server, for a package running on SSIS/DTS machine. There is no magic way to get the DTS package to run on the other machine, other than calling the package from that machine itself. I would stick with a DTS package on the AS2000 box.

|||

Thanks Darren,

Actually I do have DTS and AS2000 installed on the same server which also has SQL Server 2000 databases on it, However I am executing these DTS packages (which process the cubes using local as server reference) from SSIS packages which are running on a different server. The DTS packages are saved as structured files on the SSIS server. Hope I am explaining it properly - what my concern is, whether executing these DTS packages having process cubes task within it from a different server will work?

Appreciate your help.

Thanks

|||

I Still have this concern whether my packages will run or not, it would be better to know now rather than getting to know in prod. Any help is appreciated.

Thanks

|||No this will not work. All the AS stuff is on the wrong server, it needs to be on the server upon which the DTS package runs. If calling DTS from SSIS then that means the DTS package runs on the same server as SSIS, which is not the AS server. This is all about execution location, which for both DTS and SSIS is cleint side, they are not client/server like SQL Server.|||

Thanks Darren,

Appreciate your help.

Thanks

|||

Hi,

I have a Cube on my AS2000 server running on the same machine as my SQL server 2000. I can execute the DTS from the SQL Enterprise manager properly.

I need to implement a C# code that will enable me to execute the DTS. I already have one as follows which works on any DTS:

---

Package2Class package = new Package2Class();

object pVarPersistStgOfHost = null;

package.LoadFromSQLServer(serverName,null,null,DTSSQLServerStorageFlags.DTSSQLStgFlag_UseTrustedConnection,null,null,null,packageName,ref pVarPersistStgOfHost);

package.Execute();

---

As I said, it works with any DTS, but as soon as I work with one which Processes Cubes, it hangs for about 2 hours, when the cube can normally be processed in 20 seconds, and crash on the following

DTS Execution error:

Do you have a clue why is it so please?

|||

I've been thinking about this some more. As I recall you can process OLAP 200 cubes remotely, well I think you could in DTS, so all you need is -

1 DTS

2 DSO

3 OLAP Task

Now in SSIS we have 1 already. 2 we can get, see the feature pack download on MS site April or November. For 3, the task, it seems that the documenattion says you need to install AS 200 to get this, well as I recall it was actually just a DTS custom task that used DSO, so why not go get the DLL, register it by hand in DTS, and give it a try -

The task DLL should be in X:\Program Files\Microsoft Analysis Services\Bin\msmdtsp.dll on any SQL 2000 box with AS installed.

|||

Darren,

I am using SQL Server 2000. I do not have SSIS and I have to get this sorted way before we upgrade to 2005.

1. Are there any issues with the methods LoadFromSQLServer from the class Package2Class when we invoke a DTS with OLAP Cube.

2. I have already installed Analysis Services. When I deployed my application to a test web server which has SQL client installed, I have a COM exception. Does it mean that I need to have AS2000 installed in order for LoadFromSQLServer to instantiate the correct steps object which are of type OLAP tasks?

Can you please advise me on the coding and permission stuff that will allow a code on .net 1.1 (since it is an upgrade on a legacy system) to launch a DTS on SQL2000 which processes a cube on AS2000?

Thanks

WaaZ

|||

WaaZ, I was replying to the thread from db_guy. I'm not sure why you have posted a DTS question in the SSIS forum, and it is not really the same issue anyway, as you are not using SSIS at all. A better thread would make more sense to start with, but this is a SSIS focused forum I'm afraid. I can branch into a new thread if you want.

1 - No issues with that method that would not be raised if using another execution host in the same location and context. Instead of running your application, try running DTSRUN in the same place, as the same user, and see what errors you get.

2 - To load a DTS package, you need DTS installed locally. If you use the AS Proc Task, then you need AS support and the AS task also installed locally.

|||

Thanks Darren,

Finally we decided that we will be processing the cubes using DTS and not SSIS, but I will surely try to test the stuff you mentioned , will let you know soon.

Thanks

Processing AS2000 Cubes from SSIS

Hi All,

I have a scenario where I want to execute AS 2000 Cubes from a SSIS package. In my Prod environment I have two servers one with the SQL 2000 database and the AS2000 cubes on it and the other with SSIS installed on it.

What I am doing here is I have a DTS package with a process cube task in it, this DTS package is saved as a structured file and then I call this DTS package from SSIS using the Execurte 2000 package task. Just FYI the process cubes task is using local as the server reference. I want to know how this will work when I execute this DTS package from within an SSIS package running on a different server? Appreciate all help.

Thanks

The "normal" way to process AS 2000 from DTS was to use the OLAP Processing task for the job, but that only gets installed as part of AS 2000, and hence will not be available on your SSIS/DTS machine. Using local as the server reference will also fail, unless you run the DTS package on the AS server, as quite obviously the local server is not the AS server, for a package running on SSIS/DTS machine. There is no magic way to get the DTS package to run on the other machine, other than calling the package from that machine itself. I would stick with a DTS package on the AS2000 box.

|||

Thanks Darren,

Actually I do have DTS and AS2000 installed on the same server which also has SQL Server 2000 databases on it, However I am executing these DTS packages (which process the cubes using local as server reference) from SSIS packages which are running on a different server. The DTS packages are saved as structured files on the SSIS server. Hope I am explaining it properly - what my concern is, whether executing these DTS packages having process cubes task within it from a different server will work?

Appreciate your help.

Thanks

|||

I Still have this concern whether my packages will run or not, it would be better to know now rather than getting to know in prod. Any help is appreciated.

Thanks

|||No this will not work. All the AS stuff is on the wrong server, it needs to be on the server upon which the DTS package runs. If calling DTS from SSIS then that means the DTS package runs on the same server as SSIS, which is not the AS server. This is all about execution location, which for both DTS and SSIS is cleint side, they are not client/server like SQL Server.|||

Thanks Darren,

Appreciate your help.

Thanks

|||

Hi,

I have a Cube on my AS2000 server running on the same machine as my SQL server 2000. I can execute the DTS from the SQL Enterprise manager properly.

I need to implement a C# code that will enable me to execute the DTS. I already have one as follows which works on any DTS:

---

Package2Class package = new Package2Class();

object pVarPersistStgOfHost = null;

package.LoadFromSQLServer(serverName,null,null,DTSSQLServerStorageFlags.DTSSQLStgFlag_UseTrustedConnection,null,null,null,packageName,ref pVarPersistStgOfHost);

package.Execute();

---

As I said, it works with any DTS, but as soon as I work with one which Processes Cubes, it hangs for about 2 hours, when the cube can normally be processed in 20 seconds, and crash on the following

DTS Execution error:

Do you have a clue why is it so please?

|||

I've been thinking about this some more. As I recall you can process OLAP 200 cubes remotely, well I think you could in DTS, so all you need is -

1 DTS

2 DSO

3 OLAP Task

Now in SSIS we have 1 already. 2 we can get, see the feature pack download on MS site April or November. For 3, the task, it seems that the documenattion says you need to install AS 200 to get this, well as I recall it was actually just a DTS custom task that used DSO, so why not go get the DLL, register it by hand in DTS, and give it a try -

The task DLL should be in X:\Program Files\Microsoft Analysis Services\Bin\msmdtsp.dll on any SQL 2000 box with AS installed.

|||

Darren,

I am using SQL Server 2000. I do not have SSIS and I have to get this sorted way before we upgrade to 2005.

1. Are there any issues with the methods LoadFromSQLServer from the class Package2Class when we invoke a DTS with OLAP Cube.

2. I have already installed Analysis Services. When I deployed my application to a test web server which has SQL client installed, I have a COM exception. Does it mean that I need to have AS2000 installed in order for LoadFromSQLServer to instantiate the correct steps object which are of type OLAP tasks?

Can you please advise me on the coding and permission stuff that will allow a code on .net 1.1 (since it is an upgrade on a legacy system) to launch a DTS on SQL2000 which processes a cube on AS2000?

Thanks

WaaZ

|||

WaaZ, I was replying to the thread from db_guy. I'm not sure why you have posted a DTS question in the SSIS forum, and it is not really the same issue anyway, as you are not using SSIS at all. A better thread would make more sense to start with, but this is a SSIS focused forum I'm afraid. I can branch into a new thread if you want.

1 - No issues with that method that would not be raised if using another execution host in the same location and context. Instead of running your application, try running DTSRUN in the same place, as the same user, and see what errors you get.

2 - To load a DTS package, you need DTS installed locally. If you use the AS Proc Task, then you need AS support and the AS task also installed locally.

|||

Thanks Darren,

Finally we decided that we will be processing the cubes using DTS and not SSIS, but I will surely try to test the stuff you mentioned , will let you know soon.

Thanks

Processing a cube on SQL server 2005 from a dts package on SQL server 2000

We just started migrating some cubes to the 2005 platform. Still there are some DTS packages running on the 2000 platform that needs some recoding to fit the 2005 enviroment. Therefore we have some solutions where we have DTS packages running on SQL Server 2000 and their "related" cubes running on the 2005 platform.

My question is therefore: Is there an easy way to initiate a processing of a cube on the 2005 platform from a Sql server 2000 DTS package ?

Hmm seems that there are no easy way|||

Hello cgpl,

I think this may be of help to you: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=265208&SiteID=1

-Jamie

Processing a cube on SQL server 2005 from a dts package on SQL server 2000

We just started migrating some cubes to the 2005 platform. Still there are some DTS packages running on the 2000 platform that needs some recoding to fit the 2005 enviroment. Therefore we have some solutions where we have DTS packages running on SQL Server 2000 and their "related" cubes running on the 2005 platform.

My question is therefore: Is there an easy way to initiate a processing of a cube on the 2005 platform from a Sql server 2000 DTS package ?

Hmm seems that there are no easy way|||

Hello cgpl,

I think this may be of help to you: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=265208&SiteID=1

-Jamie

Processing a cube on SQL server 2005 from a dts package on SQL server 2000

We just started migrating some cubes to the 2005 platform. Still there are some DTS packages running on the 2000 platform that needs some recoding to fit the 2005 enviroment. Therefore we have some solutions where we have DTS packages running on SQL Server 2000 and their "related" cubes running on the 2005 platform.

My question is therefore: Is there an easy way to initiate a processing of a cube on the 2005 platform from a Sql server 2000 DTS package ?

Hmm seems that there are no easy way|||

Hello cgpl,

I think this may be of help to you: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=265208&SiteID=1

-Jamie

Process exit code:1073741819

I have changed a SSIS package last week. Now, I met the problem that the package sometimes failed both in SQL agent and the BIDs.

SQL agent just give the detail: Process Exit Code -1073741819. The step failed.

In BIDs,when I Check the log,there is even no error. But the last Infomation in the output windows is the package canceled. It just like somebody stop running package manually.

The more strange thing is the package sometimes succeed with running the same data.

Thanks for your help

We have a build process (using Visual Build Pro) that has magically developed a problem. When building one of our installers (using the InstallShield project step) it fails with the message "Process completed with exit code -1073741819". However, there is no error actual thrown during the building of the installer by InstallShield.

I have set the step to log the command line being executed and have manually run that exact command line in a command prompt. This completes with no problems. The project also compiles no problem with the InstallShield GUI, so there should really be no problem compiling it with the command line.

So the next thing I did was to use a Call Program step and pasted that same command line call into it. Same error message as the InstallShield project step that I mentioned above.

Then I tried modifying that Call Program step and made it call: %DOSCMD% call "C:\Program Files... so that it would actually pass it to a command prompt for execution. This works. So I found a work around.

I Googled this error number in correspondance with Visual Build and InstallShield but found nothing helpful. The only thing I did find talked about handling the step finished event and overriding that error number as a successful step. However, the project hasn't fully finished building at this point, so it really wasn't successful. We need it to actually build the installer.

We have also determined that this is NOT a problem with any changes made to the installer project or build file as we reran a previous build that had succeeded and now also gets that same error message.

The only change that I am aware of that was done to that machine was that it was rebooted since the last successful build (which was yesterday morning). So unless a Microsoft patch was installed that I was unaware of or someone else installed something (unlikely since I am really one of only two people who uses that box and the other guy didn't install anything on it), nothing has been installed/uninstalled from it.

I do not believe this is specifically an InstallShield problem as it builds fine using the exact command line that the step is trying to execute. I think Visual Build is picking up a return code from the InstallShield output that it shouldn't be.

Has anyone else experienced this or knows the fix for it?

Visual Build Pro v6.1
InstallShield v11.5

One more note: we did experience this same error message about a month or so ago as well. At that time we had InstallShield 10.5 as well as 11.5 on the box. Uninstalling 10.5 fixed the problem at that time. As stated above, I am not aware of anything being installed to or uninstalled from the box since yesterday morning.

from:http://www.kinook.com/Forum/showthread.php?threadid=1791|||Thanks for your reply.
The error that I've post is taken after I've checked "Show step
details". OK, I'll post the error again completely :

Executed as user: XXXX\xxxx. ...un OnStart:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart:
DTSStep_DTSDataPumpTask_1 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_4
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_4
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_4
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTS... Process
Exit Code -1073741819. The step failed.

from:http://www.thescripts.com/forum/thread155774.html|||That's pretty anonymous. Unfortunately I don't know DTS, so I don't
have any suggestions to offer. Maybe the people in
microsoft.public.sqlserver.dts has any ideas.

from:|||--------------------------------------------------------------------------------

Some Googling suggests that the error may be caused by a Windows bug:

http://support.microsoft.com/defaul...kb;EN-US;306497
http://groups-beta.google.com/group...lr=&sa=N&tab=wg

If you don't already have the latest servicepacks for Windows and
MSSQL, it would probably be worth installing them to see if that
resolves the issue. Since a few people seem to have seen this error in
connection with a virus infection, that would be something else to
check. If this doesn't help, then it might be worth calling Microsoft.|||I think you are encountering a bug in the BOINC API Library. This is partly fixed in an Einstein@.Home beta test application available from the Einstein@.Home front page (bottom left hand corner). Please spend a few minutes and install this. Walt Gribben recently tracked down (this week) and fixed the remainder of this problem, so in the next couple of weeks we should be able to release a new application that hopefully takes care of this problem entirely.

from:http://einstein.phys.uwm.edu/forum_thread.php?id=2888|||Hi, Do you have an ATI graphics card per chance?

I have this installed on my new P4 3.0ghz machine with an ATI x600 PCI Express card and it will not run the globe graphics. It will run seti, but I get a very similar message to you when I interupt the screesaver to do some work.

I have boinc on a P4 2.53ghz machine with a Nvidia 5900 agb board and it works fine.

Please can someone sort out the ati issues.|||I keep getting compute errors, eventhough I do not get compute errors on S@.H or P@.H. One example is below. This particular failure cost me 29000 secs of work. I'm using a notebook on this, so the computer is off and on several times a day.

4.45
The semaphore cannot be set again. (0x67) - exit code 103 (0x67)

detected finished Fstat file - skipping Fstat run 1
Resuming computation at 19947/1715206/1726153
ERROR! sftIndex = -1076102
|||As Bernd Machenschalk suggested to Andrew Dickey in the preceding posts, maybe you should try the Beta Application. Einstein 4.79 (which I presume you are running) is not completely "up to speed" with BOINC 4.45. There is a known "graphics" bug related to running the two and Client error Computing messages are a common symptom. The Beta App fixes the "graphics" bug. The link to it is under More Informationon the E@.H home page.
|||I am surprised and disappointed too. The Beta App worked for me (and others also). Your error report is a new on me. Hopefully, you will get a response from one of the developers soon. A bit of warning - they will probably ask you to "unhide" your computer so they can have access to more info about the problem. If you are a little uneasy about this, I suggest you click on my name and check out the type of information that is made available when you do this. Good luck! I hope you get things straightened out soon.|||Did you get any 0xC0000005 errors with the .018 version? The one you reported in the other thread looks like a completely different error. It would be nice to know whether your other WU's - the ones with 0xC0000005 errors - were crunched with 0.18 or an earlier version.
|||Damn! It failed again, with yet another error statement. This time, I put the notebook into hibernation, went home, resumed using the wireless rather than the hardwire network connection, and checked about an hour later. The damn thing bombed again. Now I have a bundle of P@.H's to do before the next E@.H wu is started. I'm really wasting cycles with this problem.

Here is what it said...
Resuming computation at 3903/180714/204114
No heartbeat from core client for 31 sec - exiting
detected finished Fstat file - skipping Fstat run 1
Resuming computation at 7991/499486/502366

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x004097A7 read attempt to address 0x2E5EBC90

1: 10/01/05 19:59:55
1: c:cygwinhomebemaeinsteinathomecfswindows_build.18cfslaldemod.c(854) +20 bytes (TestLALDemod)
1: c:cygwinhomebemaeinsteinathomecfswindows_build.18computefstatistic.c(728) +28 bytes (boincmain)
1: c:cygwinhomebemaeinsteinathomecfswindows_build.18computefstatistic.c(3082) +20 bytes (worker)
1: c:cygwinhomebemaeinsteinathomecfswindows_build.18boincapigraphics_impl.c(75) +0 bytes (foobar)|||Thanks for answer. Yesterday, without screensaver mode I had first good result in Einstein@.home (wheras LHC@.home and SETI@.home work continuously without errors). Then I changed to Einstein 0.18 and to newest 7.8.0.1. driver for my NIVIDA Geforce FX 5200 graphic card and leaved project for night working and Unfotunatelly I had the same error messages in the mornig as before:

1.Application error. Memory can't be written.

2.2005-10-02 09:59:41|Einstein@.Home|Unrecoverable error for result l1_1317.0__1317.4_0.1_T09_S4lB_2 ( - exit code -1073741819 (0xc0000005))

Einstein obviously does'nt want to work at night ;) and I'm starting to think, that in such cases maby more effectively for humanity science at whole ist switching immediatelly to another project than spending hours on finding some error. I'm asking myself: Why to repair some tool (maby computer??)if it can work as another tool, without any additional effort ?|||Thanks for answer. Yesterday, without screensaver mode I had first good result in Einstein@.home (wheras LHC@.home and SETI@.home work continuously without errors). Then I changed to Einstein 0.18 and to newest 7.8.0.1. driver for my NIVIDA Geforce FX 5200 graphic card and leaved project for night working and Unfotunatelly I had the same error messages in the mornig as before:

1.Application error. Memory can't be written.

2.2005-10-02 09:59:41|Einstein@.Home|Unrecoverable error for result l1_1317.0__1317.4_0.1_T09_S4lB_2 ( - exit code -1073741819 (0xc0000005))

Einstein obviously does'nt want to work at night ;) and I'm starting to think, that in such cases maby more effectively for humanity science at whole ist switching immediatelly to another project than spending hours on finding some error. I'm asking myself: Why to repair some tool (maby computer??)if it can work as another tool, without any additional effort ?[/quote]

I am sorry it didn't work. Obviously, the Beta App doesn't fix all the BOINC 4.45/Einstein 4.79 bugs. I suggest you post your problem and error message on the Beta App Message Board [Message boards : Cafe Einstein : NEW: WINDOWS TEST APPLICATION FOR EINSTEIN@.HOME]. In the meantime, I guess reverting back to 4.79 without graphics is the way to go.|||Did you find an answer?
I am struggling with the same problem...

Process exit code:1073741819

I have changed a SSIS package last week. Now, I met the problem that the package sometimes failed both in SQL agent and the BIDs.

SQL agent just give the detail: Process Exit Code -1073741819. The step failed.

In BIDs,when I Check the log,there is even no error. But the last Infomation in the output windows is the package canceled. It just like somebody stop running package manually.

The more strange thing is the package sometimes succeed with running the same data.

Thanks for your help

I have the same query, please help somebody..

Thanks,

|||

Is there anyone who can help us with this?

|||Be sure you have package logging turned on. If so, are there any errors in the log?

Process exit code:1073741819

I have changed a SSIS package last week. Now, I met the problem that the package sometimes failed both in SQL agent and the BIDs.

SQL agent just give the detail: Process Exit Code -1073741819. The step failed.

In BIDs,when I Check the log,there is even no error. But the last Infomation in the output windows is the package canceled. It just like somebody stop running package manually.

The more strange thing is the package sometimes succeed with running the same data.

Thanks for your help

I have the same query, please help somebody..

Thanks,

|||

Is there anyone who can help us with this?

|||Be sure you have package logging turned on. If so, are there any errors in the log?

Process Cube using SQL DTS

Hi
I have created a package to do this which simply returns with the error
'1 task(s) failed during execution'. I can process the dimensions and
cubes manually in analysis Manager fine.
SQL and analysis Manager are both on the same server and the task
appears to be running with the domain administrator user.
Cany anyone help?
Cheers
Brettos.
brettos
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message542345.html
In workflow properties, set "Execute on main package thread", including all
packages that contains OLAP processing.
James Ma
"brettos" wrote:

> Hi
> I have created a package to do this which simply returns with the error
> '1 task(s) failed during execution'. I can process the dimensions and
> cubes manually in analysis Manager fine.
> SQL and analysis Manager are both on the same server and the task
> appears to be running with the domain administrator user.
> Cany anyone help?
> Cheers
> Brettos.
>
> --
> brettos
> Posted via http://www.webservertalk.com
> View this thread: http://www.webservertalk.com/message542345.html
>
|||To help in your debuging.
Open The package in design mode.
Right Click and Select "Package Properties"
Select The "Logging" tab.
Provide a log file location to use during processing of the package.
save and close the package.
Now run the package.
Open the log file and see what details you can gleam.
report back to us.
Hope this helps.
dlr
"brettos" <brettos.1gk5p2@.mail.webservertalk.com> wrote in message
news:brettos.1gk5p2@.mail.webservertalk.com...
> Hi
> I have created a package to do this which simply returns with the error
> '1 task(s) failed during execution'. I can process the dimensions and
> cubes manually in analysis Manager fine.
> SQL and analysis Manager are both on the same server and the task
> appears to be running with the domain administrator user.
> Cany anyone help?
> Cheers
> Brettos.
>
> --
> brettos
> Posted via http://www.webservertalk.com
> View this thread: http://www.webservertalk.com/message542345.html
>

Process Cube using SQL DTS

Hi
I have created a package to do this which simply returns with the error '1 t
ask(s) failed during execution'. I can process the dimensions and cubes man
ually in analysis Manager fine.
SQL and analysis Manager are both on the same server and the task appears to
be running with the domain administrator user.
Cany anyone help?
Cheers
Brettos.In workflow properties, set "Execute on main package thread", including all
packages that contains OLAP processing.
James Ma
"brettos" wrote:

> Hi
> I have created a package to do this which simply returns with the error
> '1 task(s) failed during execution'. I can process the dimensions and
> cubes manually in analysis Manager fine.
> SQL and analysis Manager are both on the same server and the task
> appears to be running with the domain administrator user.
> Cany anyone help?
> Cheers
> Brettos.
>
> --
> brettos
> ---
> Posted via http://www.webservertalk.com
> ---
> View this thread: http://www.webservertalk.com/message542345.html
>|||To help in your debuging.
Open The package in design mode.
Right Click and Select "Package Properties"
Select The "Logging" tab.
Provide a log file location to use during processing of the package.
save and close the package.
Now run the package.
Open the log file and see what details you can gleam.
report back to us.
Hope this helps.
dlr
"brettos" <brettos.1gk5p2@.mail.webservertalk.com> wrote in message
news:brettos.1gk5p2@.mail.webservertalk.com...
> Hi
> I have created a package to do this which simply returns with the error
> '1 task(s) failed during execution'. I can process the dimensions and
> cubes manually in analysis Manager fine.
> SQL and analysis Manager are both on the same server and the task
> appears to be running with the domain administrator user.
> Cany anyone help?
> Cheers
> Brettos.
>
> --
> brettos
> ---
> Posted via http://www.webservertalk.com
> ---
> View this thread: http://www.webservertalk.com/message542345.html
>

Process constantly polling the tmw_queue table looking for work to do

I have created a package that will backup prod. database and restore
dev. database.
The job failed because there is a process constantly polling for work
to do.
How can I have the job kill this process, put database in single user
mode and then restore database?
Isabel
Use ALTER DATABASE to set restricted user or single user and the ROLLBACK option of ALTER DATABASE
(see Books Online for syntax).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"confused" <isabelellis@.hotmail.com> wrote in message
news:1133543598.767838.12810@.o13g2000cwo.googlegro ups.com...
>I have created a package that will backup prod. database and restore
> dev. database.
> The job failed because there is a process constantly polling for work
> to do.
> How can I have the job kill this process, put database in single user
> mode and then restore database?
> Isabel
>

Process constantly polling the tmw_queue table looking for work to do

I have created a package that will backup prod. database and restore
dev. database.
The job failed because there is a process constantly polling for work
to do.
How can I have the job kill this process, put database in single user
mode and then restore database?
IsabelUse ALTER DATABASE to set restricted user or single user and the ROLLBACK op
tion of ALTER DATABASE
(see Books Online for syntax).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"confused" <isabelellis@.hotmail.com> wrote in message
news:1133543598.767838.12810@.o13g2000cwo.googlegroups.com...
>I have created a package that will backup prod. database and restore
> dev. database.
> The job failed because there is a process constantly polling for work
> to do.
> How can I have the job kill this process, put database in single user
> mode and then restore database?
> Isabel
>

Process constantly polling the tmw_queue table looking for work to do

I have created a package that will backup prod. database and restore
dev. database.
The job failed because there is a process constantly polling for work
to do.
How can I have the job kill this process, put database in single user
mode and then restore database?
IsabelUse ALTER DATABASE to set restricted user or single user and the ROLLBACK option of ALTER DATABASE
(see Books Online for syntax).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"confused" <isabelellis@.hotmail.com> wrote in message
news:1133543598.767838.12810@.o13g2000cwo.googlegroups.com...
>I have created a package that will backup prod. database and restore
> dev. database.
> The job failed because there is a process constantly polling for work
> to do.
> How can I have the job kill this process, put database in single user
> mode and then restore database?
> Isabel
>