Thank you for the reply, Phil!

It was a minor adjustment on the networking folks, and it is fixed now.

thx

Not exists is much atomic than sets.

Use Not Exists.

Nice piece to read.

Well, gurus, I have decided to trash that instance and have created another one.  It was a new dev box that did not work well.

I will chalk...

Yes, agree. I have used the advanced option to write out the error / message / etc. but it does not get there.. and there is no history, here is...

The _Sandbox exists in other servers without any issues. That's correct.

Here is the definition.

It is a simple 1 liner. The perfmon show that there are several retries before it crashes.

The services are running.

USE [msdb]
GO

/****** Object:  Job...

I have a similar issue.

select 1    this is all I have in a test SQL Agent job and runs forever.

This is an enterprise 2019 on a datacenter server.

on top of...

Some minor fix is required.

Originally, the AvgHighTempC is set to "not null", by default.

To make the "update table" work, the table constructor needs the "null" for the said column.

CREATE TABLE...

• This reply was modified 4 years, 1 month ago by  John Esraelo-498130. Reason: adding more comment

use "distinct" at the bottom of your CTE,  right after "select"  on the line where you have the "windowing" (over.. partition..)

I am not 100% sure, but, give it a shot

• This reply was modified 5 years, 5 months ago by  John Esraelo-498130.

How about having a shared location, sort of a DMZ, since the DEV cannot see the PROD by design.

A scheduled agent task / job at the destination can run an...

The AD group should have "connect" privilege by modifying the properties of the database (for each DB). Then, you would need to create role(s) and assign read/write/view definition/etc. for the...

If this column is not acting as a foreign key to another DB object(s) then perhaps my suggestion may raise eye-brows.

Add a new col, put the values that you wish...

I came too late into this conversation and I hope I make sense.

Option 2 is not bad.  However, if I had to take that route then I would first create...

Have you tried using client provider 10 to connect to your 2008 sql server?

That could be the problem.