I recently reviewd our Veritas backup jobs and found several databases
failing on backup. I then went through the native SQL Backup processes and
found that these databases were indeed backing up to disk, but not thru the
Veritas client. After further review all of these database all had one thing
in common. They all had E:\PathName\\FileName.MDF in their filenames.
(Notice the double \\) I corrected this by detaching and reattaching with
move. What I wanna know is if anyone noticed this problem and what is
creating it?
Thanx for your help,
Raoul B. LaoyanGenerally it's Enterprise Manager. If the Default Data or Default Log
directory as viewed in Server Properties in EM have a trailing backslash
then new databases created without specifying filenames will have a \\ in
their path. To resolve this simply remove the trailing backslash from the
default data and log paths.
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raoul Laoyan" <RaoulLaoyan@.discussions.microsoft.com> wrote in message
news:A049D4BF-0FBA-49BA-B031-CF6B21021B2A@.microsoft.com...
>I recently reviewd our Veritas backup jobs and found several databases
> failing on backup. I then went through the native SQL Backup processes
> and
> found that these databases were indeed backing up to disk, but not thru
> the
> Veritas client. After further review all of these database all had one
> thing
> in common. They all had E:\PathName\\FileName.MDF in their filenames.
> (Notice the double \\) I corrected this by detaching and reattaching with
> move. What I wanna know is if anyone noticed this problem and what is
> creating it?
> Thanx for your help,
> Raoul B. Laoyan
Showing posts with label jobs. Show all posts
Showing posts with label jobs. Show all posts
Sunday, March 11, 2012
Duble \\ in physical file name
I recently reviewd our Veritas backup jobs and found several databases
failing on backup. I then went through the native SQL Backup processes and
found that these databases were indeed backing up to disk, but not thru the
Veritas client. After further review all of these database all had one thing
in common. They all had E:\PathName\\FileName.MDF in their filenames.
(Notice the double \\) I corrected this by detaching and reattaching with
move. What I wanna know is if anyone noticed this problem and what is
creating it?
Thanx for your help,
Raoul B. Laoyan
Generally it's Enterprise Manager. If the Default Data or Default Log
directory as viewed in Server Properties in EM have a trailing backslash
then new databases created without specifying filenames will have a \\ in
their path. To resolve this simply remove the trailing backslash from the
default data and log paths.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raoul Laoyan" <RaoulLaoyan@.discussions.microsoft.com> wrote in message
news:A049D4BF-0FBA-49BA-B031-CF6B21021B2A@.microsoft.com...
>I recently reviewd our Veritas backup jobs and found several databases
> failing on backup. I then went through the native SQL Backup processes
> and
> found that these databases were indeed backing up to disk, but not thru
> the
> Veritas client. After further review all of these database all had one
> thing
> in common. They all had E:\PathName\\FileName.MDF in their filenames.
> (Notice the double \\) I corrected this by detaching and reattaching with
> move. What I wanna know is if anyone noticed this problem and what is
> creating it?
> Thanx for your help,
> Raoul B. Laoyan
failing on backup. I then went through the native SQL Backup processes and
found that these databases were indeed backing up to disk, but not thru the
Veritas client. After further review all of these database all had one thing
in common. They all had E:\PathName\\FileName.MDF in their filenames.
(Notice the double \\) I corrected this by detaching and reattaching with
move. What I wanna know is if anyone noticed this problem and what is
creating it?
Thanx for your help,
Raoul B. Laoyan
Generally it's Enterprise Manager. If the Default Data or Default Log
directory as viewed in Server Properties in EM have a trailing backslash
then new databases created without specifying filenames will have a \\ in
their path. To resolve this simply remove the trailing backslash from the
default data and log paths.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raoul Laoyan" <RaoulLaoyan@.discussions.microsoft.com> wrote in message
news:A049D4BF-0FBA-49BA-B031-CF6B21021B2A@.microsoft.com...
>I recently reviewd our Veritas backup jobs and found several databases
> failing on backup. I then went through the native SQL Backup processes
> and
> found that these databases were indeed backing up to disk, but not thru
> the
> Veritas client. After further review all of these database all had one
> thing
> in common. They all had E:\PathName\\FileName.MDF in their filenames.
> (Notice the double \\) I corrected this by detaching and reattaching with
> move. What I wanna know is if anyone noticed this problem and what is
> creating it?
> Thanx for your help,
> Raoul B. Laoyan
Duble \\ in physical file name
I recently reviewd our Veritas backup jobs and found several databases
failing on backup. I then went through the native SQL Backup processes and
found that these databases were indeed backing up to disk, but not thru the
Veritas client. After further review all of these database all had one thin
g
in common. They all had E:\PathName\\FileName.MDF in their filenames.
(Notice the double \\) I corrected this by detaching and reattaching with
move. What I wanna know is if anyone noticed this problem and what is
creating it?
Thanx for your help,
Raoul B. LaoyanGenerally it's Enterprise Manager. If the Default Data or Default Log
directory as viewed in Server Properties in EM have a trailing backslash
then new databases created without specifying filenames will have a \\ in
their path. To resolve this simply remove the trailing backslash from the
default data and log paths.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raoul Laoyan" <RaoulLaoyan@.discussions.microsoft.com> wrote in message
news:A049D4BF-0FBA-49BA-B031-CF6B21021B2A@.microsoft.com...
>I recently reviewd our Veritas backup jobs and found several databases
> failing on backup. I then went through the native SQL Backup processes
> and
> found that these databases were indeed backing up to disk, but not thru
> the
> Veritas client. After further review all of these database all had one
> thing
> in common. They all had E:\PathName\\FileName.MDF in their filenames.
> (Notice the double \\) I corrected this by detaching and reattaching with
> move. What I wanna know is if anyone noticed this problem and what is
> creating it?
> Thanx for your help,
> Raoul B. Laoyan
failing on backup. I then went through the native SQL Backup processes and
found that these databases were indeed backing up to disk, but not thru the
Veritas client. After further review all of these database all had one thin
g
in common. They all had E:\PathName\\FileName.MDF in their filenames.
(Notice the double \\) I corrected this by detaching and reattaching with
move. What I wanna know is if anyone noticed this problem and what is
creating it?
Thanx for your help,
Raoul B. LaoyanGenerally it's Enterprise Manager. If the Default Data or Default Log
directory as viewed in Server Properties in EM have a trailing backslash
then new databases created without specifying filenames will have a \\ in
their path. To resolve this simply remove the trailing backslash from the
default data and log paths.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raoul Laoyan" <RaoulLaoyan@.discussions.microsoft.com> wrote in message
news:A049D4BF-0FBA-49BA-B031-CF6B21021B2A@.microsoft.com...
>I recently reviewd our Veritas backup jobs and found several databases
> failing on backup. I then went through the native SQL Backup processes
> and
> found that these databases were indeed backing up to disk, but not thru
> the
> Veritas client. After further review all of these database all had one
> thing
> in common. They all had E:\PathName\\FileName.MDF in their filenames.
> (Notice the double \\) I corrected this by detaching and reattaching with
> move. What I wanna know is if anyone noticed this problem and what is
> creating it?
> Thanx for your help,
> Raoul B. Laoyan
Friday, March 9, 2012
Dual Log Shipping Restore Jobs
I have 2 SQL server 2000 servers, Server A, and Server B.
Server A is production. It has a log shipping restore job that updates the
database every half hour throughout the day automatically.
Server B is a reporting/test server, that has its log shipped restored
manually every 6 hours.
There is a job on Server A, that copies the transaction logs to a folder on
Server B every half hour.
We are manually restoring the transaction logs for Server B, that are copied
into this folder every 6 hours. So yeah, we have 6 hours worth of half hour t-
logs to restore every 6 hours.
I need to create a job, on server A, that will automatically restore the t-
log every 6 hours on Server B , AND keep its current half-hour log shipping
plan so we won't have to keep manually restoring the t-logs on Server B every
day?
So server A will continue to restore every half hour, and server b will be
restored with a big bulldog t-log file for the last 6 hours.
I hope that ws made clear.
Any insight would be wonderful, thanks in advance.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200510/1
Just a thought, have you considered replication every 30 mintues or so
instead of immediate updating? (I assume you aren't doing this with
immediate updating due to the load or something like that).
Shawn Mason
Shawn Mason
Customer Support
http://www.visualonline.net
"Frank N via droptable.com" <u10790@.uwe> wrote in message
news:5687be0f857c0@.uwe...
>I have 2 SQL server 2000 servers, Server A, and Server B.
> Server A is production. It has a log shipping restore job that updates the
> database every half hour throughout the day automatically.
> Server B is a reporting/test server, that has its log shipped restored
> manually every 6 hours.
> There is a job on Server A, that copies the transaction logs to a folder
> on
> Server B every half hour.
> We are manually restoring the transaction logs for Server B, that are
> copied
> into this folder every 6 hours. So yeah, we have 6 hours worth of half
> hour t-
> logs to restore every 6 hours.
> I need to create a job, on server A, that will automatically restore the
> t-
> log every 6 hours on Server B , AND keep its current half-hour log
> shipping
> plan so we won't have to keep manually restoring the t-logs on Server B
> every
> day?
> So server A will continue to restore every half hour, and server b will be
> restored with a big bulldog t-log file for the last 6 hours.
> I hope that ws made clear.
> Any insight would be wonderful, thanks in advance.
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200510/1
Server A is production. It has a log shipping restore job that updates the
database every half hour throughout the day automatically.
Server B is a reporting/test server, that has its log shipped restored
manually every 6 hours.
There is a job on Server A, that copies the transaction logs to a folder on
Server B every half hour.
We are manually restoring the transaction logs for Server B, that are copied
into this folder every 6 hours. So yeah, we have 6 hours worth of half hour t-
logs to restore every 6 hours.
I need to create a job, on server A, that will automatically restore the t-
log every 6 hours on Server B , AND keep its current half-hour log shipping
plan so we won't have to keep manually restoring the t-logs on Server B every
day?
So server A will continue to restore every half hour, and server b will be
restored with a big bulldog t-log file for the last 6 hours.
I hope that ws made clear.
Any insight would be wonderful, thanks in advance.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200510/1
Just a thought, have you considered replication every 30 mintues or so
instead of immediate updating? (I assume you aren't doing this with
immediate updating due to the load or something like that).
Shawn Mason
Shawn Mason
Customer Support
http://www.visualonline.net
"Frank N via droptable.com" <u10790@.uwe> wrote in message
news:5687be0f857c0@.uwe...
>I have 2 SQL server 2000 servers, Server A, and Server B.
> Server A is production. It has a log shipping restore job that updates the
> database every half hour throughout the day automatically.
> Server B is a reporting/test server, that has its log shipped restored
> manually every 6 hours.
> There is a job on Server A, that copies the transaction logs to a folder
> on
> Server B every half hour.
> We are manually restoring the transaction logs for Server B, that are
> copied
> into this folder every 6 hours. So yeah, we have 6 hours worth of half
> hour t-
> logs to restore every 6 hours.
> I need to create a job, on server A, that will automatically restore the
> t-
> log every 6 hours on Server B , AND keep its current half-hour log
> shipping
> plan so we won't have to keep manually restoring the t-logs on Server B
> every
> day?
> So server A will continue to restore every half hour, and server b will be
> restored with a big bulldog t-log file for the last 6 hours.
> I hope that ws made clear.
> Any insight would be wonderful, thanks in advance.
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200510/1
Dual Log Shipping Restore Jobs
I have 2 SQL server 2000 servers, Server A, and Server B.
Server A is production. It has a log shipping restore job that updates the
database every half hour throughout the day automatically.
Server B is a reporting/test server, that has its log shipped restored
manually every 6 hours.
There is a job on Server A, that copies the transaction logs to a folder on
Server B every half hour.
We are manually restoring the transaction logs for Server B, that are copie
d
into this folder every 6 hours. So yeah, we have 6 hours worth of half hour
t-
logs to restore every 6 hours.
I need to create a job, on server A, that will automatically restore the t-
log every 6 hours on Server B , AND keep its current half-hour log shipping
plan so we won't have to keep manually restoring the t-logs on Server B ever
y
day?
So server A will continue to restore every half hour, and server b will be
restored with a big bulldog t-log file for the last 6 hours.
I hope that ws made clear.
Any insight would be wonderful, thanks in advance.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...server/200510/1Just a thought, have you considered replication every 30 mintues or so
instead of immediate updating? (I assume you aren't doing this with
immediate updating due to the load or something like that).
Shawn Mason
Shawn Mason
Customer Support
http://www.visualonline.net
"Frank N via droptable.com" <u10790@.uwe> wrote in message
news:5687be0f857c0@.uwe...
>I have 2 SQL server 2000 servers, Server A, and Server B.
> Server A is production. It has a log shipping restore job that updates the
> database every half hour throughout the day automatically.
> Server B is a reporting/test server, that has its log shipped restored
> manually every 6 hours.
> There is a job on Server A, that copies the transaction logs to a folder
> on
> Server B every half hour.
> We are manually restoring the transaction logs for Server B, that are
> copied
> into this folder every 6 hours. So yeah, we have 6 hours worth of half
> hour t-
> logs to restore every 6 hours.
> I need to create a job, on server A, that will automatically restore the
> t-
> log every 6 hours on Server B , AND keep its current half-hour log
> shipping
> plan so we won't have to keep manually restoring the t-logs on Server B
> every
> day?
> So server A will continue to restore every half hour, and server b will be
> restored with a big bulldog t-log file for the last 6 hours.
> I hope that ws made clear.
> Any insight would be wonderful, thanks in advance.
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200510/1
Server A is production. It has a log shipping restore job that updates the
database every half hour throughout the day automatically.
Server B is a reporting/test server, that has its log shipped restored
manually every 6 hours.
There is a job on Server A, that copies the transaction logs to a folder on
Server B every half hour.
We are manually restoring the transaction logs for Server B, that are copie
d
into this folder every 6 hours. So yeah, we have 6 hours worth of half hour
t-
logs to restore every 6 hours.
I need to create a job, on server A, that will automatically restore the t-
log every 6 hours on Server B , AND keep its current half-hour log shipping
plan so we won't have to keep manually restoring the t-logs on Server B ever
y
day?
So server A will continue to restore every half hour, and server b will be
restored with a big bulldog t-log file for the last 6 hours.
I hope that ws made clear.
Any insight would be wonderful, thanks in advance.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...server/200510/1Just a thought, have you considered replication every 30 mintues or so
instead of immediate updating? (I assume you aren't doing this with
immediate updating due to the load or something like that).
Shawn Mason
Shawn Mason
Customer Support
http://www.visualonline.net
"Frank N via droptable.com" <u10790@.uwe> wrote in message
news:5687be0f857c0@.uwe...
>I have 2 SQL server 2000 servers, Server A, and Server B.
> Server A is production. It has a log shipping restore job that updates the
> database every half hour throughout the day automatically.
> Server B is a reporting/test server, that has its log shipped restored
> manually every 6 hours.
> There is a job on Server A, that copies the transaction logs to a folder
> on
> Server B every half hour.
> We are manually restoring the transaction logs for Server B, that are
> copied
> into this folder every 6 hours. So yeah, we have 6 hours worth of half
> hour t-
> logs to restore every 6 hours.
> I need to create a job, on server A, that will automatically restore the
> t-
> log every 6 hours on Server B , AND keep its current half-hour log
> shipping
> plan so we won't have to keep manually restoring the t-logs on Server B
> every
> day?
> So server A will continue to restore every half hour, and server b will be
> restored with a big bulldog t-log file for the last 6 hours.
> I hope that ws made clear.
> Any insight would be wonderful, thanks in advance.
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200510/1
Dual Log Shipping Restore Jobs
I have 2 SQL server 2000 servers, Server A, and Server B.
Server A is production. It has a log shipping restore job that updates the
database every half hour throughout the day automatically.
Server B is a reporting/test server, that has its log shipped restored
manually every 6 hours.
There is a job on Server A, that copies the transaction logs to a folder on
Server B every half hour.
We are manually restoring the transaction logs for Server B, that are copied
into this folder every 6 hours. So yeah, we have 6 hours worth of half hour t-
logs to restore every 6 hours.
I need to create a job, on server A, that will automatically restore the t-
log every 6 hours on Server B , AND keep its current half-hour log shipping
plan so we won't have to keep manually restoring the t-logs on Server B every
day?
So server A will continue to restore every half hour, and server b will be
restored with a big bulldog t-log file for the last 6 hours.
I hope that ws made clear.
Any insight would be wonderful, thanks in advance.
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200510/1Just a thought, have you considered replication every 30 mintues or so
instead of immediate updating? (I assume you aren't doing this with
immediate updating due to the load or something like that).
Shawn Mason
--
Shawn Mason
Customer Support
http://www.visualonline.net
"Frank N via SQLMonster.com" <u10790@.uwe> wrote in message
news:5687be0f857c0@.uwe...
>I have 2 SQL server 2000 servers, Server A, and Server B.
> Server A is production. It has a log shipping restore job that updates the
> database every half hour throughout the day automatically.
> Server B is a reporting/test server, that has its log shipped restored
> manually every 6 hours.
> There is a job on Server A, that copies the transaction logs to a folder
> on
> Server B every half hour.
> We are manually restoring the transaction logs for Server B, that are
> copied
> into this folder every 6 hours. So yeah, we have 6 hours worth of half
> hour t-
> logs to restore every 6 hours.
> I need to create a job, on server A, that will automatically restore the
> t-
> log every 6 hours on Server B , AND keep its current half-hour log
> shipping
> plan so we won't have to keep manually restoring the t-logs on Server B
> every
> day?
> So server A will continue to restore every half hour, and server b will be
> restored with a big bulldog t-log file for the last 6 hours.
> I hope that ws made clear.
> Any insight would be wonderful, thanks in advance.
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200510/1
Server A is production. It has a log shipping restore job that updates the
database every half hour throughout the day automatically.
Server B is a reporting/test server, that has its log shipped restored
manually every 6 hours.
There is a job on Server A, that copies the transaction logs to a folder on
Server B every half hour.
We are manually restoring the transaction logs for Server B, that are copied
into this folder every 6 hours. So yeah, we have 6 hours worth of half hour t-
logs to restore every 6 hours.
I need to create a job, on server A, that will automatically restore the t-
log every 6 hours on Server B , AND keep its current half-hour log shipping
plan so we won't have to keep manually restoring the t-logs on Server B every
day?
So server A will continue to restore every half hour, and server b will be
restored with a big bulldog t-log file for the last 6 hours.
I hope that ws made clear.
Any insight would be wonderful, thanks in advance.
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200510/1Just a thought, have you considered replication every 30 mintues or so
instead of immediate updating? (I assume you aren't doing this with
immediate updating due to the load or something like that).
Shawn Mason
--
Shawn Mason
Customer Support
http://www.visualonline.net
"Frank N via SQLMonster.com" <u10790@.uwe> wrote in message
news:5687be0f857c0@.uwe...
>I have 2 SQL server 2000 servers, Server A, and Server B.
> Server A is production. It has a log shipping restore job that updates the
> database every half hour throughout the day automatically.
> Server B is a reporting/test server, that has its log shipped restored
> manually every 6 hours.
> There is a job on Server A, that copies the transaction logs to a folder
> on
> Server B every half hour.
> We are manually restoring the transaction logs for Server B, that are
> copied
> into this folder every 6 hours. So yeah, we have 6 hours worth of half
> hour t-
> logs to restore every 6 hours.
> I need to create a job, on server A, that will automatically restore the
> t-
> log every 6 hours on Server B , AND keep its current half-hour log
> shipping
> plan so we won't have to keep manually restoring the t-logs on Server B
> every
> day?
> So server A will continue to restore every half hour, and server b will be
> restored with a big bulldog t-log file for the last 6 hours.
> I hope that ws made clear.
> Any insight would be wonderful, thanks in advance.
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200510/1
Sunday, February 26, 2012
DTSRun remote execution
Hi,
I am trying to figure out a way for a machine other than the SQL Server 2000 machine hosting my DTS jobs to fire off a DTS job on request. The jobs are scheduled, but I want to be able to fire them off remotely if the schedule fails. I don't have access Enterprise Manager on the second machine I want to start the jobs from.
An added restriction I have is that I can only execute command line shell scripts on the second machine. This could be a batch file, an executable or any other function available from the command line.
In an initial attempt I made the SQL Server Binn directory available via a restricted network share so the second machine could access the DTSRun.exe file. I then created the DTSRun commands and set them up to run. This worked fine, except I ran into another complication. The DTS Jobs I am running make use of an ActiveX DLL and an ActiveX Control (OCX). These files are registered on the server, but since using DTSRun forces execution to take place on the machine issuing the DTSRun command, the jobs fail because the components are not installed on the second machine.
I would like to try and aviod installing these components on the second machine and was hoping someone could suggest an alternative method for remotely fireing off these DTSJobs.
Any help would be greatly appreciated!
Thanks!
- BradMy first suggestion would be to use a VBScript that uses ADO to manually force execution of the remote job that runs the DTS package.
Just about anything else (SP, CmdExec, etc) is going to run the DTS in the context of your client which may not be desirable for reasons other than the registered ActiveX controls you mention.
Another option might be to create a job or DTS package that checks the original and makes sure that it has run (and executes it if it has not). Or you could simply add this as an additional error check into the original DTS package (set a retry counter and a Global Variable with the maximum number of retries). You would need to examine the business requirements and design a strategy that suits your environment.
Regards,
Hugh Scott
Originally posted by BradC
Hi,
I am trying to figure out a way for a machine other than the SQL Server 2000 machine hosting my DTS jobs to fire off a DTS job on request. The jobs are scheduled, but I want to be able to fire them off remotely if the schedule fails. I don't have access Enterprise Manager on the second machine I want to start the jobs from.
An added restriction I have is that I can only execute command line shell scripts on the second machine. This could be a batch file, an executable or any other function available from the command line.
In an initial attempt I made the SQL Server Binn directory available via a restricted network share so the second machine could access the DTSRun.exe file. I then created the DTSRun commands and set them up to run. This worked fine, except I ran into another complication. The DTS Jobs I am running make use of an ActiveX DLL and an ActiveX Control (OCX). These files are registered on the server, but since using DTSRun forces execution to take place on the machine issuing the DTSRun command, the jobs fail because the components are not installed on the second machine.
I would like to try and aviod installing these components on the second machine and was hoping someone could suggest an alternative method for remotely fireing off these DTSJobs.
Any help would be greatly appreciated!
Thanks!
- Brad|||Hi Hugh, thanks for the reply.
The VBScript option sounds like it may be the way to go. Using a number of retries approach may not work in this case because we need to be able to manually fire off the jobs on request. Catch is, the people who will be firing off these jobs don't have access (or skills) to go into enterprise manager to run them.
If a VBScript file is used to fire off a job using ADO, would the job be executed on the server or on the local client machine? From your comments on context I gather it will be run on the server (which is a good thing in this case as it avoids the ActiveX components needing to be installed on client machines).
Thanks again for the help!
- Brad
[SIZE=1]Originally posted by hmscott
My first suggestion would be to use a VBScript that uses ADO to manually force execution of the remote job that runs the DTS package.|||Im using a stored procedure to run my DTS from the outside whenever I want.
CREATE PROCEDURE ProcImportFile AS
EXEC msdb.dbo.sp_start_job @.job_name = 'Import_file'
GO
I scheduled the DTS package to get a job to call from the procedure.
Haven't tried this solution fully yet beacuse there is some problems regarding the permissions on my database. If i execute the package manually it works fine. But the scheduled job fails averytime...
Helpdesk hasn't fixed it yet.
I am trying to figure out a way for a machine other than the SQL Server 2000 machine hosting my DTS jobs to fire off a DTS job on request. The jobs are scheduled, but I want to be able to fire them off remotely if the schedule fails. I don't have access Enterprise Manager on the second machine I want to start the jobs from.
An added restriction I have is that I can only execute command line shell scripts on the second machine. This could be a batch file, an executable or any other function available from the command line.
In an initial attempt I made the SQL Server Binn directory available via a restricted network share so the second machine could access the DTSRun.exe file. I then created the DTSRun commands and set them up to run. This worked fine, except I ran into another complication. The DTS Jobs I am running make use of an ActiveX DLL and an ActiveX Control (OCX). These files are registered on the server, but since using DTSRun forces execution to take place on the machine issuing the DTSRun command, the jobs fail because the components are not installed on the second machine.
I would like to try and aviod installing these components on the second machine and was hoping someone could suggest an alternative method for remotely fireing off these DTSJobs.
Any help would be greatly appreciated!
Thanks!
- BradMy first suggestion would be to use a VBScript that uses ADO to manually force execution of the remote job that runs the DTS package.
Just about anything else (SP, CmdExec, etc) is going to run the DTS in the context of your client which may not be desirable for reasons other than the registered ActiveX controls you mention.
Another option might be to create a job or DTS package that checks the original and makes sure that it has run (and executes it if it has not). Or you could simply add this as an additional error check into the original DTS package (set a retry counter and a Global Variable with the maximum number of retries). You would need to examine the business requirements and design a strategy that suits your environment.
Regards,
Hugh Scott
Originally posted by BradC
Hi,
I am trying to figure out a way for a machine other than the SQL Server 2000 machine hosting my DTS jobs to fire off a DTS job on request. The jobs are scheduled, but I want to be able to fire them off remotely if the schedule fails. I don't have access Enterprise Manager on the second machine I want to start the jobs from.
An added restriction I have is that I can only execute command line shell scripts on the second machine. This could be a batch file, an executable or any other function available from the command line.
In an initial attempt I made the SQL Server Binn directory available via a restricted network share so the second machine could access the DTSRun.exe file. I then created the DTSRun commands and set them up to run. This worked fine, except I ran into another complication. The DTS Jobs I am running make use of an ActiveX DLL and an ActiveX Control (OCX). These files are registered on the server, but since using DTSRun forces execution to take place on the machine issuing the DTSRun command, the jobs fail because the components are not installed on the second machine.
I would like to try and aviod installing these components on the second machine and was hoping someone could suggest an alternative method for remotely fireing off these DTSJobs.
Any help would be greatly appreciated!
Thanks!
- Brad|||Hi Hugh, thanks for the reply.
The VBScript option sounds like it may be the way to go. Using a number of retries approach may not work in this case because we need to be able to manually fire off the jobs on request. Catch is, the people who will be firing off these jobs don't have access (or skills) to go into enterprise manager to run them.
If a VBScript file is used to fire off a job using ADO, would the job be executed on the server or on the local client machine? From your comments on context I gather it will be run on the server (which is a good thing in this case as it avoids the ActiveX components needing to be installed on client machines).
Thanks again for the help!
- Brad
[SIZE=1]Originally posted by hmscott
My first suggestion would be to use a VBScript that uses ADO to manually force execution of the remote job that runs the DTS package.|||Im using a stored procedure to run my DTS from the outside whenever I want.
CREATE PROCEDURE ProcImportFile AS
EXEC msdb.dbo.sp_start_job @.job_name = 'Import_file'
GO
I scheduled the DTS package to get a job to call from the procedure.
Haven't tried this solution fully yet beacuse there is some problems regarding the permissions on my database. If i execute the package manually it works fine. But the scheduled job fails averytime...
Helpdesk hasn't fixed it yet.
Wednesday, February 15, 2012
dts to copy jobs
We are upgrading our SQL 2000 Enterprise Server to a new server running the
same. When using DTS to transfer the jobs from old server to new 4 of them
will not transfer over to the new server. It just gives a unspecified error.
Any ideas?
You can generate a script for the jobs instead, through Enterprise Manager
(right click a job name, and it is under Tasks). Just run the generated
script on the target server.
Andy Price,
Sr. Database Administrator,
MCDBA 2003
"Tom Reis" wrote:
> We are upgrading our SQL 2000 Enterprise Server to a new server running the
> same. When using DTS to transfer the jobs from old server to new 4 of them
> will not transfer over to the new server. It just gives a unspecified error.
> Any ideas?
>
>
same. When using DTS to transfer the jobs from old server to new 4 of them
will not transfer over to the new server. It just gives a unspecified error.
Any ideas?
You can generate a script for the jobs instead, through Enterprise Manager
(right click a job name, and it is under Tasks). Just run the generated
script on the target server.
Andy Price,
Sr. Database Administrator,
MCDBA 2003
"Tom Reis" wrote:
> We are upgrading our SQL 2000 Enterprise Server to a new server running the
> same. When using DTS to transfer the jobs from old server to new 4 of them
> will not transfer over to the new server. It just gives a unspecified error.
> Any ideas?
>
>
dts to copy jobs
We are upgrading our SQL 2000 Enterprise Server to a new server running the
same. When using DTS to transfer the jobs from old server to new 4 of them
will not transfer over to the new server. It just gives a unspecified error.
Any ideas?You can generate a script for the jobs instead, through Enterprise Manager
(right click a job name, and it is under Tasks). Just run the generated
script on the target server.
Andy Price,
Sr. Database Administrator,
MCDBA 2003
"Tom Reis" wrote:
> We are upgrading our SQL 2000 Enterprise Server to a new server running th
e
> same. When using DTS to transfer the jobs from old server to new 4 of them
> will not transfer over to the new server. It just gives a unspecified erro
r.
> Any ideas?
>
>
same. When using DTS to transfer the jobs from old server to new 4 of them
will not transfer over to the new server. It just gives a unspecified error.
Any ideas?You can generate a script for the jobs instead, through Enterprise Manager
(right click a job name, and it is under Tasks). Just run the generated
script on the target server.
Andy Price,
Sr. Database Administrator,
MCDBA 2003
"Tom Reis" wrote:
> We are upgrading our SQL 2000 Enterprise Server to a new server running th
e
> same. When using DTS to transfer the jobs from old server to new 4 of them
> will not transfer over to the new server. It just gives a unspecified erro
r.
> Any ideas?
>
>
dts to copy jobs
We are upgrading our SQL 2000 Enterprise Server to a new server running the
same. When using DTS to transfer the jobs from old server to new 4 of them
will not transfer over to the new server. It just gives a unspecified error.
Any ideas?You can generate a script for the jobs instead, through Enterprise Manager
(right click a job name, and it is under Tasks). Just run the generated
script on the target server.
Andy Price,
Sr. Database Administrator,
MCDBA 2003
"Tom Reis" wrote:
> We are upgrading our SQL 2000 Enterprise Server to a new server running the
> same. When using DTS to transfer the jobs from old server to new 4 of them
> will not transfer over to the new server. It just gives a unspecified error.
> Any ideas?
>
>
same. When using DTS to transfer the jobs from old server to new 4 of them
will not transfer over to the new server. It just gives a unspecified error.
Any ideas?You can generate a script for the jobs instead, through Enterprise Manager
(right click a job name, and it is under Tasks). Just run the generated
script on the target server.
Andy Price,
Sr. Database Administrator,
MCDBA 2003
"Tom Reis" wrote:
> We are upgrading our SQL 2000 Enterprise Server to a new server running the
> same. When using DTS to transfer the jobs from old server to new 4 of them
> will not transfer over to the new server. It just gives a unspecified error.
> Any ideas?
>
>
Subscribe to:
Posts (Atom)