I am trying to create a centralized job monitoring system that can be
managed by some operators to restart a job if it fails. Everything
will be running on one system but I need to invoke remote jobs on
remote system. I am having trouble starting a job on a remote system
even if I have the permissions to do so.
[Code]
DECLARE @.SQLCMD VARCHAR(MAX)
SET @.SQLCMD = ''
DECLARE @.SystemNameVARCHAR(50)
DECLARE @.JobNameVARCHAR(50)
DECLARE @.StepNameVARCHAR(50)
SET @.SystemName = RemoteServer
SET @.JobName = Explode
SET @.StepName = BadStep
SET @.SQLCMD = '' + @.SystemName + '.msdb.dbo.sp_start_job @.job_name =
''' + @.JobName + ''', @.step_name = ''' + @.StepName + ''''
PRINT @.SQLCMD
[/code]
This will generate the following
RemoteServer.msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name =
'Bad'
If i run this command as an adhoc command, it will execute on the
RemoteServer and start the job at the step. However for the SP i am
writing this does not work
[Code]
EXEC @.SQLCMD
EXEC msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name = 'Bad'
[/Code]
This error appers.
Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'msdb.dbo.sp_start_job @.job_name =
'Explode', @.step_name = 'Bad''.
If I try to run it this way, I get the following error message.
EXEC msdb.dbo.sp_start_job @.server_name = 'dbdev4', @.job_name =
'Explode', @.step_name = 'Bad'
Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
Line 67
The specified @.job_name ('Explode') does not exist.
Any ideas
Thanks
-Matt-
Hi Matt
"Matthew" wrote:
> I am trying to create a centralized job monitoring system that can be
> managed by some operators to restart a job if it fails. Everything
> will be running on one system but I need to invoke remote jobs on
> remote system. I am having trouble starting a job on a remote system
> even if I have the permissions to do so.
> [Code]
> DECLARE @.SQLCMD VARCHAR(MAX)
> SET @.SQLCMD = ''
> DECLARE @.SystemNameVARCHAR(50)
> DECLARE @.JobNameVARCHAR(50)
> DECLARE @.StepNameVARCHAR(50)
> SET @.SystemName = RemoteServer
> SET @.JobName = Explode
> SET @.StepName = BadStep
> SET @.SQLCMD = '' + @.SystemName + '.msdb.dbo.sp_start_job @.job_name =
> ''' + @.JobName + ''', @.step_name = ''' + @.StepName + ''''
> PRINT @.SQLCMD
> [/code]
> This will generate the following
> RemoteServer.msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name =
> 'Bad'
> If i run this command as an adhoc command, it will execute on the
> RemoteServer and start the job at the step. However for the SP i am
> writing this does not work
> [Code]
> EXEC @.SQLCMD
> EXEC msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name = 'Bad'
> [/Code]
> This error appers.
> Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'msdb.dbo.sp_start_job @.job_name =
> 'Explode', @.step_name = 'Bad''.
Try:
EXEC ( @.SQLCMD )
or
EXEC RemoteServer.msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name =
'Bad'
> If I try to run it this way, I get the following error message.
> EXEC msdb.dbo.sp_start_job @.server_name = 'dbdev4', @.job_name =
> 'Explode', @.step_name = 'Bad'
> Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
> Line 67
> The specified @.job_name ('Explode') does not exist.
> Any ideas
> Thanks
> -Matt-
John
Showing posts with label job. Show all posts
Showing posts with label job. Show all posts
Tuesday, March 27, 2012
EXEC sp_start_job Remote Server
I am trying to create a centralized job monitoring system that can be
managed by some operators to restart a job if it fails. Everything
will be running on one system but I need to invoke remote jobs on
remote system. I am having trouble starting a job on a remote system
even if I have the permissions to do so.
[Code]
DECLARE @.SQLCMD VARCHAR(MAX)
SET @.SQLCMD = ''
DECLARE @.SystemName VARCHAR(50)
DECLARE @.JobName VARCHAR(50)
DECLARE @.StepName VARCHAR(50)
SET @.SystemName = RemoteServer
SET @.JobName = Explode
SET @.StepName = BadStep
SET @.SQLCMD = '' + @.SystemName + '.msdb.dbo.sp_start_job @.job_name =
''' + @.JobName + ''', @.step_name = ''' + @.StepName + ''''
PRINT @.SQLCMD
[/code]
This will generate the following
RemoteServer.msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name =
'Bad'
If i run this command as an adhoc command, it will execute on the
RemoteServer and start the job at the step. However for the SP i am
writing this does not work
[Code]
EXEC @.SQLCMD
EXEC msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name = 'Bad'
[/Code]
This error appers.
Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'msdb.dbo.sp_start_job @.job_name =
'Explode', @.step_name = 'Bad''.
If I try to run it this way, I get the following error message.
EXEC msdb.dbo.sp_start_job @.server_name = 'dbdev4', @.job_name =
'Explode', @.step_name = 'Bad'
Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
Line 67
The specified @.job_name ('Explode') does not exist.
Any ideas
Thanks
-Matt-Hi Matt
"Matthew" wrote:
> I am trying to create a centralized job monitoring system that can be
> managed by some operators to restart a job if it fails. Everything
> will be running on one system but I need to invoke remote jobs on
> remote system. I am having trouble starting a job on a remote system
> even if I have the permissions to do so.
> [Code]
> DECLARE @.SQLCMD VARCHAR(MAX)
> SET @.SQLCMD = ''
> DECLARE @.SystemName VARCHAR(50)
> DECLARE @.JobName VARCHAR(50)
> DECLARE @.StepName VARCHAR(50)
> SET @.SystemName = RemoteServer
> SET @.JobName = Explode
> SET @.StepName = BadStep
> SET @.SQLCMD = '' + @.SystemName + '.msdb.dbo.sp_start_job @.job_name =
> ''' + @.JobName + ''', @.step_name = ''' + @.StepName + ''''
> PRINT @.SQLCMD
> [/code]
> This will generate the following
> RemoteServer.msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name =
> 'Bad'
> If i run this command as an adhoc command, it will execute on the
> RemoteServer and start the job at the step. However for the SP i am
> writing this does not work
> [Code]
> EXEC @.SQLCMD
> EXEC msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name = 'Bad'
> [/Code]
> This error appers.
> Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'msdb.dbo.sp_start_job @.job_name =
> 'Explode', @.step_name = 'Bad''.
Try:
EXEC ( @.SQLCMD )
or
EXEC RemoteServer.msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name =
'Bad'
> If I try to run it this way, I get the following error message.
> EXEC msdb.dbo.sp_start_job @.server_name = 'dbdev4', @.job_name =
> 'Explode', @.step_name = 'Bad'
> Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
> Line 67
> The specified @.job_name ('Explode') does not exist.
> Any ideas
> Thanks
> -Matt-
Johnsql
managed by some operators to restart a job if it fails. Everything
will be running on one system but I need to invoke remote jobs on
remote system. I am having trouble starting a job on a remote system
even if I have the permissions to do so.
[Code]
DECLARE @.SQLCMD VARCHAR(MAX)
SET @.SQLCMD = ''
DECLARE @.SystemName VARCHAR(50)
DECLARE @.JobName VARCHAR(50)
DECLARE @.StepName VARCHAR(50)
SET @.SystemName = RemoteServer
SET @.JobName = Explode
SET @.StepName = BadStep
SET @.SQLCMD = '' + @.SystemName + '.msdb.dbo.sp_start_job @.job_name =
''' + @.JobName + ''', @.step_name = ''' + @.StepName + ''''
PRINT @.SQLCMD
[/code]
This will generate the following
RemoteServer.msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name =
'Bad'
If i run this command as an adhoc command, it will execute on the
RemoteServer and start the job at the step. However for the SP i am
writing this does not work
[Code]
EXEC @.SQLCMD
EXEC msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name = 'Bad'
[/Code]
This error appers.
Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'msdb.dbo.sp_start_job @.job_name =
'Explode', @.step_name = 'Bad''.
If I try to run it this way, I get the following error message.
EXEC msdb.dbo.sp_start_job @.server_name = 'dbdev4', @.job_name =
'Explode', @.step_name = 'Bad'
Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
Line 67
The specified @.job_name ('Explode') does not exist.
Any ideas
Thanks
-Matt-Hi Matt
"Matthew" wrote:
> I am trying to create a centralized job monitoring system that can be
> managed by some operators to restart a job if it fails. Everything
> will be running on one system but I need to invoke remote jobs on
> remote system. I am having trouble starting a job on a remote system
> even if I have the permissions to do so.
> [Code]
> DECLARE @.SQLCMD VARCHAR(MAX)
> SET @.SQLCMD = ''
> DECLARE @.SystemName VARCHAR(50)
> DECLARE @.JobName VARCHAR(50)
> DECLARE @.StepName VARCHAR(50)
> SET @.SystemName = RemoteServer
> SET @.JobName = Explode
> SET @.StepName = BadStep
> SET @.SQLCMD = '' + @.SystemName + '.msdb.dbo.sp_start_job @.job_name =
> ''' + @.JobName + ''', @.step_name = ''' + @.StepName + ''''
> PRINT @.SQLCMD
> [/code]
> This will generate the following
> RemoteServer.msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name =
> 'Bad'
> If i run this command as an adhoc command, it will execute on the
> RemoteServer and start the job at the step. However for the SP i am
> writing this does not work
> [Code]
> EXEC @.SQLCMD
> EXEC msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name = 'Bad'
> [/Code]
> This error appers.
> Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'msdb.dbo.sp_start_job @.job_name =
> 'Explode', @.step_name = 'Bad''.
Try:
EXEC ( @.SQLCMD )
or
EXEC RemoteServer.msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name =
'Bad'
> If I try to run it this way, I get the following error message.
> EXEC msdb.dbo.sp_start_job @.server_name = 'dbdev4', @.job_name =
> 'Explode', @.step_name = 'Bad'
> Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
> Line 67
> The specified @.job_name ('Explode') does not exist.
> Any ideas
> Thanks
> -Matt-
Johnsql
EXEC sp_start_job Remote Server
I am trying to create a centralized job monitoring system that can be
managed by some operators to restart a job if it fails. Everything
will be running on one system but I need to invoke remote jobs on
remote system. I am having trouble starting a job on a remote system
even if I have the permissions to do so.
[Code]
DECLARE @.SQLCMD VARCHAR(MAX)
SET @.SQLCMD = ''
DECLARE @.SystemName VARCHAR(50)
DECLARE @.JobName VARCHAR(50)
DECLARE @.StepName VARCHAR(50)
SET @.SystemName = RemoteServer
SET @.JobName = Explode
SET @.StepName = BadStep
SET @.SQLCMD = '' + @.SystemName + '.msdb.dbo.sp_start_job @.job_name = ''' + @.JobName + ''', @.step_name = ''' + @.StepName + ''''
PRINT @.SQLCMD
[/code]
This will generate the following
RemoteServer.msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name = 'Bad'
If i run this command as an adhoc command, it will execute on the
RemoteServer and start the job at the step. However for the SP i am
writing this does not work
[Code]
EXEC @.SQLCMD
EXEC msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name = 'Bad'
[/Code]
This error appers.
Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name = 'Bad''.
If I try to run it this way, I get the following error message.
EXEC msdb.dbo.sp_start_job @.server_name = 'dbdev4', @.job_name = 'Explode', @.step_name = 'Bad'
Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
Line 67
The specified @.job_name ('Explode') does not exist.
Any ideas
Thanks
-Matt-Hi Matt
"Matthew" wrote:
> I am trying to create a centralized job monitoring system that can be
> managed by some operators to restart a job if it fails. Everything
> will be running on one system but I need to invoke remote jobs on
> remote system. I am having trouble starting a job on a remote system
> even if I have the permissions to do so.
> [Code]
> DECLARE @.SQLCMD VARCHAR(MAX)
> SET @.SQLCMD = ''
> DECLARE @.SystemName VARCHAR(50)
> DECLARE @.JobName VARCHAR(50)
> DECLARE @.StepName VARCHAR(50)
> SET @.SystemName = RemoteServer
> SET @.JobName = Explode
> SET @.StepName = BadStep
> SET @.SQLCMD = '' + @.SystemName + '.msdb.dbo.sp_start_job @.job_name => ''' + @.JobName + ''', @.step_name = ''' + @.StepName + ''''
> PRINT @.SQLCMD
> [/code]
> This will generate the following
> RemoteServer.msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name => 'Bad'
> If i run this command as an adhoc command, it will execute on the
> RemoteServer and start the job at the step. However for the SP i am
> writing this does not work
> [Code]
> EXEC @.SQLCMD
> EXEC msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name = 'Bad'
> [/Code]
> This error appers.
> Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'msdb.dbo.sp_start_job @.job_name => 'Explode', @.step_name = 'Bad''.
Try:
EXEC ( @.SQLCMD )
or
EXEC RemoteServer.msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name ='Bad'
> If I try to run it this way, I get the following error message.
> EXEC msdb.dbo.sp_start_job @.server_name = 'dbdev4', @.job_name => 'Explode', @.step_name = 'Bad'
> Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
> Line 67
> The specified @.job_name ('Explode') does not exist.
> Any ideas
> Thanks
> -Matt-
John
managed by some operators to restart a job if it fails. Everything
will be running on one system but I need to invoke remote jobs on
remote system. I am having trouble starting a job on a remote system
even if I have the permissions to do so.
[Code]
DECLARE @.SQLCMD VARCHAR(MAX)
SET @.SQLCMD = ''
DECLARE @.SystemName VARCHAR(50)
DECLARE @.JobName VARCHAR(50)
DECLARE @.StepName VARCHAR(50)
SET @.SystemName = RemoteServer
SET @.JobName = Explode
SET @.StepName = BadStep
SET @.SQLCMD = '' + @.SystemName + '.msdb.dbo.sp_start_job @.job_name = ''' + @.JobName + ''', @.step_name = ''' + @.StepName + ''''
PRINT @.SQLCMD
[/code]
This will generate the following
RemoteServer.msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name = 'Bad'
If i run this command as an adhoc command, it will execute on the
RemoteServer and start the job at the step. However for the SP i am
writing this does not work
[Code]
EXEC @.SQLCMD
EXEC msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name = 'Bad'
[/Code]
This error appers.
Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name = 'Bad''.
If I try to run it this way, I get the following error message.
EXEC msdb.dbo.sp_start_job @.server_name = 'dbdev4', @.job_name = 'Explode', @.step_name = 'Bad'
Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
Line 67
The specified @.job_name ('Explode') does not exist.
Any ideas
Thanks
-Matt-Hi Matt
"Matthew" wrote:
> I am trying to create a centralized job monitoring system that can be
> managed by some operators to restart a job if it fails. Everything
> will be running on one system but I need to invoke remote jobs on
> remote system. I am having trouble starting a job on a remote system
> even if I have the permissions to do so.
> [Code]
> DECLARE @.SQLCMD VARCHAR(MAX)
> SET @.SQLCMD = ''
> DECLARE @.SystemName VARCHAR(50)
> DECLARE @.JobName VARCHAR(50)
> DECLARE @.StepName VARCHAR(50)
> SET @.SystemName = RemoteServer
> SET @.JobName = Explode
> SET @.StepName = BadStep
> SET @.SQLCMD = '' + @.SystemName + '.msdb.dbo.sp_start_job @.job_name => ''' + @.JobName + ''', @.step_name = ''' + @.StepName + ''''
> PRINT @.SQLCMD
> [/code]
> This will generate the following
> RemoteServer.msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name => 'Bad'
> If i run this command as an adhoc command, it will execute on the
> RemoteServer and start the job at the step. However for the SP i am
> writing this does not work
> [Code]
> EXEC @.SQLCMD
> EXEC msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name = 'Bad'
> [/Code]
> This error appers.
> Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'msdb.dbo.sp_start_job @.job_name => 'Explode', @.step_name = 'Bad''.
Try:
EXEC ( @.SQLCMD )
or
EXEC RemoteServer.msdb.dbo.sp_start_job @.job_name = 'Explode', @.step_name ='Bad'
> If I try to run it this way, I get the following error message.
> EXEC msdb.dbo.sp_start_job @.server_name = 'dbdev4', @.job_name => 'Explode', @.step_name = 'Bad'
> Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers,
> Line 67
> The specified @.job_name ('Explode') does not exist.
> Any ideas
> Thanks
> -Matt-
John
Monday, March 26, 2012
exec a .sql file
Hi,
I need to create a sql job that exec a .sql file located in c:\.
Anyone knows how to?
ThanksCreate a job step of type: Operating System
Enter a command: OSQL -E -i C:\MyFolder\myscript.sql -o
C:\MyFolder\myscript.txt
Assuming that the account running OSQL has the needed rights, then OSQL will
run the script for you.
What account you run as differs depending on whether you are running SQL
2000 or 2005. Read about SQL Agent proxy accounts.
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:ueohAzIpHHA.4196@.TK2MSFTNGP06.phx.gbl...
> Hi,
> I need to create a sql job that exec a .sql file located in c:\.
> Anyone knows how to?
> Thanks
>|||I'll try. Thanks a lot
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:ORU1z$IpHHA.5052@.TK2MSFTNGP04.phx.gbl...
> Create a job step of type: Operating System
> Enter a command: OSQL -E -i C:\MyFolder\myscript.sql -o
> C:\MyFolder\myscript.txt
> Assuming that the account running OSQL has the needed rights, then OSQL
> will run the script for you.
> What account you run as differs depending on whether you are running SQL
> 2000 or 2005. Read about SQL Agent proxy accounts.
> RLF
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:ueohAzIpHHA.4196@.TK2MSFTNGP06.phx.gbl...
>> Hi,
>> I need to create a sql job that exec a .sql file located in c:\.
>> Anyone knows how to?
>> Thanks
>
I need to create a sql job that exec a .sql file located in c:\.
Anyone knows how to?
ThanksCreate a job step of type: Operating System
Enter a command: OSQL -E -i C:\MyFolder\myscript.sql -o
C:\MyFolder\myscript.txt
Assuming that the account running OSQL has the needed rights, then OSQL will
run the script for you.
What account you run as differs depending on whether you are running SQL
2000 or 2005. Read about SQL Agent proxy accounts.
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:ueohAzIpHHA.4196@.TK2MSFTNGP06.phx.gbl...
> Hi,
> I need to create a sql job that exec a .sql file located in c:\.
> Anyone knows how to?
> Thanks
>|||I'll try. Thanks a lot
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:ORU1z$IpHHA.5052@.TK2MSFTNGP04.phx.gbl...
> Create a job step of type: Operating System
> Enter a command: OSQL -E -i C:\MyFolder\myscript.sql -o
> C:\MyFolder\myscript.txt
> Assuming that the account running OSQL has the needed rights, then OSQL
> will run the script for you.
> What account you run as differs depending on whether you are running SQL
> 2000 or 2005. Read about SQL Agent proxy accounts.
> RLF
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:ueohAzIpHHA.4196@.TK2MSFTNGP06.phx.gbl...
>> Hi,
>> I need to create a sql job that exec a .sql file located in c:\.
>> Anyone knows how to?
>> Thanks
>
exec a .sql file
Hi,
I need to create a sql job that exec a .sql file located in c:\.
Anyone knows how to?
ThanksCreate a job step of type: Operating System
Enter a command: OSQL -E -i C:\MyFolder\myscript.sql -o
C:\MyFolder\myscript.txt
Assuming that the account running OSQL has the needed rights, then OSQL will
run the script for you.
What account you run as differs depending on whether you are running SQL
2000 or 2005. Read about SQL Agent proxy accounts.
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:ueohAzIpHHA.4196@.TK2MSFTNGP06.phx.gbl...
> Hi,
> I need to create a sql job that exec a .sql file located in c:\.
> Anyone knows how to?
> Thanks
>|||I'll try. Thanks a lot
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:ORU1z$IpHHA.5052@.TK2MSFTNGP04.phx.gbl...
> Create a job step of type: Operating System
> Enter a command: OSQL -E -i C:\MyFolder\myscript.sql -o
> C:\MyFolder\myscript.txt
> Assuming that the account running OSQL has the needed rights, then OSQL
> will run the script for you.
> What account you run as differs depending on whether you are running SQL
> 2000 or 2005. Read about SQL Agent proxy accounts.
> RLF
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:ueohAzIpHHA.4196@.TK2MSFTNGP06.phx.gbl...
>
I need to create a sql job that exec a .sql file located in c:\.
Anyone knows how to?
ThanksCreate a job step of type: Operating System
Enter a command: OSQL -E -i C:\MyFolder\myscript.sql -o
C:\MyFolder\myscript.txt
Assuming that the account running OSQL has the needed rights, then OSQL will
run the script for you.
What account you run as differs depending on whether you are running SQL
2000 or 2005. Read about SQL Agent proxy accounts.
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:ueohAzIpHHA.4196@.TK2MSFTNGP06.phx.gbl...
> Hi,
> I need to create a sql job that exec a .sql file located in c:\.
> Anyone knows how to?
> Thanks
>|||I'll try. Thanks a lot
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:ORU1z$IpHHA.5052@.TK2MSFTNGP04.phx.gbl...
> Create a job step of type: Operating System
> Enter a command: OSQL -E -i C:\MyFolder\myscript.sql -o
> C:\MyFolder\myscript.txt
> Assuming that the account running OSQL has the needed rights, then OSQL
> will run the script for you.
> What account you run as differs depending on whether you are running SQL
> 2000 or 2005. Read about SQL Agent proxy accounts.
> RLF
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:ueohAzIpHHA.4196@.TK2MSFTNGP06.phx.gbl...
>
exec a .sql file
Hi,
I need to create a sql job that exec a .sql file located in c:\.
Anyone knows how to?
Thanks
Create a job step of type: Operating System
Enter a command: OSQL -E -i C:\MyFolder\myscript.sql -o
C:\MyFolder\myscript.txt
Assuming that the account running OSQL has the needed rights, then OSQL will
run the script for you.
What account you run as differs depending on whether you are running SQL
2000 or 2005. Read about SQL Agent proxy accounts.
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:ueohAzIpHHA.4196@.TK2MSFTNGP06.phx.gbl...
> Hi,
> I need to create a sql job that exec a .sql file located in c:\.
> Anyone knows how to?
> Thanks
>
|||I'll try. Thanks a lot
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:ORU1z$IpHHA.5052@.TK2MSFTNGP04.phx.gbl...
> Create a job step of type: Operating System
> Enter a command: OSQL -E -i C:\MyFolder\myscript.sql -o
> C:\MyFolder\myscript.txt
> Assuming that the account running OSQL has the needed rights, then OSQL
> will run the script for you.
> What account you run as differs depending on whether you are running SQL
> 2000 or 2005. Read about SQL Agent proxy accounts.
> RLF
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:ueohAzIpHHA.4196@.TK2MSFTNGP06.phx.gbl...
>
I need to create a sql job that exec a .sql file located in c:\.
Anyone knows how to?
Thanks
Create a job step of type: Operating System
Enter a command: OSQL -E -i C:\MyFolder\myscript.sql -o
C:\MyFolder\myscript.txt
Assuming that the account running OSQL has the needed rights, then OSQL will
run the script for you.
What account you run as differs depending on whether you are running SQL
2000 or 2005. Read about SQL Agent proxy accounts.
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:ueohAzIpHHA.4196@.TK2MSFTNGP06.phx.gbl...
> Hi,
> I need to create a sql job that exec a .sql file located in c:\.
> Anyone knows how to?
> Thanks
>
|||I'll try. Thanks a lot
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:ORU1z$IpHHA.5052@.TK2MSFTNGP04.phx.gbl...
> Create a job step of type: Operating System
> Enter a command: OSQL -E -i C:\MyFolder\myscript.sql -o
> C:\MyFolder\myscript.txt
> Assuming that the account running OSQL has the needed rights, then OSQL
> will run the script for you.
> What account you run as differs depending on whether you are running SQL
> 2000 or 2005. Read about SQL Agent proxy accounts.
> RLF
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:ueohAzIpHHA.4196@.TK2MSFTNGP06.phx.gbl...
>
Friday, March 23, 2012
exec .sql file
Hi,
How do I exec a .sql file from a sql job(code)
ThanksOSQL - See BOL
"mecn" <mecn2002@.yahoo.com> wrote in message
news:%23Gr%23iLfNIHA.5980@.TK2MSFTNGP04.phx.gbl...
> Hi,
> How do I exec a .sql file from a sql job(code)
> Thanks
>
How do I exec a .sql file from a sql job(code)
ThanksOSQL - See BOL
"mecn" <mecn2002@.yahoo.com> wrote in message
news:%23Gr%23iLfNIHA.5980@.TK2MSFTNGP04.phx.gbl...
> Hi,
> How do I exec a .sql file from a sql job(code)
> Thanks
>
Friday, February 24, 2012
Exception
I start a job (the job successfully executes) but I notice in a trace that an
Exception occurs when the job starts. This is the output for the SQL:
BatchCompleted. Any idea why this would throw an exception? It appears as
though it is all SQL Server generated code.
create table #tmp_sp_help_category
(category_id int null, category_type tinyint null, name nvarchar(128) null)
insert into #tmp_sp_help_category exec msdb.dbo.sp_help_category
SELECT
sv.name AS [Name],
CAST(sv.enabled AS bit) AS [IsEnabled],
tshc.name AS [Category],
null AS [CurrentRunStatus],
null AS [CurrentRunStep],
null AS [HasSchedule],
null AS [HasStep],
null AS [HasServer],
null AS [LastRunDate],
null AS [NextRunDate],
null AS [LastRunOutcome],
CAST(sv.job_id AS nvarchar(100)) AS [job_id]
FROM
msdb.dbo.sysjobs_view AS sv
INNER JOIN #tmp_sp_help_category AS tshc ON sv.category_id = tshc.category_id
WHERE
(sv.name=N'Trace Duration Job 1')
drop table #tmp_sp_help_category
--
Message posted via http://www.sqlmonster.comHi
You may want to look at batch/statement starting to find what is causing
this rather than what has completed.
John
"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:5eeb1211a50ab@.uwe...
>I start a job (the job successfully executes) but I notice in a trace that
>an
> Exception occurs when the job starts. This is the output for the SQL:
> BatchCompleted. Any idea why this would throw an exception? It appears as
> though it is all SQL Server generated code.
>
> create table #tmp_sp_help_category
> (category_id int null, category_type tinyint null, name nvarchar(128)
> null)
> insert into #tmp_sp_help_category exec msdb.dbo.sp_help_category
> SELECT
> sv.name AS [Name],
> CAST(sv.enabled AS bit) AS [IsEnabled],
> tshc.name AS [Category],
> null AS [CurrentRunStatus],
> null AS [CurrentRunStep],
> null AS [HasSchedule],
> null AS [HasStep],
> null AS [HasServer],
> null AS [LastRunDate],
> null AS [NextRunDate],
> null AS [LastRunOutcome],
> CAST(sv.job_id AS nvarchar(100)) AS [job_id]
> FROM
> msdb.dbo.sysjobs_view AS sv
> INNER JOIN #tmp_sp_help_category AS tshc ON sv.category_id => tshc.category_id
> WHERE
> (sv.name=N'Trace Duration Job 1')
> drop table #tmp_sp_help_category
> --
> Message posted via http://www.sqlmonster.com
Exception occurs when the job starts. This is the output for the SQL:
BatchCompleted. Any idea why this would throw an exception? It appears as
though it is all SQL Server generated code.
create table #tmp_sp_help_category
(category_id int null, category_type tinyint null, name nvarchar(128) null)
insert into #tmp_sp_help_category exec msdb.dbo.sp_help_category
SELECT
sv.name AS [Name],
CAST(sv.enabled AS bit) AS [IsEnabled],
tshc.name AS [Category],
null AS [CurrentRunStatus],
null AS [CurrentRunStep],
null AS [HasSchedule],
null AS [HasStep],
null AS [HasServer],
null AS [LastRunDate],
null AS [NextRunDate],
null AS [LastRunOutcome],
CAST(sv.job_id AS nvarchar(100)) AS [job_id]
FROM
msdb.dbo.sysjobs_view AS sv
INNER JOIN #tmp_sp_help_category AS tshc ON sv.category_id = tshc.category_id
WHERE
(sv.name=N'Trace Duration Job 1')
drop table #tmp_sp_help_category
--
Message posted via http://www.sqlmonster.comHi
You may want to look at batch/statement starting to find what is causing
this rather than what has completed.
John
"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:5eeb1211a50ab@.uwe...
>I start a job (the job successfully executes) but I notice in a trace that
>an
> Exception occurs when the job starts. This is the output for the SQL:
> BatchCompleted. Any idea why this would throw an exception? It appears as
> though it is all SQL Server generated code.
>
> create table #tmp_sp_help_category
> (category_id int null, category_type tinyint null, name nvarchar(128)
> null)
> insert into #tmp_sp_help_category exec msdb.dbo.sp_help_category
> SELECT
> sv.name AS [Name],
> CAST(sv.enabled AS bit) AS [IsEnabled],
> tshc.name AS [Category],
> null AS [CurrentRunStatus],
> null AS [CurrentRunStep],
> null AS [HasSchedule],
> null AS [HasStep],
> null AS [HasServer],
> null AS [LastRunDate],
> null AS [NextRunDate],
> null AS [LastRunOutcome],
> CAST(sv.job_id AS nvarchar(100)) AS [job_id]
> FROM
> msdb.dbo.sysjobs_view AS sv
> INNER JOIN #tmp_sp_help_category AS tshc ON sv.category_id => tshc.category_id
> WHERE
> (sv.name=N'Trace Duration Job 1')
> drop table #tmp_sp_help_category
> --
> Message posted via http://www.sqlmonster.com
Exception
I start a job (the job successfully executes) but I notice in a trace that a
n
Exception occurs when the job starts. This is the output for the SQL:
BatchCompleted. Any idea why this would throw an exception? It appears as
though it is all SQL Server generated code.
create table #tmp_sp_help_category
(category_id int null, category_type tinyint null, name nvarchar(128) null)
insert into #tmp_sp_help_category exec msdb.dbo.sp_help_category
SELECT
sv.name AS [Name],
CAST(sv.enabled AS bit) AS [IsEnabled],
tshc.name AS [Category],
null AS [CurrentRunStatus],
null AS [CurrentRunStep],
null AS [HasSchedule],
null AS [HasStep],
null AS [HasServer],
null AS [LastRunDate],
null AS [NextRunDate],
null AS [LastRunOutcome],
CAST(sv.job_id AS nvarchar(100)) AS [job_id]
FROM
msdb.dbo.sysjobs_view AS sv
INNER JOIN #tmp_sp_help_category AS tshc ON sv.category_id = tshc.category_i
d
WHERE
(sv.name=N'Trace Duration Job 1')
drop table #tmp_sp_help_category
Message posted via http://www.droptable.comHi
You may want to look at batch/statement starting to find what is causing
this rather than what has completed.
John
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:5eeb1211a50ab@.uwe...
>I start a job (the job successfully executes) but I notice in a trace that
>an
> Exception occurs when the job starts. This is the output for the SQL:
> BatchCompleted. Any idea why this would throw an exception? It appears as
> though it is all SQL Server generated code.
>
> create table #tmp_sp_help_category
> (category_id int null, category_type tinyint null, name nvarchar(128)
> null)
> insert into #tmp_sp_help_category exec msdb.dbo.sp_help_category
> SELECT
> sv.name AS [Name],
> CAST(sv.enabled AS bit) AS [IsEnabled],
> tshc.name AS [Category],
> null AS [CurrentRunStatus],
> null AS [CurrentRunStep],
> null AS [HasSchedule],
> null AS [HasStep],
> null AS [HasServer],
> null AS [LastRunDate],
> null AS [NextRunDate],
> null AS [LastRunOutcome],
> CAST(sv.job_id AS nvarchar(100)) AS [job_id]
> FROM
> msdb.dbo.sysjobs_view AS sv
> INNER JOIN #tmp_sp_help_category AS tshc ON sv.category_id =
> tshc.category_id
> WHERE
> (sv.name=N'Trace Duration Job 1')
> drop table #tmp_sp_help_category
> --
> Message posted via http://www.droptable.com
n
Exception occurs when the job starts. This is the output for the SQL:
BatchCompleted. Any idea why this would throw an exception? It appears as
though it is all SQL Server generated code.
create table #tmp_sp_help_category
(category_id int null, category_type tinyint null, name nvarchar(128) null)
insert into #tmp_sp_help_category exec msdb.dbo.sp_help_category
SELECT
sv.name AS [Name],
CAST(sv.enabled AS bit) AS [IsEnabled],
tshc.name AS [Category],
null AS [CurrentRunStatus],
null AS [CurrentRunStep],
null AS [HasSchedule],
null AS [HasStep],
null AS [HasServer],
null AS [LastRunDate],
null AS [NextRunDate],
null AS [LastRunOutcome],
CAST(sv.job_id AS nvarchar(100)) AS [job_id]
FROM
msdb.dbo.sysjobs_view AS sv
INNER JOIN #tmp_sp_help_category AS tshc ON sv.category_id = tshc.category_i
d
WHERE
(sv.name=N'Trace Duration Job 1')
drop table #tmp_sp_help_category
Message posted via http://www.droptable.comHi
You may want to look at batch/statement starting to find what is causing
this rather than what has completed.
John
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:5eeb1211a50ab@.uwe...
>I start a job (the job successfully executes) but I notice in a trace that
>an
> Exception occurs when the job starts. This is the output for the SQL:
> BatchCompleted. Any idea why this would throw an exception? It appears as
> though it is all SQL Server generated code.
>
> create table #tmp_sp_help_category
> (category_id int null, category_type tinyint null, name nvarchar(128)
> null)
> insert into #tmp_sp_help_category exec msdb.dbo.sp_help_category
> SELECT
> sv.name AS [Name],
> CAST(sv.enabled AS bit) AS [IsEnabled],
> tshc.name AS [Category],
> null AS [CurrentRunStatus],
> null AS [CurrentRunStep],
> null AS [HasSchedule],
> null AS [HasStep],
> null AS [HasServer],
> null AS [LastRunDate],
> null AS [NextRunDate],
> null AS [LastRunOutcome],
> CAST(sv.job_id AS nvarchar(100)) AS [job_id]
> FROM
> msdb.dbo.sysjobs_view AS sv
> INNER JOIN #tmp_sp_help_category AS tshc ON sv.category_id =
> tshc.category_id
> WHERE
> (sv.name=N'Trace Duration Job 1')
> drop table #tmp_sp_help_category
> --
> Message posted via http://www.droptable.com
Sunday, February 19, 2012
Excel Rendering updated?
I'm wondering whether Katmai Reporting Services will do a better job of "rendering" to Excel. Quite Frequently, I create nice looking reports for the PDF renderer, only to to make a separate copy of that same report and mangle it so that I can get half of what I wanted.
For example:
1. I am frequently lining up the left and right edges of text boxes everywhere, as to not generate way too many columns in excel. As a result, I'm often formatting for excel to look, often ignoring the formatting needs of my data. The worst case scenario of this is when I had two rows of textboxes (roughly seven textboxes each) , and the PDF renderer did a beautiful job. However the Excel renderer would randomly choose to push some of the textboxes down into another Excel row, giving a checker-board look to my report. Hours were wasted in attempts to reformat a separate copy of the report to eliminate the Checkerboard look, to no avail.
2. Formatting Data in any way (FormatCurrency(), FormatDate(), ect) converts the data type to string, and my excel reports are flooded with smart tags saying "Convert to Number". These reports do not gracefully import into my client's applications. In addition to this, there is no way to format the textboxes so that Excel's Cell formatting will be given to the cells (right click on a cell, "Format Cells" and choose a category and some options with different categories). I can leave the data unformatted, but it looks SO unprofessional. So I have been evaluating several other Excel reporting packages that will allow me to Format Cells without changing the data types of my data to a string.
3. Images. Yikes! The PDF renderer has had some occasional glitches with images that some vendors have given us. We have thousands of vendors that give us images created with a large spectrum of consumer digital cameras. Occasionally, the PDF renderer refuses to render (a large gamut of error messages have been seen), while the TIFF renderer will suceed. I have even had an image (still do if you would find them helpful) that will not even render through the TIFF renderer. I had to open the image and "Save As " to get the TIFF renderer to work, but the PDF renderer would still not work. So we had to create some backup tools to "Resave the images" and also "use the TIFF version instead", both of which cost us personnel time.
Please let me know if these will be fixed in the Katmai RS?!?
For #1, the Excel rendering has improved in Katmai, mainly around reducing the number of merged cells. However, it looks like you are looking for more of a data renderer, which is currently not planned.
For #2, why are you using the Format... functions instead of setting the format property? If you set the format property, you should get numbers with the appropriate formatting.
For #3, it sounds like you are running into a bug, either with our PDF renderer or the framework image libraries. Have you filed repro cases at http://connect.microsoft.com?
Brian|||
Alternatively, if you are having problem getting http://connect.microsoft.com to work, you can email me directly with a sample of the problem images. Clicking on my name to the left will show my email address. Just be sure to put a good subject line so my inbox doesn't delete your email as spam.
Thank you.
Friday, February 17, 2012
Excel Rendering updated?
I'm wondering whether Katmai Reporting Services will do a better job of "rendering" to Excel. Quite Frequently, I create nice looking reports for the PDF renderer, only to to make a separate copy of that same report and mangle it so that I can get half of what I wanted.
For example:
1. I am frequently lining up the left and right edges of text boxes everywhere, as to not generate way too many columns in excel. As a result, I'm often formatting for excel to look, often ignoring the formatting needs of my data. The worst case scenario of this is when I had two rows of textboxes (roughly seven textboxes each) , and the PDF renderer did a beautiful job. However the Excel renderer would randomly choose to push some of the textboxes down into another Excel row, giving a checker-board look to my report. Hours were wasted in attempts to reformat a separate copy of the report to eliminate the Checkerboard look, to no avail.
2. Formatting Data in any way (FormatCurrency(), FormatDate(), ect) converts the data type to string, and my excel reports are flooded with smart tags saying "Convert to Number". These reports do not gracefully import into my client's applications. In addition to this, there is no way to format the textboxes so that Excel's Cell formatting will be given to the cells (right click on a cell, "Format Cells" and choose a category and some options with different categories). I can leave the data unformatted, but it looks SO unprofessional. So I have been evaluating several other Excel reporting packages that will allow me to Format Cells without changing the data types of my data to a string.
3. Images. Yikes! The PDF renderer has had some occasional glitches with images that some vendors have given us. We have thousands of vendors that give us images created with a large spectrum of consumer digital cameras. Occasionally, the PDF renderer refuses to render (a large gamut of error messages have been seen), while the TIFF renderer will suceed. I have even had an image (still do if you would find them helpful) that will not even render through the TIFF renderer. I had to open the image and "Save As " to get the TIFF renderer to work, but the PDF renderer would still not work. So we had to create some backup tools to "Resave the images" and also "use the TIFF version instead", both of which cost us personnel time.
Please let me know if these will be fixed in the Katmai RS?!?
For #1, the Excel rendering has improved in Katmai, mainly around reducing the number of merged cells. However, it looks like you are looking for more of a data renderer, which is currently not planned.
For #2, why are you using the Format... functions instead of setting the format property? If you set the format property, you should get numbers with the appropriate formatting.
For #3, it sounds like you are running into a bug, either with our PDF renderer or the framework image libraries. Have you filed repro cases at http://connect.microsoft.com?
Brian|||Alternatively, if you are having problem getting http://connect.microsoft.com to work, you can email me directly with a sample of the problem images. Clicking on my name to the left will show my email address. Just be sure to put a good subject line so my inbox doesn't delete your email as spam.
Thank you.
Subscribe to:
Posts (Atom)