Scheduling a SSIS Package using SQL Agent (passing credentials)

Hi:

I created a fairly simple SSIS package to move data from a remote server which uses SQL Server Authentication to a local server that uses Windows Authentication. Everything works fine when executing the package within BI studio and if I execute the package by connecting to SSIS. If I schedule it as a SQL Server Agent Job, however, the non-integrated security fails unless I manually edit the connection to include the password. Obviously this is insecure because it is in plain text. What can I do?

Thanks.

You might need to change the encryption protection of your package (i.e. encrypt sensitive w/ user key, encrypt sensitive w/ password, etc) as well as setting up your proxy / credentials correctly.

Check out these MS article...

http://support.microsoft.com/kb/912911

http://support.microsoft.com/?kbid=918760

There are also many threads discussing these topics, including:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1322146&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1955723&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=703968&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2068280&SiteID=1

|||

Thanks for your response.

First of all, I did try the encrypt sensitive w / password (the default is w / user key) and I put a password in, saved the package to SQL Server and re-setup the job. It prompted me for passwords as I was setting the job up, but it didn't help at all with the remote connection. Do I need to put my connection information into the command line (user and password) AND encrypt with the password to keep others from seeing the username and password. So far I've just done one or the other.

I also tried the proxy credentials thing, but I am not so sure I understood exactly how it works. Specifically, it was prompting for an AD account, which doesn't help me in the non-integrated (SQL) login environment.

|||

RM,

You have multiple choices, but before choosing one you have to understand the pros and cons of each one. Using Package protection level equal to DonSaveSensitive plus using package configurations is a popular method that works well. You have more details in the method 4 described in one of the KB articles that EWisdahl pointed out( http://support.microsoft.com/?kbid=918760)

Search by package configurations and you will find plenty of options and examples

|||

Interestingly enough,

When I went back into the SQL Agent Job and clicked on command line (where I had added the credentials before) it defaulted back to the original command line. If this is the case, no problem, because the password I typed is hidden, right? Of course, now when I click on the data sources tab I get an error that states my connection string is invalid and it shows no data sources, either? Is the behavior somehow interrelated? The job seems to be running fine, though!?!

Schedule problem with remote SQL instance.

Im running RS on Windows 2003 server, connecting to a remote instance of SQL.
When I try to set up a schedule for any report, i get...
"The SQL Agent service is not running. This operation requires the SQL Agent
service. (rsSchedulerNotResponding)"
I know its not finding any local sql agent on the server RS is running on,
what im wondering is if there is a way to hack it to use the SQL agent on a
remote SQL server to schedule these reports.
Thanks!i have the same problem..Did u find any solution?
"Jason Brinkley" wrote:
> Im running RS on Windows 2003 server, connecting to a remote instance of SQL.
> When I try to set up a schedule for any report, i get...
> "The SQL Agent service is not running. This operation requires the SQL Agent
> service. (rsSchedulerNotResponding)"
> I know its not finding any local sql agent on the server RS is running on,
> what im wondering is if there is a way to hack it to use the SQL agent on a
> remote SQL server to schedule these reports.
> Thanks!|||I am pretty sure the SQL Agent message IS talking about the server with the
database.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chitra" <Chitra@.discussions.microsoft.com> wrote in message
news:CAB5BEB8-36DD-490E-8AC5-15E57C19AC7B@.microsoft.com...
>i have the same problem..Did u find any solution?
> "Jason Brinkley" wrote:
>> Im running RS on Windows 2003 server, connecting to a remote instance of
>> SQL.
>> When I try to set up a schedule for any report, i get...
>> "The SQL Agent service is not running. This operation requires the SQL
>> Agent
>> service. (rsSchedulerNotResponding)"
>> I know its not finding any local sql agent on the server RS is running
>> on,
>> what im wondering is if there is a way to hack it to use the SQL agent on
>> a
>> remote SQL server to schedule these reports.
>> Thanks!

schedule job to set database to single user mode

Task Summary:
I have a remote user to sending records every 5 minutes by DTS package.
I think the best way to handle this is to create a job that will up the
database
into single user mode, set the remote user to the single user.
allow the job to run 10 to 15 minutes then take it out of single user mode.
Task Break down:
1:
Put the database into single user mode.
assign myself as the user.
(How do I define which user has access?)
2:
Backup the database
unassign myself as the single user
assign remote user as the single user
3:
Scheduled the job to execute for 15 minutes
4:
take database out of single user mode
5:
Schedule job to execute evey 6 hours.
Hi
"mj" wrote:

> Task Summary:
> I have a remote user to sending records every 5 minutes by DTS package.
> I think the best way to handle this is to create a job that will up the
> database
> into single user mode, set the remote user to the single user.
> allow the job to run 10 to 15 minutes then take it out of single user mode.
>
> Task Break down:
> 1:
> Put the database into single user mode.
> assign myself as the user.
> (How do I define which user has access?)
> 2:
> Backup the database
> unassign myself as the single user
> assign remote user as the single user
> 3:
> Scheduled the job to execute for 15 minutes
> 4:
> take database out of single user mode
> 5:
> Schedule job to execute evey 6 hours.
>
You can not assign another user to be the single user in single user mode!
If you are not connected to the database when it is set in single user mode
then potentially anyone could get in and be that single user.
I am not sure why the remote user is send things every 5 minutes and you
will only want him to send something for a 15 minute period every 6 hours.
What may be a better scenario is that every 6 hours you fetch the information
from the remote location and then processes it in one batch, then the process
is controlled by the server. A different approach you be to have a second
database that the user updates (local or remote) and then use replication to
merge the differences. With SQL 2005 service broker may possibly be useful.
John
|||What is the justification for this attempt to "lock the database into
single-user mode for a specific user"?
TheSQLGuru
President
Indicium Resources, Inc.
"mj" <mj@.discussions.microsoft.com> wrote in message
news:137E0713-D3ED-4915-95CD-E4CD4D766A57@.microsoft.com...
> Task Summary:
> I have a remote user to sending records every 5 minutes by DTS package.
> I think the best way to handle this is to create a job that will up the
> database
> into single user mode, set the remote user to the single user.
> allow the job to run 10 to 15 minutes then take it out of single user
> mode.
>
> Task Break down:
> 1:
> Put the database into single user mode.
> assign myself as the user.
> (How do I define which user has access?)
> 2:
> Backup the database
> unassign myself as the single user
> assign remote user as the single user
> 3:
> Scheduled the job to execute for 15 minutes
> 4:
> take database out of single user mode
> 5:
> Schedule job to execute evey 6 hours.
>
>
|||Thanks John and SQLGuRu for the interest;
More Background Details:
The remote user has developed an extensive DTS package.
When the transformations have been completed, then the transformed
data is sent to a central server.
For this reason I can not just go get the data.
To ensure the migration is completed without interuption, I need to put the
server into single user mode.
To preserve the data prior to the migration, I need to perform a backup.
My current solution looks like this:
Procedure MySolution AS
Alter database Set Single_User
Perform back up of database
perform backup of logs
alter database Set Multi_User
End Procedure
Create Job
Call Procedure Mysolution
Schedule Job 6hrs
"TheSQLGuru" wrote:

> What is the justification for this attempt to "lock the database into
> single-user mode for a specific user"?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "mj" <mj@.discussions.microsoft.com> wrote in message
> news:137E0713-D3ED-4915-95CD-E4CD4D766A57@.microsoft.com...
>
>
|||Hi
"mj" wrote:
[vbcol=seagreen]
> Thanks John and SQLGuRu for the interest;
>
> More Background Details:
> The remote user has developed an extensive DTS package.
> When the transformations have been completed, then the transformed
> data is sent to a central server.
> For this reason I can not just go get the data.
> To ensure the migration is completed without interuption, I need to put the
> server into single user mode.
> To preserve the data prior to the migration, I need to perform a backup.
> My current solution looks like this:
> ----
> Procedure MySolution AS
> Alter database Set Single_User
> Perform back up of database
> perform backup of logs
> alter database Set Multi_User
> End Procedure
> Create Job
> Call Procedure Mysolution
> Schedule Job 6hrs
> ----
>
> "TheSQLGuru" wrote:
I can only assume that this is not a system with users, as a period of
unavailability every 6 hours is not the sort of service level that would be
classed as acceptable!!
Who do you need to load this every 6 hours?
Have you considered replication?
If you have a proper sequence of log backups you may not need to do the full
backup if you accept that you will need to restore the last full backup and
roll forward to return to the state prior to your process running.
Alternatively a differential backup would remove the need to restore some of
the log backups.
If you set the database into single user mode, then you can not guarantee
getting access to the database (for that single user) in subsequent job steps.
What do you do with the files that the process has transferred?
John

schedule job to set database to single user mode

Task Summary:
I have a remote user to sending records every 5 minutes by DTS package.
I think the best way to handle this is to create a job that will up the
database
into single user mode, set the remote user to the single user.
allow the job to run 10 to 15 minutes then take it out of single user mode.
Task Break down:
1:
Put the database into single user mode.
assign myself as the user.
(How do I define which user has access?)
2:
Backup the database
unassign myself as the single user
assign remote user as the single user
3:
Scheduled the job to execute for 15 minutes
4:
take database out of single user mode
5:
Schedule job to execute evey 6 hours.Hi
"mj" wrote:

> Task Summary:
> I have a remote user to sending records every 5 minutes by DTS package.
> I think the best way to handle this is to create a job that will up the
> database
> into single user mode, set the remote user to the single user.
> allow the job to run 10 to 15 minutes then take it out of single user mode
.
>
> Task Break down:
> 1:
> Put the database into single user mode.
> assign myself as the user.
> (How do I define which user has access?)
> 2:
> Backup the database
> unassign myself as the single user
> assign remote user as the single user
> 3:
> Scheduled the job to execute for 15 minutes
> 4:
> take database out of single user mode
> 5:
> Schedule job to execute evey 6 hours.
>
You can not assign another user to be the single user in single user mode!
If you are not connected to the database when it is set in single user mode
then potentially anyone could get in and be that single user.
I am not sure why the remote user is send things every 5 minutes and you
will only want him to send something for a 15 minute period every 6 hours.
What may be a better scenario is that every 6 hours you fetch the informatio
n
from the remote location and then processes it in one batch, then the proces
s
is controlled by the server. A different approach you be to have a second
database that the user updates (local or remote) and then use replication to
merge the differences. With SQL 2005 service broker may possibly be useful.
John|||What is the justification for this attempt to "lock the database into
single-user mode for a specific user"'
TheSQLGuru
President
Indicium Resources, Inc.
"mj" <mj@.discussions.microsoft.com> wrote in message
news:137E0713-D3ED-4915-95CD-E4CD4D766A57@.microsoft.com...
> Task Summary:
> I have a remote user to sending records every 5 minutes by DTS package.
> I think the best way to handle this is to create a job that will up the
> database
> into single user mode, set the remote user to the single user.
> allow the job to run 10 to 15 minutes then take it out of single user
> mode.
>
> Task Break down:
> 1:
> Put the database into single user mode.
> assign myself as the user.
> (How do I define which user has access?)
> 2:
> Backup the database
> unassign myself as the single user
> assign remote user as the single user
> 3:
> Scheduled the job to execute for 15 minutes
> 4:
> take database out of single user mode
> 5:
> Schedule job to execute evey 6 hours.
>
>|||Thanks John and SQLGuRu for the interest;
More Background Details:
The remote user has developed an extensive DTS package.
When the transformations have been completed, then the transformed
data is sent to a central server.
For this reason I can not just go get the data.
To ensure the migration is completed without interuption, I need to put the
server into single user mode.
To preserve the data prior to the migration, I need to perform a backup.
My current solution looks like this:
----
--
Procedure MySolution AS
Alter database Set Single_User
Perform back up of database
perform backup of logs
alter database Set Multi_User
End Procedure
Create Job
Call Procedure Mysolution
Schedule Job 6hrs
----
--
"TheSQLGuru" wrote:

> What is the justification for this attempt to "lock the database into
> single-user mode for a specific user"'
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "mj" <mj@.discussions.microsoft.com> wrote in message
> news:137E0713-D3ED-4915-95CD-E4CD4D766A57@.microsoft.com...
>
>|||Hi
"mj" wrote:
[vbcol=seagreen]
> Thanks John and SQLGuRu for the interest;
>
> More Background Details:
> The remote user has developed an extensive DTS package.
> When the transformations have been completed, then the transformed
> data is sent to a central server.
> For this reason I can not just go get the data.
> To ensure the migration is completed without interuption, I need to put th
e
> server into single user mode.
> To preserve the data prior to the migration, I need to perform a backup.
> My current solution looks like this:
> ----
--
> Procedure MySolution AS
> Alter database Set Single_User
> Perform back up of database
> perform backup of logs
> alter database Set Multi_User
> End Procedure
> Create Job
> Call Procedure Mysolution
> Schedule Job 6hrs
> ----
--
>
> "TheSQLGuru" wrote:
>
I can only assume that this is not a system with users, as a period of
unavailability every 6 hours is not the sort of service level that would be
classed as acceptable!!
Who do you need to load this every 6 hours?
Have you considered replication?
If you have a proper sequence of log backups you may not need to do the full
backup if you accept that you will need to restore the last full backup and
roll forward to return to the state prior to your process running.
Alternatively a differential backup would remove the need to restore some of
the log backups.
If you set the database into single user mode, then you can not guarantee
getting access to the database (for that single user) in subsequent job step
s.
What do you do with the files that the process has transferred?
John

schedule job to set database to single user mode

Task Summary:
I have a remote user to sending records every 5 minutes by DTS package.
I think the best way to handle this is to create a job that will up the
database
into single user mode, set the remote user to the single user.
allow the job to run 10 to 15 minutes then take it out of single user mode.
Task Break down:
1:
Put the database into single user mode.
assign myself as the user.
(How do I define which user has access?)
2:
Backup the database
unassign myself as the single user
assign remote user as the single user
3:
Scheduled the job to execute for 15 minutes
4:
take database out of single user mode
5:
Schedule job to execute evey 6 hours.Hi
"mj" wrote:
> Task Summary:
> I have a remote user to sending records every 5 minutes by DTS package.
> I think the best way to handle this is to create a job that will up the
> database
> into single user mode, set the remote user to the single user.
> allow the job to run 10 to 15 minutes then take it out of single user mode.
>
> Task Break down:
> 1:
> Put the database into single user mode.
> assign myself as the user.
> (How do I define which user has access?)
> 2:
> Backup the database
> unassign myself as the single user
> assign remote user as the single user
> 3:
> Scheduled the job to execute for 15 minutes
> 4:
> take database out of single user mode
> 5:
> Schedule job to execute evey 6 hours.
>
You can not assign another user to be the single user in single user mode!
If you are not connected to the database when it is set in single user mode
then potentially anyone could get in and be that single user.
I am not sure why the remote user is send things every 5 minutes and you
will only want him to send something for a 15 minute period every 6 hours.
What may be a better scenario is that every 6 hours you fetch the information
from the remote location and then processes it in one batch, then the process
is controlled by the server. A different approach you be to have a second
database that the user updates (local or remote) and then use replication to
merge the differences. With SQL 2005 service broker may possibly be useful.
John|||What is the justification for this attempt to "lock the database into
single-user mode for a specific user"'
--
TheSQLGuru
President
Indicium Resources, Inc.
"mj" <mj@.discussions.microsoft.com> wrote in message
news:137E0713-D3ED-4915-95CD-E4CD4D766A57@.microsoft.com...
> Task Summary:
> I have a remote user to sending records every 5 minutes by DTS package.
> I think the best way to handle this is to create a job that will up the
> database
> into single user mode, set the remote user to the single user.
> allow the job to run 10 to 15 minutes then take it out of single user
> mode.
>
> Task Break down:
> 1:
> Put the database into single user mode.
> assign myself as the user.
> (How do I define which user has access?)
> 2:
> Backup the database
> unassign myself as the single user
> assign remote user as the single user
> 3:
> Scheduled the job to execute for 15 minutes
> 4:
> take database out of single user mode
> 5:
> Schedule job to execute evey 6 hours.
>
>|||Thanks John and SQLGuRu for the interest;
More Background Details:
The remote user has developed an extensive DTS package.
When the transformations have been completed, then the transformed
data is sent to a central server.
For this reason I can not just go get the data.
To ensure the migration is completed without interuption, I need to put the
server into single user mode.
To preserve the data prior to the migration, I need to perform a backup.
My current solution looks like this:
----
Procedure MySolution AS
Alter database Set Single_User
Perform back up of database
perform backup of logs
alter database Set Multi_User
End Procedure
Create Job
Call Procedure Mysolution
Schedule Job 6hrs
----
"TheSQLGuru" wrote:
> What is the justification for this attempt to "lock the database into
> single-user mode for a specific user"'
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "mj" <mj@.discussions.microsoft.com> wrote in message
> news:137E0713-D3ED-4915-95CD-E4CD4D766A57@.microsoft.com...
> >
> > Task Summary:
> > I have a remote user to sending records every 5 minutes by DTS package.
> > I think the best way to handle this is to create a job that will up the
> > database
> > into single user mode, set the remote user to the single user.
> > allow the job to run 10 to 15 minutes then take it out of single user
> > mode.
> >
> >
> > Task Break down:
> >
> > 1:
> > Put the database into single user mode.
> > assign myself as the user.
> > (How do I define which user has access?)
> >
> > 2:
> > Backup the database
> >
> > unassign myself as the single user
> >
> > assign remote user as the single user
> >
> > 3:
> >
> > Scheduled the job to execute for 15 minutes
> >
> > 4:
> > take database out of single user mode
> >
> > 5:
> > Schedule job to execute evey 6 hours.
> >
> >
> >
> >
>
>|||Hi
"mj" wrote:
> Thanks John and SQLGuRu for the interest;
>
> More Background Details:
> The remote user has developed an extensive DTS package.
> When the transformations have been completed, then the transformed
> data is sent to a central server.
> For this reason I can not just go get the data.
> To ensure the migration is completed without interuption, I need to put the
> server into single user mode.
> To preserve the data prior to the migration, I need to perform a backup.
> My current solution looks like this:
> ----
> Procedure MySolution AS
> Alter database Set Single_User
> Perform back up of database
> perform backup of logs
> alter database Set Multi_User
> End Procedure
> Create Job
> Call Procedure Mysolution
> Schedule Job 6hrs
> ----
>
> "TheSQLGuru" wrote:
> > What is the justification for this attempt to "lock the database into
> > single-user mode for a specific user"'
> >
> > --
> > TheSQLGuru
> > President
> > Indicium Resources, Inc.
> >
> > "mj" <mj@.discussions.microsoft.com> wrote in message
> > news:137E0713-D3ED-4915-95CD-E4CD4D766A57@.microsoft.com...
> > >
> > > Task Summary:
> > > I have a remote user to sending records every 5 minutes by DTS package.
> > > I think the best way to handle this is to create a job that will up the
> > > database
> > > into single user mode, set the remote user to the single user.
> > > allow the job to run 10 to 15 minutes then take it out of single user
> > > mode.
> > >
> > >
> > > Task Break down:
> > >
> > > 1:
> > > Put the database into single user mode.
> > > assign myself as the user.
> > > (How do I define which user has access?)
> > >
> > > 2:
> > > Backup the database
> > >
> > > unassign myself as the single user
> > >
> > > assign remote user as the single user
> > >
> > > 3:
> > >
> > > Scheduled the job to execute for 15 minutes
> > >
> > > 4:
> > > take database out of single user mode
> > >
> > > 5:
> > > Schedule job to execute evey 6 hours.
I can only assume that this is not a system with users, as a period of
unavailability every 6 hours is not the sort of service level that would be
classed as acceptable!!
Who do you need to load this every 6 hours?
Have you considered replication?
If you have a proper sequence of log backups you may not need to do the full
backup if you accept that you will need to restore the last full backup and
roll forward to return to the state prior to your process running.
Alternatively a differential backup would remove the need to restore some of
the log backups.
If you set the database into single user mode, then you can not guarantee
getting access to the database (for that single user) in subsequent job steps.
What do you do with the files that the process has transferred?
John

schedule dts at a remote server

Hi
Can somenone help me build a DTS in SQL Server 2000 that allows to schedule
the execution of a executable file in a remote server without sql server?...
[]
RickyRicky,
try to read up on xp_cmdshell in BOL.
--
Venkat
sql server admirer
"Ricky" wrote:

> Hi
> Can somenone help me build a DTS in SQL Server 2000 that allows to schedul
e
> the execution of a executable file in a remote server without sql server?.
.
> []
> Ricky
>
>
>|||Ricky,
try to read up on xp_cmdshell in BOL.
--
Venkat
sql server admirer
"Ricky" wrote:

> Hi
> Can somenone help me build a DTS in SQL Server 2000 that allows to schedul
e
> the execution of a executable file in a remote server without sql server?.
.
> []
> Ricky
>
>
>|||I didn't understand what "xp_cmdshell in BOL" is. Can you explain better.
Sorry but i'm a newbie on this matter.
Thanks
Ricky
"Venkat" <Venkat@.discussions.microsoft.com> wrote in message
news:39EFAD0A-689B-441E-A444-9CC7FCA660D8@.microsoft.com...[vbcol=seagreen]
> Ricky,
> try to read up on xp_cmdshell in BOL.
> --
> Venkat
> sql server admirer
>
> "Ricky" wrote:
>|||I didn't understand what "xp_cmdshell in BOL" is. Can you explain better.
Sorry but i'm a newbie on this matter.
Thanks
Ricky
"Venkat" <Venkat@.discussions.microsoft.com> wrote in message
news:39EFAD0A-689B-441E-A444-9CC7FCA660D8@.microsoft.com...[vbcol=seagreen]
> Ricky,
> try to read up on xp_cmdshell in BOL.
> --
> Venkat
> sql server admirer
>
> "Ricky" wrote:
>

schedule dts at a remote server

Hi
Can somenone help me build a DTS in SQL Server 2000 that allows to schedule
the execution of a executable file in a remote server without sql server?...
[]
RickyCan you access shared folders on the remote server? If so you could use
xp_cmdshell to run the command - mapping a Network Drive if necessary. You
will need to set appropriate permissions on the shared folder.
Alternatively if you are using the DTS package to unconditionally run the
executable then instead you could just schedule the executable on the remote
server using Windows Scheduled Tasks.
Chris
"Ricky" wrote:

> Hi
> Can somenone help me build a DTS in SQL Server 2000 that allows to schedul
e
> the execution of a executable file in a remote server without sql server?.
.
> []
> Ricky
>
>
>|||Thanks for the tip. But i must go with the first option once i've tried the
second option you advice but the excutable i want to run in the remote
server doesn't do an audit to the software and hardware of the remote
server.
The executable file is audit32.exe from www.itsolutions.intuit.com
Can you design for me the dts and send it to my email?.. Or give me the
right/direct way of doing that in DTS of SQL Server 2000.
Thanks
[]
Ricky
"Chris Howarth" <ChrisHowarth@.discussions.microsoft.com> wrote in message
news:193887B6-D869-45D2-A6DC-362A62009FBA@.microsoft.com...
> Can you access shared folders on the remote server? If so you could use
> xp_cmdshell to run the command - mapping a Network Drive if necessary. You
> will need to set appropriate permissions on the shared folder.
> Alternatively if you are using the DTS package to unconditionally run the
> executable then instead you could just schedule the executable on the
> remote
> server using Windows Scheduled Tasks.
> Chris
>
> "Ricky" wrote:
>|||Ricky wrote:
> Thanks for the tip. But i must go with the first option once i've tried th
e
> second option you advice but the excutable i want to run in the remote
> server doesn't do an audit to the software and hardware of the remote
> server.
> The executable file is audit32.exe from www.itsolutions.intuit.com
> Can you design for me the dts and send it to my email?.. Or give me the
> right/direct way of doing that in DTS of SQL Server 2000.
>
So you're trying to perform a Trackit audit on a remote machine from
within SQL Server? This isn't going to work. That executable file must
be run ON THE MACHINE that you want to audit. Running it from within
SQL, via xp_cmdshell, DTS, SQL Agent, whatever, is going to execute it
on the SQL Server machine, not the remote machine. You're either going
to have to schedule it on the remote machine itself, or find some way to
open a remote command shell to the remote machine.|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:%23eePm2flGHA.3528@.TK2MSFTNGP02.phx.gbl...
> Ricky wrote:
> So you're trying to perform a Trackit audit on a remote machine from
> within SQL Server? This isn't going to work. That executable file must
> be run ON THE MACHINE that you want to audit. Running it from within SQL,
> via xp_cmdshell, DTS, SQL Agent, whatever, is going to execute it on the
> SQL Server machine, not the remote machine. You're either going to have
> to schedule it on the remote machine itself, or find some way to open a
> remote command shell to the remote machine.
You're right but to run the Trackit audit in the remote server i only have
to
let the file in that specific remote server and share the directory where is
it.
The final purpose is to make a DTS with schedule and force the Trackit audit
run at x time. So i need help for this design. Can you help me?...
Thanks
Ricky|||Ricky wrote:
> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
> news:%23eePm2flGHA.3528@.TK2MSFTNGP02.phx.gbl...
>
> You're right but to run the Trackit audit in the remote server i only have
> to
> let the file in that specific remote server and share the directory where
is
> it.
> The final purpose is to make a DTS with schedule and force the Trackit aud
it
> run at x time. So i need help for this design. Can you help me?...
> Thanks
> Ricky
>
Running the executable from a job ON YOUR SQL SERVER is NOT going to
execute it on the remote server. To illustrate, go to your SQL Server
machine, open Explorer, navigate to the executable via the UNC path to
your remote share. If you double-click on the executable, it's going to
run within the context of your SQL Server machine.
You need to run the audit within the context of the remote machine,
meaning it needs to be scheduled ON THE REMOTE SERVER.|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:elzOtfmlGHA.3588@.TK2MSFTNGP02.phx.gbl...
> Ricky wrote:
> Running the executable from a job ON YOUR SQL SERVER is NOT going to
> execute it on the remote server. To illustrate, go to your SQL Server
> machine, open Explorer, navigate to the executable via the UNC path to
> your remote share. If you double-click on the executable, it's going to
> run within the context of your SQL Server machine.
> You need to run the audit within the context of the remote machine,
> meaning it needs to be scheduled ON THE REMOTE SERVER.
>
Yes i know that. The audit must be schedule on the Remote Server.
But couldn't i do that by creating a DTS Schedule that will run in a shared
directory where is the audit32.exe?
Thanks
Ricky|||Ricky wrote:
> Yes i know that. The audit must be schedule on the Remote Server.
> But couldn't i do that by creating a DTS Schedule that will run in a share
d
> directory where is the audit32.exe?
> Thanks
> Ricky
>
Open Windows Explorer on your SQL Server machine. Navigate to the
remote share that contains the audit32.exe file, double-click the exe
file. Where does the program run? It runs on your SQL Server machine.
If you schedule the job ON THE SQL SERVER MACHINE, SQL is going to do
exactly what you just did - it's going to pull the exe from the remote
share and run it, ON THE SQL SERVER MACHINE. I really truly don't know
a better way to explain execution context to you, perhaps you should
consult with one of your local IT guys?|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:uP9vpFMmGHA.856@.TK2MSFTNGP03.phx.gbl...
> Ricky wrote:
> Open Windows Explorer on your SQL Server machine. Navigate to the remote
> share that contains the audit32.exe file, double-click the exe file.
> Where does the program run? It runs on your SQL Server machine. If you
> schedule the job ON THE SQL SERVER MACHINE, SQL is going to do exactly
> what you just did - it's going to pull the exe from the remote share and
> run it, ON THE SQL SERVER MACHINE. I really truly don't know a better way
> to explain execution context to you, perhaps you should consult with one
> of your local IT guys?
Ok. I've already understand what you mean. So what do you advice then? Once
i've already try windows schedule and didn't work well.
Thanks
Ricky|||Ricky wrote:
> Ok. I've already understand what you mean. So what do you advice then? Onc
e
> i've already try windows schedule and didn't work well.
> Thanks
> Ricky
>
Recent versions of TrackIT offer the ability to do scheduled audits.
Consult your Administrator's Guide for details on how to set one up.

schedule dts at a remote server

Hi
Can somenone help me build a DTS in SQL Server 2000 that allows to schedule
the execution of a executable file in a remote server without sql server?...
[]
RickyRicky,
try to read up on xp_cmdshell in BOL.
--
Venkat
sql server admirer
"Ricky" wrote:
> Hi
> Can somenone help me build a DTS in SQL Server 2000 that allows to schedule
> the execution of a executable file in a remote server without sql server?...
> []
> Ricky
>
>
>|||I didn't understand what "xp_cmdshell in BOL" is. Can you explain better.
Sorry but i'm a newbie on this matter.
Thanks
Ricky
"Venkat" <Venkat@.discussions.microsoft.com> wrote in message
news:39EFAD0A-689B-441E-A444-9CC7FCA660D8@.microsoft.com...
> Ricky,
> try to read up on xp_cmdshell in BOL.
> --
> Venkat
> sql server admirer
>
> "Ricky" wrote:
>> Hi
>> Can somenone help me build a DTS in SQL Server 2000 that allows to
>> schedule
>> the execution of a executable file in a remote server without sql
>> server?...
>> []
>> Ricky
>>
>>
>>