Here is the framework for a solution but I need some of the information I requested to be sure it meets all the business requirements:

if OBJECT_ID('tempdb.dbo.#hours') is not null

...

Gstar1224 (2/18/2016)

---

Hey Everyone,

I have been trying to build a query that would calculate the number of concurrent users every hour for a date range(Lets say a month). Below is...

Thanks. Please provide a CREATE TABLE statement including all indexes and constraints.

Log Shipping is tried and true, no doubt, but data center operations folks mostly (in my experience) think about 0 data loss from a DR perspective and therefore favor mirroring...

Seems you've ruled out a database problem. Maybe contact the Power Builder folks or post your question on a Power Builder forum.

Earlier you said you were not, from the new database via the OLE DB Driver....

Is the table partitioned?

Seems like you isolated it to a driver issue. If memory serves, the OLE DB driver in SNAC actually leverages the ODBC driver behind the scenes so the problem may...

ChrisM@Work (2/16/2016)

---

Orlando Colamatteo (2/15/2016)

---

Can you try it in order from most rows to least, see Jeff's follow-up post to mine. The thought being to reduce the set as much as...

Lynn Pettis (2/16/2016)

---

I don't like using closed ended ranges for date ranges. Prefer close ended on the...

TheSQLGuru (2/16/2016)

---

Just have a job step that starts the next job you want to run AFTER the completion of the first job. Easy-peasy-lemon-squeezy! 🙂

sp_job_start is the sproc IIRC. You could...

Thanks for clarifying. My understanding is that processes running as "local system" may have trouble accessing network resources.

You've proven it works when the services are running as your account. Not...

Maybe semantics, but wasn't thinking of anything to incorporate in your existing code. I was proposing new code and a new step 2 in your job.

Suggestion: make a new...

Please read the article I linked to. While a scan of the data is inevitable with like%% the technique in the article still improves performance even with 0% nulls.

How about this:

Job starts at 20:15:

Step 1: take backup

Step 2: T-SQL, if before 21:00 run WAITFOR TIME '21:00'; else just be done

Step 3: do important stuff