Good point Elliot,

Just remove the parameters completely if you always set them in the proc anyway.

CREATE PROCEDURE yourProcNameHere

AS

BEGIN

DECLARE @EndDate DATETIME,

...

You can't pass a value to a stored proc like that.

You must do it like this:

DECLARE @start DATETIME, @end DATETIME

SELECT @start = dateadd(m,-1, dateadd(s,-1,dateadd(dd, datediff(d,0,getdate()),0)) ),

...

See here

...or this

Have a look at this article

Haven't you already asked this here http://www.sqlservercentral.com/Forums/Topic775061-147-1.aspx?

Here you go, try this. You'll need a Tally table first (see here[/url]):

DECLARE @startDate datetime, @endDate DATETIME

SELECT @startDate = '20090101', -- First day in range

...

Ashka Modi (8/25/2009)

---

2) Use of cursor is never been a good idea. cursor includes lot of overhead to query. if you can use if else or for loop just avois...

Do you mean it's an IDENTITY column? I.e each row in the table has a unique ID value.

If so you'll need a different...

With the Background property

Jeff,

Are you sure? Take a look at this.

Also the argument to xp_cmdshell is varchar(8000)!?

Nigel

Try this to get a set of the month end dates you are interested in, it might help you on your way.

Note: You'll need to read Jeff Moden's Tally Table...

Your function can be rewritten using this single statement, which is an adpatation of Gail's from the link in the previous post:

select dateadd(dd,-1,dateadd(mm, datediff(mm,0, getdate())+1,0))

The result has a time...

Question:

Why is your @cmd variable of type sysname? This has a max length of 256, which has the potential to get truncated if @ReqContent is too long. Try changing to...

gerald.drouin (8/13/2009)

---

Thanks for the catch on the negative numbers. I've added a 14 day offset to ensure the code always lands in the current month. Works for every...