install SQL on WinXP: job

Showing posts with label job. Show all posts

Sunday, March 25, 2012

Can not create Job on SQL2005

Could not create SQL jobs. Getting Error:

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

- Tried several different job types, always same result.
- Installing SP1 or SP2 does not help.
- Installing with or without Integration Service does not help.

Any help is highly appreciated

Thanks.

Try this:

Dim strDBName As String
Dim strJobID As Guid
Dim jobDumpJob As Job
Dim jbsDumpJobStep As JobStep
Dim intStepID As Integer

' Connect to the server
Dim srvMgmtServer As Server
srvMgmtServer = New Server("MyServer")
Dim srvConn As ServerConnection
srvConn = srvMgmtServer.ConnectionContext
srvConn.LoginSecure = True

strDBName = dbDatabase.Name
jobDumpJob = New Job(srvMgmtServer.JobServer, "YourJobName")
jobDumpJob.Description = "Job Description"
jobDumpJob.Category = "[Uncategorized (Local)]"
jobDumpJob.OwnerLoginName = "sa"
jobDumpJob.Create()
strJobID = jobDumpJob.JobID

jbsDumpJobStep = New JobStep(jobDumpJob, "Step 1")
jbsDumpJobStep.DatabaseName = "UserDB"
jbsDumpJobStep.Command = "TSQL command"
jbsDumpJobStep.OnSuccessAction = StepCompletionAction.QuitWithSuccess
jbsDumpJobStep.OnFailAction = StepCompletionAction.QuitWithFailure
jbsDumpJobStep.Create()
intStepID = jbsDumpJobStep.ID

jobDumpJob.ApplyToTargetServer(srvMgmtServer.Name)
jobDumpJob.StartStepID = intStepID
jobDumpJob.Alter()

|||

I am also having this problem.

Im trying to create a job to run SQL Server Integration Package.

The Code that you have given above. What is that for?

Thanks

|||This code uses SMO in VB.Net to create a job to execute a TSQL command. Browse around in ObjectBrowser and you should find the properties necessary to execute a SSIS package.|||

I can execute the SISS Package.

But i want to execute it within a job.

Is there any tutorials for creating jobs that i could look at?

|||for some reason it works on an another machine. I dont no why.|||

I figured it out. Despite you could install Management Tool on any computer it will work only on machine that have SQL Server 2005 SP2 installed.

|||Try installing SP2 for the client components on all computers taht run management studio, reboot, then try again from management studio client.|||

Identical problems here--also tried the new hotfix as well.

We've held off rolling out SP2 due to these and other errors. Until someone deals with these problems I suppose my company is stuck.

|||Check whether Distributed Transaction Coordinator service is started. If not, start it and try again.|||

We have a sql2005 installation that I've created jobs on routinely for months and then today we hit this message. I'm not going to install SP2 just yet since some users report that it doesn't help.

The details from the error message are as follows. Any help would be much appreciated. I deleted all SSIS packages and Jobs with no luck. We've rebooted and cycled services per suggestions from users.

The original error message:

TITLE: Microsoft SQL Server Management Studio

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

BUTTONS:

Technical details

===================================

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Program Location:

at Microsoft.SqlServer.Management.Smo.Agent.JobCollection.GetObjectByKey(ObjectKeyBase key)
at Microsoft.SqlServer.Management.Smo.SimpleObjectCollectionBase.Contains(String name)
at Microsoft.SqlServer.Management.SqlManagerUI.JobData.JobExists(String jobName)
at Microsoft.SqlServer.Management.SqlManagerUI.JobData.ApplyChanges()
at Microsoft.SqlServer.Management.SqlManagerUI.JobPropertySheet.DoPreProcessExecution(RunType runType, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.DoPreProcessExecutionAndRunViews(RunType runType)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.ExecuteForSql(PreProcessExecutionInfo executionInfo, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.SqlMgmtTreeViewControl.Microsoft.SqlServer.Management.SqlMgmt.IExecutionAwareSqlControlCollection.PreProcessExecution(PreProcessExecutionInfo executionInfo, ExecutionMode& executionResult)
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.RunNow(RunType runType, Object sender)

|||

Hi folks,

I too had the same exact error when trying to schedule a package. After reading numerous posts and forums, some people have said

SP2 solved their problems and some said it didn't.

Here's what I did to get it to work.

On our SQL Server 2005 development machine, we did install SP2

however, that doesn't solve the problem because the problem lies in scheduling your job using Management Studio through your local machine. If you logged onto your SQL 2005 server that has SP2, you should be able to schedule from there. But it's through Management Studio, which I'm guessing most of you are trying to create a job schedule for your packages. Usually, people don't think of upgrading their client tools as well.

I verified this by upgrading my local machine to SP2 for the client tools and was able to successfully schedule. You might also need to upgrade your server machine to SP2 to work as well.

I hope this helps.

-SX

|||

I finally uninstalled all SQL related products and services, reinstalled everything, added hot fixes and finally we have two of the three servers working--mostly. There are still occaisional errors, but most seem limited to SSMS' and its UI

I haven't rolled SP2 to production yet and won't be adding any new SQL servers to our mix until this mess settles. I thought we'd be going to some of the better features (like Mirroring) later this year but now it'll be Q1'08 at the earliest.

Haven't had this much fun since SQL2KSP4! Keep smiling....

|||

Hello Visgor Allen and others!

Thank you for reporting this problem, and sorry for the problems that you are experiencing.

I'd like to understand this issue better so we can provide guidance to other customers. Can somebody on this thread please provide more details on how to repro this problem:

1) What is the initial configuration on both server and client machines (if different)? Is it SQL Server 2005 RTM or SP1?

2) Does the problem reproduce after upgrading client/server/both machines to SP2?

3) From what machine (client/server) are you trying to create a new job?

Thanks in advance!

|||

Unable to create new jobs in sql 2005, SSIS service is running. Finally i was surfing net for solution and understood need to install SP2 in my machine. But if i need to create new jobs in remote system what should i do.

Please suggest me a solution.

Can not create Job on SQL2005

Could not create SQL jobs. Getting Error:

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

- Tried several different job types, always same result.
- Installing SP1 or SP2 does not help.
- Installing with or without Integration Service does not help.

Any help is highly appreciated

Thanks.

Try this:

Dim strDBName As String
Dim strJobID As Guid
Dim jobDumpJob As Job
Dim jbsDumpJobStep As JobStep
Dim intStepID As Integer

' Connect to the server
Dim srvMgmtServer As Server
srvMgmtServer = New Server("MyServer")
Dim srvConn As ServerConnection
srvConn = srvMgmtServer.ConnectionContext
srvConn.LoginSecure = True

jobDumpJob.ApplyToTargetServer(srvMgmtServer.Name)
jobDumpJob.StartStepID = intStepID
jobDumpJob.Alter()

|||

I am also having this problem.

Im trying to create a job to run SQL Server Integration Package.

The Code that you have given above. What is that for?

Thanks

|||This code uses SMO in VB.Net to create a job to execute a TSQL command. Browse around in ObjectBrowser and you should find the properties necessary to execute a SSIS package.|||

I can execute the SISS Package.

But i want to execute it within a job.

Is there any tutorials for creating jobs that i could look at?

|||for some reason it works on an another machine. I dont no why.|||

I figured it out. Despite you could install Management Tool on any computer it will work only on machine that have SQL Server 2005 SP2 installed.

|||Try installing SP2 for the client components on all computers taht run management studio, reboot, then try again from management studio client.|||

Identical problems here--also tried the new hotfix as well.

We've held off rolling out SP2 due to these and other errors. Until someone deals with these problems I suppose my company is stuck.

|||Check whether Distributed Transaction Coordinator service is started. If not, start it and try again.|||

We have a sql2005 installation that I've created jobs on routinely for months and then today we hit this message. I'm not going to install SP2 just yet since some users report that it doesn't help.

The original error message:

TITLE: Microsoft SQL Server Management Studio

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

BUTTONS:

Technical details

===================================

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Program Location:

|||

Hi folks,

I too had the same exact error when trying to schedule a package. After reading numerous posts and forums, some people have said

SP2 solved their problems and some said it didn't.

Here's what I did to get it to work.

On our SQL Server 2005 development machine, we did install SP2

I verified this by upgrading my local machine to SP2 for the client tools and was able to successfully schedule. You might also need to upgrade your server machine to SP2 to work as well.

I hope this helps.

-SX

|||

Haven't had this much fun since SQL2KSP4! Keep smiling....

|||

Hello Visgor Allen and others!

Thank you for reporting this problem, and sorry for the problems that you are experiencing.

I'd like to understand this issue better so we can provide guidance to other customers. Can somebody on this thread please provide more details on how to repro this problem:

1) What is the initial configuration on both server and client machines (if different)? Is it SQL Server 2005 RTM or SP1?

2) Does the problem reproduce after upgrading client/server/both machines to SP2?

3) From what machine (client/server) are you trying to create a new job?

Thanks in advance!

|||

Please suggest me a solution.

Can not create Job on SQL2005

Could not create SQL jobs. Getting Error:

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

- Tried several different job types, always same result.
- Installing SP1 or SP2 does not help.
- Installing with or without Integration Service does not help.

Any help is highly appreciated

Thanks.

Try this:

Dim strDBName As String
Dim strJobID As Guid
Dim jobDumpJob As Job
Dim jbsDumpJobStep As JobStep
Dim intStepID As Integer

' Connect to the server
Dim srvMgmtServer As Server
srvMgmtServer = New Server("MyServer")
Dim srvConn As ServerConnection
srvConn = srvMgmtServer.ConnectionContext
srvConn.LoginSecure = True

jobDumpJob.ApplyToTargetServer(srvMgmtServer.Name)
jobDumpJob.StartStepID = intStepID
jobDumpJob.Alter()

|||

I am also having this problem.

Im trying to create a job to run SQL Server Integration Package.

The Code that you have given above. What is that for?

Thanks

|||This code uses SMO in VB.Net to create a job to execute a TSQL command. Browse around in ObjectBrowser and you should find the properties necessary to execute a SSIS package.|||

I can execute the SISS Package.

But i want to execute it within a job.

Is there any tutorials for creating jobs that i could look at?

|||for some reason it works on an another machine. I dont no why.|||

I figured it out. Despite you could install Management Tool on any computer it will work only on machine that have SQL Server 2005 SP2 installed.

|||Try installing SP2 for the client components on all computers taht run management studio, reboot, then try again from management studio client.|||

Identical problems here--also tried the new hotfix as well.

We've held off rolling out SP2 due to these and other errors. Until someone deals with these problems I suppose my company is stuck.

|||Check whether Distributed Transaction Coordinator service is started. If not, start it and try again.|||

We have a sql2005 installation that I've created jobs on routinely for months and then today we hit this message. I'm not going to install SP2 just yet since some users report that it doesn't help.

The original error message:

TITLE: Microsoft SQL Server Management Studio

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

BUTTONS:

Technical details

===================================

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Program Location:

|||

Hi folks,

I too had the same exact error when trying to schedule a package. After reading numerous posts and forums, some people have said

SP2 solved their problems and some said it didn't.

Here's what I did to get it to work.

On our SQL Server 2005 development machine, we did install SP2

I verified this by upgrading my local machine to SP2 for the client tools and was able to successfully schedule. You might also need to upgrade your server machine to SP2 to work as well.

I hope this helps.

-SX

|||

Haven't had this much fun since SQL2KSP4! Keep smiling....

|||

Hello Visgor Allen and others!

Thank you for reporting this problem, and sorry for the problems that you are experiencing.

I'd like to understand this issue better so we can provide guidance to other customers. Can somebody on this thread please provide more details on how to repro this problem:

1) What is the initial configuration on both server and client machines (if different)? Is it SQL Server 2005 RTM or SP1?

2) Does the problem reproduce after upgrading client/server/both machines to SP2?

3) From what machine (client/server) are you trying to create a new job?

Thanks in advance!

|||

Please suggest me a solution.

Can not create Job on SQL2005

Could not create SQL jobs. Getting Error:

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

- Tried several different job types, always same result.
- Installing SP1 or SP2 does not help.
- Installing with or without Integration Service does not help.

Any help is highly appreciated

Thanks.

Try this:

Dim strDBName As String
Dim strJobID As Guid
Dim jobDumpJob As Job
Dim jbsDumpJobStep As JobStep
Dim intStepID As Integer

' Connect to the server
Dim srvMgmtServer As Server
srvMgmtServer = New Server("MyServer")
Dim srvConn As ServerConnection
srvConn = srvMgmtServer.ConnectionContext
srvConn.LoginSecure = True

jobDumpJob.ApplyToTargetServer(srvMgmtServer.Name)
jobDumpJob.StartStepID = intStepID
jobDumpJob.Alter()

|||

I am also having this problem.

Im trying to create a job to run SQL Server Integration Package.

The Code that you have given above. What is that for?

Thanks

|||This code uses SMO in VB.Net to create a job to execute a TSQL command. Browse around in ObjectBrowser and you should find the properties necessary to execute a SSIS package.|||

I can execute the SISS Package.

But i want to execute it within a job.

Is there any tutorials for creating jobs that i could look at?

|||for some reason it works on an another machine. I dont no why.|||

I figured it out. Despite you could install Management Tool on any computer it will work only on machine that have SQL Server 2005 SP2 installed.

|||Try installing SP2 for the client components on all computers taht run management studio, reboot, then try again from management studio client.|||

Identical problems here--also tried the new hotfix as well.

We've held off rolling out SP2 due to these and other errors. Until someone deals with these problems I suppose my company is stuck.

|||Check whether Distributed Transaction Coordinator service is started. If not, start it and try again.|||

We have a sql2005 installation that I've created jobs on routinely for months and then today we hit this message. I'm not going to install SP2 just yet since some users report that it doesn't help.

The original error message:

TITLE: Microsoft SQL Server Management Studio

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

BUTTONS:

Technical details

===================================

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Program Location:

|||

Hi folks,

I too had the same exact error when trying to schedule a package. After reading numerous posts and forums, some people have said

SP2 solved their problems and some said it didn't.

Here's what I did to get it to work.

On our SQL Server 2005 development machine, we did install SP2

I verified this by upgrading my local machine to SP2 for the client tools and was able to successfully schedule. You might also need to upgrade your server machine to SP2 to work as well.

I hope this helps.

-SX

|||

Haven't had this much fun since SQL2KSP4! Keep smiling....

|||

Hello Visgor Allen and others!

Thank you for reporting this problem, and sorry for the problems that you are experiencing.

I'd like to understand this issue better so we can provide guidance to other customers. Can somebody on this thread please provide more details on how to repro this problem:

1) What is the initial configuration on both server and client machines (if different)? Is it SQL Server 2005 RTM or SP1?

2) Does the problem reproduce after upgrading client/server/both machines to SP2?

3) From what machine (client/server) are you trying to create a new job?

Thanks in advance!

|||

Please suggest me a solution.

sql

Can not create Job on SQL2005

Could not create SQL jobs. Getting Error:

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

- Tried several different job types, always same result.
- Installing SP1 or SP2 does not help.
- Installing with or without Integration Service does not help.

Any help is highly appreciated

Thanks.

Try this:

Dim strDBName As String
Dim strJobID As Guid
Dim jobDumpJob As Job
Dim jbsDumpJobStep As JobStep
Dim intStepID As Integer

' Connect to the server
Dim srvMgmtServer As Server
srvMgmtServer = New Server("MyServer")
Dim srvConn As ServerConnection
srvConn = srvMgmtServer.ConnectionContext
srvConn.LoginSecure = True

jobDumpJob.ApplyToTargetServer(srvMgmtServer.Name)
jobDumpJob.StartStepID = intStepID
jobDumpJob.Alter()

|||

I am also having this problem.

Im trying to create a job to run SQL Server Integration Package.

The Code that you have given above. What is that for?

Thanks

|||This code uses SMO in VB.Net to create a job to execute a TSQL command. Browse around in ObjectBrowser and you should find the properties necessary to execute a SSIS package.|||

I can execute the SISS Package.

But i want to execute it within a job.

Is there any tutorials for creating jobs that i could look at?

|||for some reason it works on an another machine. I dont no why.|||

I figured it out. Despite you could install Management Tool on any computer it will work only on machine that have SQL Server 2005 SP2 installed.

|||Try installing SP2 for the client components on all computers taht run management studio, reboot, then try again from management studio client.|||

Identical problems here--also tried the new hotfix as well.

We've held off rolling out SP2 due to these and other errors. Until someone deals with these problems I suppose my company is stuck.

|||Check whether Distributed Transaction Coordinator service is started. If not, start it and try again.|||

We have a sql2005 installation that I've created jobs on routinely for months and then today we hit this message. I'm not going to install SP2 just yet since some users report that it doesn't help.

The original error message:

TITLE: Microsoft SQL Server Management Studio

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

BUTTONS:

Technical details

===================================

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Program Location:

|||

Hi folks,

I too had the same exact error when trying to schedule a package. After reading numerous posts and forums, some people have said

SP2 solved their problems and some said it didn't.

Here's what I did to get it to work.

On our SQL Server 2005 development machine, we did install SP2

I verified this by upgrading my local machine to SP2 for the client tools and was able to successfully schedule. You might also need to upgrade your server machine to SP2 to work as well.

I hope this helps.

-SX

|||

Haven't had this much fun since SQL2KSP4! Keep smiling....

|||

Hello Visgor Allen and others!

Thank you for reporting this problem, and sorry for the problems that you are experiencing.

I'd like to understand this issue better so we can provide guidance to other customers. Can somebody on this thread please provide more details on how to repro this problem:

1) What is the initial configuration on both server and client machines (if different)? Is it SQL Server 2005 RTM or SP1?

2) Does the problem reproduce after upgrading client/server/both machines to SP2?

3) From what machine (client/server) are you trying to create a new job?

Thanks in advance!

|||

Please suggest me a solution.

Can not create Job on SQL2005

Could not create SQL jobs. Getting Error:

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type
'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

- Tried several different job types, always same result.
- Installing SP1 or SP2 does not help.
- Installing with or without Integration Service does not help.

Any help is highly appreciated

Thanks.

Try this:

Dim strDBName As String
Dim strJobID As Guid
Dim jobDumpJob As Job
Dim jbsDumpJobStep As JobStep
Dim intStepID As Integer

' Connect to the server
Dim srvMgmtServer As Server
srvMgmtServer = New Server("MyServer")
Dim srvConn As ServerConnection
srvConn = srvMgmtServer.ConnectionContext
srvConn.LoginSecure = True

jobDumpJob.ApplyToTargetServer(srvMgmtServer.Name)
jobDumpJob.StartStepID = intStepID
jobDumpJob.Alter()

|||

I am also having this problem.

Im trying to create a job to run SQL Server Integration Package.

The Code that you have given above. What is that for?

Thanks

|||This code uses SMO in VB.Net to create a job to execute a TSQL command. Browse around in ObjectBrowser and you should find the properties necessary to execute a SSIS package.|||

I can execute the SISS Package.

But i want to execute it within a job.

Is there any tutorials for creating jobs that i could look at?

|||for some reason it works on an another machine. I dont no why.|||

I figured it out. Despite you could install Management Tool on any computer it will work only on machine that have SQL Server 2005 SP2 installed.

|||Try installing SP2 for the client components on all computers taht run management studio, reboot, then try again from management studio client.|||

Identical problems here--also tried the new hotfix as well.

We've held off rolling out SP2 due to these and other errors. Until someone deals with these problems I suppose my company is stuck.

|||Check whether Distributed Transaction Coordinator service is started. If not, start it and try again.|||

We have a sql2005 installation that I've created jobs on routinely for months and then today we hit this message. I'm not going to install SP2 just yet since some users report that it doesn't help.

The original error message:

TITLE: Microsoft SQL Server Management Studio

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

BUTTONS:

Technical details

===================================

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Program Location:

|||

Hi folks,

I too had the same exact error when trying to schedule a package. After reading numerous posts and forums, some people have said

SP2 solved their problems and some said it didn't.

Here's what I did to get it to work.

On our SQL Server 2005 development machine, we did install SP2

I verified this by upgrading my local machine to SP2 for the client tools and was able to successfully schedule. You might also need to upgrade your server machine to SP2 to work as well.

I hope this helps.

-SX

|||

Haven't had this much fun since SQL2KSP4! Keep smiling....

|||

Hello Visgor Allen and others!

Thank you for reporting this problem, and sorry for the problems that you are experiencing.

I'd like to understand this issue better so we can provide guidance to other customers. Can somebody on this thread please provide more details on how to repro this problem:

1) What is the initial configuration on both server and client machines (if different)? Is it SQL Server 2005 RTM or SP1?

2) Does the problem reproduce after upgrading client/server/both machines to SP2?

3) From what machine (client/server) are you trying to create a new job?

Thanks in advance!

|||

Please suggest me a solution.

Can not copy view

I have a replication job that can not replicate a view. Any ideas? I am
assuming the replication job relicates views that are associated with the
tables. Is there a way to only replicate the table and not the view?
I'm not sure I follow this

Do you get an error when replicating the view?
If so, please can you post it up. If you just want to replicate the table
and not the view, sp_dropsubscription and sp_droparticle should do it for
you eg
sp_dropsubscription @.publication = 'northwindxxx'
, @.article = 'regionview'
, @.subscriber = 'pll-lt-16'
sp_droparticle @.publication = 'northwindxxx'
, @.article = 'regionview'
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)1

Sunday, March 11, 2012

Can Job Frequency go less than one minute?

Hi,
I'd like to schedule a job on my utility server to run every 15 seconds. Is
it possible to do that in SQL Agent?
Thanks,What kind of task is it ?
--
Message posted via http://www.sqlmonster.com|||You create on job and loop this job with issuing a wait statement for the
time the job didn´t take place.
WAITFOR DELAY '000:00:15'
OR evaluating the time when the last start took and ended and substract that
from the 15 seconds.
--
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Kam" <Kam@.discussions.microsoft.com> schrieb im Newsbeitrag
news:9EA7C3C3-10BC-48C9-9B84-7AF4F9891E56@.microsoft.com...
> Hi,
> I'd like to schedule a job on my utility server to run every 15 seconds.
> Is
> it possible to do that in SQL Agent?
> Thanks,|||Have a look at http://sqldev.net/sqlagent/SQLAgentRecuringJobsInSecs.htm
--
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
"Kam" <Kam@.discussions.microsoft.com> wrote in message
news:9EA7C3C3-10BC-48C9-9B84-7AF4F9891E56@.microsoft.com...
> Hi,
> I'd like to schedule a job on my utility server to run every 15 seconds.
> Is
> it possible to do that in SQL Agent?
> Thanks,

Can Job Frequency go less than one minute?

Hi,
I'd like to schedule a job on my utility server to run every 15 seconds. Is
it possible to do that in SQL Agent?
Thanks,
What kind of task is it ?
Message posted via http://www.droptable.com
|||You create on job and loop this job with issuing a wait statement for the
time the job didnt take place.
WAITFOR DELAY '000:00:15'
OR evaluating the time when the last start took and ended and substract that
from the 15 seconds.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Kam" <Kam@.discussions.microsoft.com> schrieb im Newsbeitrag
news:9EA7C3C3-10BC-48C9-9B84-7AF4F9891E56@.microsoft.com...
> Hi,
> I'd like to schedule a job on my utility server to run every 15 seconds.
> Is
> it possible to do that in SQL Agent?
> Thanks,
|||Have a look at http://sqldev.net/sqlagent/SQLAgentR...JobsInSecs.htm
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
"Kam" <Kam@.discussions.microsoft.com> wrote in message
news:9EA7C3C3-10BC-48C9-9B84-7AF4F9891E56@.microsoft.com...
> Hi,
> I'd like to schedule a job on my utility server to run every 15 seconds.
> Is
> it possible to do that in SQL Agent?
> Thanks,

Can Job Frequency go less than one minute?

Hi,
I'd like to schedule a job on my utility server to run every 15 seconds. Is
it possible to do that in SQL Agent?
Thanks,What kind of task is it ?
Message posted via http://www.droptable.com|||You create on job and loop this job with issuing a wait statement for the
time the job didnt take place.
WAITFOR DELAY '000:00:15'
OR evaluating the time when the last start took and ended and substract that
from the 15 seconds.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Kam" <Kam@.discussions.microsoft.com> schrieb im Newsbeitrag
news:9EA7C3C3-10BC-48C9-9B84-7AF4F9891E56@.microsoft.com...
> Hi,
> I'd like to schedule a job on my utility server to run every 15 seconds.
> Is
> it possible to do that in SQL Agent?
> Thanks,|||Have a look at http://sqldev.net/sqlagent/SQLAgent...gJobsInSecs.htm
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
"Kam" <Kam@.discussions.microsoft.com> wrote in message
news:9EA7C3C3-10BC-48C9-9B84-7AF4F9891E56@.microsoft.com...
> Hi,
> I'd like to schedule a job on my utility server to run every 15 seconds.
> Is
> it possible to do that in SQL Agent?
> Thanks,

Thursday, March 8, 2012

Can i write T-SQL statements to skip other job steps

Hi All,

Please let me know. is it possible to write T-SQL statements in a job step to skip some other job steps.

Regards
Nedu. MOn the 'Advanced' tab of the 'Job Step Properties' you can play with the 'on failure' and 'On Success'.
Ex:
step 1_DO_MY_THING
on success : quit with success
on failure : go to step 2
step 2_REPORT_THE_FAILURE
on success : quit with failure
on failure : quit with failure

In other cases you could merge the steps or save the state somewhere in your db

Friday, February 24, 2012

can I stop a scheduled job by setting @@error manually

I either need to have a job not start if the table is empty or
stop if it is empty.
I Think the the latter would be something like the following
job steps
step 1) count records - success = next step - failure = end job with failure
step 2 ) dts file.
step logic:
step 1) select count(*) from tablea
if count = 0 then set @.@.error = 999 /*or what ever causes job
to fail
else
continue to create file for dts step.
step 2) dts job to export data.
TIAYes, I think you're on the right track. The job's first step could be a
stored proc that does something like this:
select @.RecCount = count(*) from tablea
IF @.RecCount = 0
Begin
Raiserror('Tablea is empty.', 16, 1)
Return 16
End
hth
Tom
tdr wrote:
>I either need to have a job not start if the table is empty or
> stop if it is empty.
>I Think the the latter would be something like the following
>job steps
>step 1) count records - success = next step - failure = end job with failure
>step 2 ) dts file.
>step logic:
>step 1) select count(*) from tablea
> if count = 0 then set @.@.error = 999 /*or what ever causes job
>to fail
> else
> continue to create file for dts step.
>step 2) dts job to export data.
>TIA
>
--
E-mail correspondence to and from this address may be subject to the
North Carolina Public Records Law and may be disclosed to third parties.

Can I start Excel on a PC using a Stored Procedure?

Is there any way to have a job in SQL Server start Excel on a PC?
Thanks in advance,
RaulExcel is a desktop application. You cannot start applications that require
a GUI component from SQL Server... SQL Server Agent will hang.
What exactly are you trying to accomplish?
"Raul" <raul@.nothere.com> wrote in message
news:62AA65E5-C7A4-4B81-9BFC-5A1AC579BE42@.microsoft.com...
> Is there any way to have a job in SQL Server start Excel on a PC?
> Thanks in advance,
> Raul|||You could create a scheduled task on your PC, called Task1, which launches
Excel.
From the SQL server,
xp_cmdshell 'schtasks /run /tn Task1 /s NAMEOFPC'
In order for this to work the SQL server process must be running as a user
that has administrative authority on the PC on which you want to start Excel
.
(Starting a scheduled task remotely requires administrator priveledge). If i
t
is running under the local system account, you could specify a username and
password in the schtasks command:
xp_cmdshell 'schtasks /run /tn Task1 /s NAMEOFPC /u username /p password'
This way would put the password for an (administrative) account in plain
text somewhere, so it is not very secure.
"Raul" wrote:

> Is there any way to have a job in SQL Server start Excel on a PC?
> Thanks in advance,
> Raul|||I want a stored procedure, that is run as a scheduled job in SQL Server
Agent, to return the results of a query to a specific Excel workbook. Once
the data is inserted in the workbook, I would like to run a VBA routine in
the workbook to carry out a number of tasks.
I can write the results of the query in Excel using a linked server to the
desired spreadsheet, but I like to be able to fire off the routine to perfor
m
a number of desired tasks after the data has been inserted.
Raul
"Aaron Bertrand [SQL Server MVP]" wrote:

> Excel is a desktop application. You cannot start applications that requir
e
> a GUI component from SQL Server... SQL Server Agent will hang.
> What exactly are you trying to accomplish?
>
>
>
> "Raul" <raul@.nothere.com> wrote in message
> news:62AA65E5-C7A4-4B81-9BFC-5A1AC579BE42@.microsoft.com...
>
>|||Thanks a bunch! The biggest problem may be getting the IT folks to give me
administrator privileges on the server. I guess the other option is to add
a
new administrator account on my PC.
Thanks again,
Raul
"Mark Williams" wrote:
> You could create a scheduled task on your PC, called Task1, which launches
> Excel.
> From the SQL server,
> xp_cmdshell 'schtasks /run /tn Task1 /s NAMEOFPC'
> In order for this to work the SQL server process must be running as a user
> that has administrative authority on the PC on which you want to start Exc
el.
> (Starting a scheduled task remotely requires administrator priveledge). If
it
> is running under the local system account, you could specify a username an
d
> password in the schtasks command:
> xp_cmdshell 'schtasks /run /tn Task1 /s NAMEOFPC /u username /p password'
> This way would put the password for an (administrative) account in plain
> text somewhere, so it is not very secure.
> --
> "Raul" wrote:
>

Tuesday, February 14, 2012

Can I Query A Temporary Table?

Hi,
I have a job that has been running for years. All of sudden I see
that it's hanging, but not outright failing. I can pinpoint a
specific SP that runs and about how far it gets. It creates a
temporary table which then gets data selected into it and then does
work based on that. I can see that the temp table is created and I've
run the select into query myself and there don't seem to be any
issues. The one thing I can't tell is if there is any data in that
temp table. Is there anyway to query the table or even get
information about how many rows are in it?
Thanks,
BillIs it a global temporary table? If it's a global one, you can simply query
it using SELECT with another session.
If it's a local temporary table, then only one session can reach it, the one
which created it.
However, this temp table will be droped automatically when its owner's
session is closed whether it's glocal or local.
You can find more information about temp tables from the following link:
http://msdn2.microsoft.com/en-us/library/ms174979.aspx
--
Ekrem Önsoy
http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
"zinck74" <bkelly3@.gmail.com> wrote in message
news:1193936161.327854.167670@.k35g2000prh.googlegroups.com...
> Hi,
> I have a job that has been running for years. All of sudden I see
> that it's hanging, but not outright failing. I can pinpoint a
> specific SP that runs and about how far it gets. It creates a
> temporary table which then gets data selected into it and then does
> work based on that. I can see that the temp table is created and I've
> run the select into query myself and there don't seem to be any
> issues. The one thing I can't tell is if there is any data in that
> temp table. Is there anyway to query the table or even get
> information about how many rows are in it?
> Thanks,
> Bill
>|||Yeah, unfortunately it's local table. I can see it in the list of
temporary tables in tempdb, but I can't get any stats on it. It seems
like there should be some way to get the stats somehow. Anyone else?
If anything I'd just like to be able to see the number of rows
Thanks,
Bill
On Nov 1, 11:16 am, Ekrem =D6nsoy <ek...@.btegitim.com> wrote:
> Is it a global temporary table? If it's a global one, you can simply query
> it using SELECT with another session.
> If it's a local temporary table, then only one session can reach it, the =one
> which created it.
> However, this temp table will be droped automatically when its owner's
> session is closed whether it's glocal or local.
> You can find more information about temp tables from the following link:h=ttp://msdn2.microsoft.com/en-us/library/ms174979.aspx
> --
> Ekrem =D6nsoyhttp://www.ekremonsoy.net,http://ekremonsoy.blogspot.com
> MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
> "zinck74" <bkel...@.gmail.com> wrote in message
> news:1193936161.327854.167670@.k35g2000prh.googlegroups.com...
>
> > Hi,
> > I have a job that has been running for years. All of sudden I see
> > that it's hanging, but not outright failing. I can pinpoint a
> > specific SP that runs and about how far it gets. It creates a
> > temporary table which then gets data selected into it and then does
> > work based on that. I can see that the temp table is created and I've
> > run the select into query myself and there don't seem to be any
> > issues. The one thing I can't tell is if there is any data in that
> > temp table. Is there anyway to query the table or even get
> > information about how many rows are in it?
> > Thanks,
> > Bill- Hide quoted text -
> - Show quoted text -

Sunday, March 25, 2012

Can not create Job on SQL2005

Can not create Job on SQL2005

Can not create Job on SQL2005

Can not create Job on SQL2005

Can not create Job on SQL2005

Can not create Job on SQL2005

Can not copy view

Sunday, March 11, 2012

Can Job Frequency go less than one minute?

Can Job Frequency go less than one minute?

Can Job Frequency go less than one minute?

Thursday, March 8, 2012

Can i write T-SQL statements to skip other job steps

Friday, February 24, 2012

can I stop a scheduled job by setting @@error manually

Can I start Excel on a PC using a Stored Procedure?

Tuesday, February 14, 2012

Can I Query A Temporary Table?

install SQL on WinXP

Blog Archive

About Me