There are a couple problems that seem to be copy/paste issues, and then a couple others.

First, the As Partition YearlyDateRange_pf All To ([Primary]) bit at the end of the CREATE...

Perhaps something like this?

CREATE TABLE Query_Test

(

CPU INT ,

ApplicationName VARCHAR(100) ,

...

I feel like there must be more at work than what we've seen so far, because a quick test with your sample data returns 345.00 for just the first method...

Yes, it's necessary.

If you just do (HOUR(create_dtim)>=19 AND MINUTE(create_dtim)>=46), then that requires every returned row to have a minute greater than or equal to 46. Because of that, you...

There are a couple ways to do this.

Let's say you're wanting only rows where the time portion is greater than or equal to 22:15 in the date range in your...

The pound signs around the dates make me think Access is being used. Just a hunch...

There are a couple problems.

The first is that spMSforeachdb takes the command as a parameter declared as nvarchar(2000). Your command is much longer than that, so it's getting truncated, resulting...

Luis Cazares (11/19/2015)

---

You're missing the obvious way to get the current date. :hehe:

USE [msdb]

GO

DECLARE @jobId BINARY(16);

EXEC dbo.sp_add_job @job_name=N'GetCurrentDate',

@enabled=1, @job_id = @jobId OUTPUT;

EXEC dbo.sp_add_jobserver

@job_name =...

Sean Lange (11/19/2015)

---

Jacob Wilkins (11/19/2015)

---

jasona.work (11/19/2015)

---

Luis Cazares (11/19/2015)

---

jasona.work (11/19/2015)

---

I was going to post this over in Steve's call for Good Basic T-SQL Exercises but decided not to pollute the topic...

jasona.work (11/19/2015)

---

Luis Cazares (11/19/2015)

---

jasona.work (11/19/2015)

---

I was going to post this over in Steve's call for Good Basic T-SQL Exercises but decided not to pollute the topic with fluff...

So I'm posting...

Yeah, to add to what g.britton said, some of the ideas with batching are:

1) Holding locks for a shorter duration

2) Better control over log growth; based on whether the DB...

Hmmm...what exactly are you trying to do?

As written, the query will never terminate, because the command to increment @C is within the scope of the IF statement, so...

Good to hear! Had I read the error completely (doh!) that would have been pretty clear from the get-go, due to its occurrence on line 0.

At any rate, I'm glad...

Ah, in that case it's likely the statement calling the procedure. Are you putting single quotes around the date values you're passing as the two date parameters? If not, those...

Most likely INVC_DT is stored as an integer, and the BETWEEN comparison is throwing that error. The explicit CAST of INVC_DT to a date type would also fail in that...