I had scheduled data transfer and backup jobs that could not complete
executing as there was not enough disk space. On stopping the jobs the
process associated with it did not clear out from the Current Activity
Process Info window. I tried stopping and starting the SQL Agent and also
killing the processes but the processed associated with those jobs still show
up in the Current Activity - Process Info window of Enterprise Manager.
I have created disk space on the drives that were running out of space.
What should I do to kill those processes.
KT
Two thoughts here:
First did you refresh your current activity view? Second is there some
process are there any blocking processes. Sometimes a process might be
running that is blocking the processes you are trying to kill. In this case
those killed processes will not die, until the process that is causing the
block is no longer blocking.
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"KT" <KT@.discussions.microsoft.com> wrote in message
news:4EDD5693-2DAC-4CC9-B9E6-DE745EF630BF@.microsoft.com...
> I had scheduled data transfer and backup jobs that could not complete
> executing as there was not enough disk space. On stopping the jobs the
> process associated with it did not clear out from the Current Activity
> Process Info window. I tried stopping and starting the SQL Agent and also
> killing the processes but the processed associated with those jobs still
show
> up in the Current Activity - Process Info window of Enterprise Manager.
> I have created disk space on the drives that were running out of space.
> What should I do to kill those processes.
> --
> KT
Showing posts with label transfer. Show all posts
Showing posts with label transfer. Show all posts
Tuesday, March 20, 2012
Monday, March 12, 2012
Scheduled Job
Hi ,
I created a batch only to transfer the files from local server to share
folder on another server. I put the batch in the DTS package and scheduled it.
When I trace the job , the file have been copied but the "Status" of the
job still stick on "Executing Step 1 ..." and it no turn to success although
the file had been copied. What's wrong with that actually ?
Thanks ,
Travis
--
Travis TanHi ,
why u are making ur work complex .
U can transfer the files using file tranfer protocol task in DTC
package.
When the batch finishes tanfer sqlserver doesnt come to know the status
and it shows executing status.
from
Doller
Travis wrote:
> Hi ,
> I created a batch only to transfer the files from local server to share
> folder on another server. I put the batch in the DTS package and scheduled it.
> When I trace the job , the file have been copied but the "Status" of the
> job still stick on "Executing Step 1 ..." and it no turn to success although
> the file had been copied. What's wrong with that actually ?
> Thanks ,
> Travis
> --
> Travis Tan|||Travis wrote:
> Hi ,
> I created a batch only to transfer the files from local server to share
> folder on another server. I put the batch in the DTS package and scheduled it.
> When I trace the job , the file have been copied but the "Status" of the
> job still stick on "Executing Step 1 ..." and it no turn to success although
> the file had been copied. What's wrong with that actually ?
> Thanks ,
> Travis
>
Are you looking at the status in Enterprise Manager? In that case you
might need to refresh it to see the actual status.
Regards
Steen|||Hi Doller ,
Thanks for your info and I understand what you said. The actually process
in DTS was
1) Transfer The Files
2) UnZip The Files
3) Restore the transaction logs
Because the Transfer Files pending in "executing" so no Unzip process is
done. Means that no way for me to resolve that ?
Thanks ,
Travis
Travis Tan
"doller" wrote:
> Hi ,
> why u are making ur work complex .
> U can transfer the files using file tranfer protocol task in DTC
> package.
> When the batch finishes tanfer sqlserver doesnt come to know the status
> and it shows executing status.
> from
> Doller
>
> Travis wrote:
> > Hi ,
> >
> > I created a batch only to transfer the files from local server to share
> > folder on another server. I put the batch in the DTS package and scheduled it.
> >
> > When I trace the job , the file have been copied but the "Status" of the
> > job still stick on "Executing Step 1 ..." and it no turn to success although
> > the file had been copied. What's wrong with that actually ?
> >
> > Thanks ,
> > Travis
> >
> > --
> > Travis Tan
>
I created a batch only to transfer the files from local server to share
folder on another server. I put the batch in the DTS package and scheduled it.
When I trace the job , the file have been copied but the "Status" of the
job still stick on "Executing Step 1 ..." and it no turn to success although
the file had been copied. What's wrong with that actually ?
Thanks ,
Travis
--
Travis TanHi ,
why u are making ur work complex .
U can transfer the files using file tranfer protocol task in DTC
package.
When the batch finishes tanfer sqlserver doesnt come to know the status
and it shows executing status.
from
Doller
Travis wrote:
> Hi ,
> I created a batch only to transfer the files from local server to share
> folder on another server. I put the batch in the DTS package and scheduled it.
> When I trace the job , the file have been copied but the "Status" of the
> job still stick on "Executing Step 1 ..." and it no turn to success although
> the file had been copied. What's wrong with that actually ?
> Thanks ,
> Travis
> --
> Travis Tan|||Travis wrote:
> Hi ,
> I created a batch only to transfer the files from local server to share
> folder on another server. I put the batch in the DTS package and scheduled it.
> When I trace the job , the file have been copied but the "Status" of the
> job still stick on "Executing Step 1 ..." and it no turn to success although
> the file had been copied. What's wrong with that actually ?
> Thanks ,
> Travis
>
Are you looking at the status in Enterprise Manager? In that case you
might need to refresh it to see the actual status.
Regards
Steen|||Hi Doller ,
Thanks for your info and I understand what you said. The actually process
in DTS was
1) Transfer The Files
2) UnZip The Files
3) Restore the transaction logs
Because the Transfer Files pending in "executing" so no Unzip process is
done. Means that no way for me to resolve that ?
Thanks ,
Travis
Travis Tan
"doller" wrote:
> Hi ,
> why u are making ur work complex .
> U can transfer the files using file tranfer protocol task in DTC
> package.
> When the batch finishes tanfer sqlserver doesnt come to know the status
> and it shows executing status.
> from
> Doller
>
> Travis wrote:
> > Hi ,
> >
> > I created a batch only to transfer the files from local server to share
> > folder on another server. I put the batch in the DTS package and scheduled it.
> >
> > When I trace the job , the file have been copied but the "Status" of the
> > job still stick on "Executing Step 1 ..." and it no turn to success although
> > the file had been copied. What's wrong with that actually ?
> >
> > Thanks ,
> > Travis
> >
> > --
> > Travis Tan
>
Scheduled Job
Hi ,
I created a batch only to transfer the files from local server to share
folder on another server. I put the batch in the DTS package and scheduled i
t.
When I trace the job , the file have been copied but the "Status" of the
job still stick on "Executing Step 1 ..." and it no turn to success althoug
h
the file had been copied. What's wrong with that actually ?
Thanks ,
Travis
Travis TanHi ,
why u are making ur work complex .
U can transfer the files using file tranfer protocol task in DTC
package.
When the batch finishes tanfer sqlserver doesnt come to know the status
and it shows executing status.
from
Doller
Travis wrote:
> Hi ,
> I created a batch only to transfer the files from local server to share
> folder on another server. I put the batch in the DTS package and scheduled
it.
> When I trace the job , the file have been copied but the "Status" of the
> job still stick on "Executing Step 1 ..." and it no turn to success altho
ugh
> the file had been copied. What's wrong with that actually ?
> Thanks ,
> Travis
> --
> Travis Tan|||Travis wrote:
> Hi ,
> I created a batch only to transfer the files from local server to share
> folder on another server. I put the batch in the DTS package and scheduled
it.
> When I trace the job , the file have been copied but the "Status" of the
> job still stick on "Executing Step 1 ..." and it no turn to success altho
ugh
> the file had been copied. What's wrong with that actually ?
> Thanks ,
> Travis
>
Are you looking at the status in Enterprise Manager? In that case you
might need to refresh it to see the actual status.
Regards
Steen|||Hi Doller ,
Thanks for your info and I understand what you said. The actually process
in DTS was
1) Transfer The Files
2) UnZip The Files
3) Restore the transaction logs
Because the Transfer Files pending in "executing" so no Unzip process is
done. Means that no way for me to resolve that ?
Thanks ,
Travis
Travis Tan
"doller" wrote:
> Hi ,
> why u are making ur work complex .
> U can transfer the files using file tranfer protocol task in DTC
> package.
> When the batch finishes tanfer sqlserver doesnt come to know the status
> and it shows executing status.
> from
> Doller
>
> Travis wrote:
>
I created a batch only to transfer the files from local server to share
folder on another server. I put the batch in the DTS package and scheduled i
t.
When I trace the job , the file have been copied but the "Status" of the
job still stick on "Executing Step 1 ..." and it no turn to success althoug
h
the file had been copied. What's wrong with that actually ?
Thanks ,
Travis
Travis TanHi ,
why u are making ur work complex .
U can transfer the files using file tranfer protocol task in DTC
package.
When the batch finishes tanfer sqlserver doesnt come to know the status
and it shows executing status.
from
Doller
Travis wrote:
> Hi ,
> I created a batch only to transfer the files from local server to share
> folder on another server. I put the batch in the DTS package and scheduled
it.
> When I trace the job , the file have been copied but the "Status" of the
> job still stick on "Executing Step 1 ..." and it no turn to success altho
ugh
> the file had been copied. What's wrong with that actually ?
> Thanks ,
> Travis
> --
> Travis Tan|||Travis wrote:
> Hi ,
> I created a batch only to transfer the files from local server to share
> folder on another server. I put the batch in the DTS package and scheduled
it.
> When I trace the job , the file have been copied but the "Status" of the
> job still stick on "Executing Step 1 ..." and it no turn to success altho
ugh
> the file had been copied. What's wrong with that actually ?
> Thanks ,
> Travis
>
Are you looking at the status in Enterprise Manager? In that case you
might need to refresh it to see the actual status.
Regards
Steen|||Hi Doller ,
Thanks for your info and I understand what you said. The actually process
in DTS was
1) Transfer The Files
2) UnZip The Files
3) Restore the transaction logs
Because the Transfer Files pending in "executing" so no Unzip process is
done. Means that no way for me to resolve that ?
Thanks ,
Travis
Travis Tan
"doller" wrote:
> Hi ,
> why u are making ur work complex .
> U can transfer the files using file tranfer protocol task in DTC
> package.
> When the batch finishes tanfer sqlserver doesnt come to know the status
> and it shows executing status.
> from
> Doller
>
> Travis wrote:
>
scheduled import/export
I used import/export in SQL 2000 to transfer one table from A server to B
server and save the package and schedule it. This works fine in SQL 2000.
However, when I try to do the same thing in SQL 2005 and after I save the
package, there is no way to schedule it. And I couldn't locate the package I
created in import/export. Does anyone know where I can find the package and
schedule it after the import/export? Is this very different way from
SQL2000? Please help. Thanks.
Hi
"00kobebrian" wrote:
> I used import/export in SQL 2000 to transfer one table from A server to B
> server and save the package and schedule it. This works fine in SQL 2000.
> However, when I try to do the same thing in SQL 2005 and after I save the
> package, there is no way to schedule it. And I couldn't locate the package I
> created in import/export. Does anyone know where I can find the package and
> schedule it after the import/export? Is this very different way from
> SQL2000? Please help. Thanks.
If you saved the task as a SSIS package on the server then you will need to
connect to Integration services to find and run the package.
To schedule a job to run the package copy the command line from the run
package dialog and use this as the parameters for DTEXEC.
>
John
|||Sorry. Do you mean copy the content in "command line" tab in "execute
package utility"? and where is DTEXEC? Thanks.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:94A2C248-9076-4126-9877-1BBFF1AB1FB2@.microsoft.com...
> Hi
> "00kobebrian" wrote:
>
> If you saved the task as a SSIS package on the server then you will need
> to
> connect to Integration services to find and run the package.
> To schedule a job to run the package copy the command line from the run
> package dialog and use this as the parameters for DTEXEC.
> John
server and save the package and schedule it. This works fine in SQL 2000.
However, when I try to do the same thing in SQL 2005 and after I save the
package, there is no way to schedule it. And I couldn't locate the package I
created in import/export. Does anyone know where I can find the package and
schedule it after the import/export? Is this very different way from
SQL2000? Please help. Thanks.
Hi
"00kobebrian" wrote:
> I used import/export in SQL 2000 to transfer one table from A server to B
> server and save the package and schedule it. This works fine in SQL 2000.
> However, when I try to do the same thing in SQL 2005 and after I save the
> package, there is no way to schedule it. And I couldn't locate the package I
> created in import/export. Does anyone know where I can find the package and
> schedule it after the import/export? Is this very different way from
> SQL2000? Please help. Thanks.
If you saved the task as a SSIS package on the server then you will need to
connect to Integration services to find and run the package.
To schedule a job to run the package copy the command line from the run
package dialog and use this as the parameters for DTEXEC.
>
John
|||Sorry. Do you mean copy the content in "command line" tab in "execute
package utility"? and where is DTEXEC? Thanks.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:94A2C248-9076-4126-9877-1BBFF1AB1FB2@.microsoft.com...
> Hi
> "00kobebrian" wrote:
>
> If you saved the task as a SSIS package on the server then you will need
> to
> connect to Integration services to find and run the package.
> To schedule a job to run the package copy the command line from the run
> package dialog and use this as the parameters for DTEXEC.
> John
scheduled import/export
I used import/export in SQL 2000 to transfer one table from A server to B
server and save the package and schedule it. This works fine in SQL 2000.
However, when I try to do the same thing in SQL 2005 and after I save the
package, there is no way to schedule it. And I couldn't locate the package I
created in import/export. Does anyone know where I can find the package and
schedule it after the import/export? Is this very different way from
SQL2000? Please help. Thanks.Hi
"00kobebrian" wrote:
> I used import/export in SQL 2000 to transfer one table from A server to B
> server and save the package and schedule it. This works fine in SQL 2000.
> However, when I try to do the same thing in SQL 2005 and after I save the
> package, there is no way to schedule it. And I couldn't locate the package
I
> created in import/export. Does anyone know where I can find the package an
d
> schedule it after the import/export? Is this very different way from
> SQL2000? Please help. Thanks.
If you saved the task as a SSIS package on the server then you will need to
connect to Integration services to find and run the package.
To schedule a job to run the package copy the command line from the run
package dialog and use this as the parameters for DTEXEC.
>
John|||How can I connect to integration services? Thanks.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:94A2C248-9076-4126-9877-1BBFF1AB1FB2@.microsoft.com...
> Hi
> "00kobebrian" wrote:
>
> If you saved the task as a SSIS package on the server then you will need
> to
> connect to Integration services to find and run the package.
> To schedule a job to run the package copy the command line from the run
> package dialog and use this as the parameters for DTEXEC.
> John|||Hi
On Feb 5, 2:31 am, "00EricClapton" <E...@.yahoo.com> wrote:
> How can I connect to integration services? Thanks.
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:94A2C248-9076-4126-9877-1BBFF1AB1FB2@.microsoft.com...
>
If you open up object explorere (F8) then there is a large connect
button at the top of the pane. Alternatively you can use the file/
connect object explorer menu options. Choose integration services for
the service type and enter the authentication details.
HTH
John|||Sorry. Do you mean copy the content in "command line" tab in "execute
package utility"? and where is DTEXEC? Thanks.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:94A2C248-9076-4126-9877-1BBFF1AB1FB2@.microsoft.com...
> Hi
> "00kobebrian" wrote:
>
> If you saved the task as a SSIS package on the server then you will need
> to
> connect to Integration services to find and run the package.
> To schedule a job to run the package copy the command line from the run
> package dialog and use this as the parameters for DTEXEC.
> John
server and save the package and schedule it. This works fine in SQL 2000.
However, when I try to do the same thing in SQL 2005 and after I save the
package, there is no way to schedule it. And I couldn't locate the package I
created in import/export. Does anyone know where I can find the package and
schedule it after the import/export? Is this very different way from
SQL2000? Please help. Thanks.Hi
"00kobebrian" wrote:
> I used import/export in SQL 2000 to transfer one table from A server to B
> server and save the package and schedule it. This works fine in SQL 2000.
> However, when I try to do the same thing in SQL 2005 and after I save the
> package, there is no way to schedule it. And I couldn't locate the package
I
> created in import/export. Does anyone know where I can find the package an
d
> schedule it after the import/export? Is this very different way from
> SQL2000? Please help. Thanks.
If you saved the task as a SSIS package on the server then you will need to
connect to Integration services to find and run the package.
To schedule a job to run the package copy the command line from the run
package dialog and use this as the parameters for DTEXEC.
>
John|||How can I connect to integration services? Thanks.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:94A2C248-9076-4126-9877-1BBFF1AB1FB2@.microsoft.com...
> Hi
> "00kobebrian" wrote:
>
> If you saved the task as a SSIS package on the server then you will need
> to
> connect to Integration services to find and run the package.
> To schedule a job to run the package copy the command line from the run
> package dialog and use this as the parameters for DTEXEC.
> John|||Hi
On Feb 5, 2:31 am, "00EricClapton" <E...@.yahoo.com> wrote:
> How can I connect to integration services? Thanks.
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:94A2C248-9076-4126-9877-1BBFF1AB1FB2@.microsoft.com...
>
If you open up object explorere (F8) then there is a large connect
button at the top of the pane. Alternatively you can use the file/
connect object explorer menu options. Choose integration services for
the service type and enter the authentication details.
HTH
John|||Sorry. Do you mean copy the content in "command line" tab in "execute
package utility"? and where is DTEXEC? Thanks.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:94A2C248-9076-4126-9877-1BBFF1AB1FB2@.microsoft.com...
> Hi
> "00kobebrian" wrote:
>
> If you saved the task as a SSIS package on the server then you will need
> to
> connect to Integration services to find and run the package.
> To schedule a job to run the package copy the command line from the run
> package dialog and use this as the parameters for DTEXEC.
> John
scheduled import/export
I used import/export in SQL 2000 to transfer one table from A server to B
server and save the package and schedule it. This works fine in SQL 2000.
However, when I try to do the same thing in SQL 2005 and after I save the
package, there is no way to schedule it. And I couldn't locate the package I
created in import/export. Does anyone know where I can find the package and
schedule it after the import/export? Is this very different way from
SQL2000? Please help. Thanks.Hi
"00kobebrian" wrote:
> I used import/export in SQL 2000 to transfer one table from A server to B
> server and save the package and schedule it. This works fine in SQL 2000.
> However, when I try to do the same thing in SQL 2005 and after I save the
> package, there is no way to schedule it. And I couldn't locate the package I
> created in import/export. Does anyone know where I can find the package and
> schedule it after the import/export? Is this very different way from
> SQL2000? Please help. Thanks.
If you saved the task as a SSIS package on the server then you will need to
connect to Integration services to find and run the package.
To schedule a job to run the package copy the command line from the run
package dialog and use this as the parameters for DTEXEC.
>
John|||How can I connect to integration services? Thanks.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:94A2C248-9076-4126-9877-1BBFF1AB1FB2@.microsoft.com...
> Hi
> "00kobebrian" wrote:
>> I used import/export in SQL 2000 to transfer one table from A server to B
>> server and save the package and schedule it. This works fine in SQL 2000.
>> However, when I try to do the same thing in SQL 2005 and after I save the
>> package, there is no way to schedule it. And I couldn't locate the
>> package I
>> created in import/export. Does anyone know where I can find the package
>> and
>> schedule it after the import/export? Is this very different way from
>> SQL2000? Please help. Thanks.
> If you saved the task as a SSIS package on the server then you will need
> to
> connect to Integration services to find and run the package.
> To schedule a job to run the package copy the command line from the run
> package dialog and use this as the parameters for DTEXEC.
> John|||Hi
On Feb 5, 2:31 am, "00EricClapton" <E...@.yahoo.com> wrote:
> How can I connect to integration services? Thanks.
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:94A2C248-9076-4126-9877-1BBFF1AB1FB2@.microsoft.com...
>
If you open up object explorere (F8) then there is a large connect
button at the top of the pane. Alternatively you can use the file/
connect object explorer menu options. Choose integration services for
the service type and enter the authentication details.
HTH
John|||Sorry. Do you mean copy the content in "command line" tab in "execute
package utility"? and where is DTEXEC? Thanks.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:94A2C248-9076-4126-9877-1BBFF1AB1FB2@.microsoft.com...
> Hi
> "00kobebrian" wrote:
>> I used import/export in SQL 2000 to transfer one table from A server to B
>> server and save the package and schedule it. This works fine in SQL 2000.
>> However, when I try to do the same thing in SQL 2005 and after I save the
>> package, there is no way to schedule it. And I couldn't locate the
>> package I
>> created in import/export. Does anyone know where I can find the package
>> and
>> schedule it after the import/export? Is this very different way from
>> SQL2000? Please help. Thanks.
> If you saved the task as a SSIS package on the server then you will need
> to
> connect to Integration services to find and run the package.
> To schedule a job to run the package copy the command line from the run
> package dialog and use this as the parameters for DTEXEC.
> John
server and save the package and schedule it. This works fine in SQL 2000.
However, when I try to do the same thing in SQL 2005 and after I save the
package, there is no way to schedule it. And I couldn't locate the package I
created in import/export. Does anyone know where I can find the package and
schedule it after the import/export? Is this very different way from
SQL2000? Please help. Thanks.Hi
"00kobebrian" wrote:
> I used import/export in SQL 2000 to transfer one table from A server to B
> server and save the package and schedule it. This works fine in SQL 2000.
> However, when I try to do the same thing in SQL 2005 and after I save the
> package, there is no way to schedule it. And I couldn't locate the package I
> created in import/export. Does anyone know where I can find the package and
> schedule it after the import/export? Is this very different way from
> SQL2000? Please help. Thanks.
If you saved the task as a SSIS package on the server then you will need to
connect to Integration services to find and run the package.
To schedule a job to run the package copy the command line from the run
package dialog and use this as the parameters for DTEXEC.
>
John|||How can I connect to integration services? Thanks.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:94A2C248-9076-4126-9877-1BBFF1AB1FB2@.microsoft.com...
> Hi
> "00kobebrian" wrote:
>> I used import/export in SQL 2000 to transfer one table from A server to B
>> server and save the package and schedule it. This works fine in SQL 2000.
>> However, when I try to do the same thing in SQL 2005 and after I save the
>> package, there is no way to schedule it. And I couldn't locate the
>> package I
>> created in import/export. Does anyone know where I can find the package
>> and
>> schedule it after the import/export? Is this very different way from
>> SQL2000? Please help. Thanks.
> If you saved the task as a SSIS package on the server then you will need
> to
> connect to Integration services to find and run the package.
> To schedule a job to run the package copy the command line from the run
> package dialog and use this as the parameters for DTEXEC.
> John|||Hi
On Feb 5, 2:31 am, "00EricClapton" <E...@.yahoo.com> wrote:
> How can I connect to integration services? Thanks.
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:94A2C248-9076-4126-9877-1BBFF1AB1FB2@.microsoft.com...
>
If you open up object explorere (F8) then there is a large connect
button at the top of the pane. Alternatively you can use the file/
connect object explorer menu options. Choose integration services for
the service type and enter the authentication details.
HTH
John|||Sorry. Do you mean copy the content in "command line" tab in "execute
package utility"? and where is DTEXEC? Thanks.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:94A2C248-9076-4126-9877-1BBFF1AB1FB2@.microsoft.com...
> Hi
> "00kobebrian" wrote:
>> I used import/export in SQL 2000 to transfer one table from A server to B
>> server and save the package and schedule it. This works fine in SQL 2000.
>> However, when I try to do the same thing in SQL 2005 and after I save the
>> package, there is no way to schedule it. And I couldn't locate the
>> package I
>> created in import/export. Does anyone know where I can find the package
>> and
>> schedule it after the import/export? Is this very different way from
>> SQL2000? Please help. Thanks.
> If you saved the task as a SSIS package on the server then you will need
> to
> connect to Integration services to find and run the package.
> To schedule a job to run the package copy the command line from the run
> package dialog and use this as the parameters for DTEXEC.
> John
Wednesday, March 7, 2012
Schedule question
Hello all!
I have a small .vbs script that I would like to run as a step in the SQL scheduler. The script is "MsgBox("Database Transfer Succesfull!")"
The client wants to something to let the end user know it was succesful with a pop up message. But it doesn't work, and just hangs up my process. The other steps are SP's and a DTS run.
Any idea's?
TIA!!
Rudy
The SQL Agent is architectured to run on servers, even without any user being logged on when the scheduled task is executed. So it runs the program in separate session, and this message box is "displayed" on the invisible desktop, so nobody can close it, and the process hangs.
Use some other way to get user notified, e.g. send him/her an e-mail, or (if you keep [deprecated] messenger service enabled) run 'net send computer message' command, etc.
Subscribe to:
Posts (Atom)