DB Backup Maint Plan - old file deletes

Hello. When using a DB Maint Plan to backup databases,
say 10 databases all in one plan... the job backs up each
database and THEN at the end of the entire job, it deletes
the previous backups (based on your backup retention).
question>> is there any way to backup the database, and
RIGHT THEN, in a Maint Plan job, delete the PREVIOUS
backup files? The problem is that you need enough disk
space to hold the current and old backups for ALL
databases being backed up, unless there's some setting
we're missing? Any thoughts on that? (using DB Maint
Plans, I know we could code things ourselves and NOT use
Maint Plans)... THanks, BruceThis is a multi-part message in MIME format.
--=_NextPart_000_03A4_01C3B337.52A2A5B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
If you're cramped for space, consider replacing the single maintenance plan
with one plan for each DB. This way, the old backup for a database is
removed before the next plan kicks in.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Bruce de Freitas" <bruce@.defreitas.com> wrote in message
news:0fca01c3b360$91c86e90$a401280a@.phx.gbl...
Hello. When using a DB Maint Plan to backup databases,
say 10 databases all in one plan... the job backs up each
database and THEN at the end of the entire job, it deletes
the previous backups (based on your backup retention).
question>> is there any way to backup the database, and
RIGHT THEN, in a Maint Plan job, delete the PREVIOUS
backup files? The problem is that you need enough disk
space to hold the current and old backups for ALL
databases being backed up, unless there's some setting
we're missing? Any thoughts on that? (using DB Maint
Plans, I know we could code things ourselves and NOT use
Maint Plans)... THanks, Bruce
--=_NextPart_000_03A4_01C3B337.52A2A5B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

If you're cramped for space, consider =replacing the single maintenance plan with one plan for each DB. This way, =the old backup for a database is removed before the next plan kicks =in.
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
"Bruce de Freitas" wrote in =message news:0fca01c3b360$91=c86e90$a401280a@.phx.gbl...Hello. When using a DB Maint Plan to backup databases, say 10 databases all =in one plan... the job backs up each database and THEN at the end of the =entire job, it deletes the previous backups (based on your backup =retention). question>> is there any way to backup the database, =and RIGHT THEN, in a Maint Plan job, delete the PREVIOUS backup =files? The problem is that you need enough disk space to hold the current =and old backups for ALL databases being backed up, unless there's some =setting we're missing? Any thoughts on that? (using DB Maint =Plans, I know we could code things ourselves and NOT use Maint Plans)... =THanks, Bruce

---

--=_NextPart_000_03A4_01C3B337.52A2A5B0--|||Yep, we talked about that as a possibility. It's nice to
have DB backups in one Maint Plan though sometimes, and
was wondering if there was a way to do that. THanks
Tom... Bruce
>--Original Message--
>If you're cramped for space, consider replacing the
single maintenance plan
>with one plan for each DB. This way, the old backup for
a database is
>removed before the next plan kicks in.
>--
>Tom
>----
--
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com/sql
>
>"Bruce de Freitas" <bruce@.defreitas.com> wrote in message
>news:0fca01c3b360$91c86e90$a401280a@.phx.gbl...
>Hello. When using a DB Maint Plan to backup databases,
>say 10 databases all in one plan... the job backs up each
>database and THEN at the end of the entire job, it deletes
>the previous backups (based on your backup retention).
>question>> is there any way to backup the database, and
>RIGHT THEN, in a Maint Plan job, delete the PREVIOUS
>backup files? The problem is that you need enough disk
>space to hold the current and old backups for ALL
>databases being backed up, unless there's some setting
>we're missing? Any thoughts on that? (using DB Maint
>Plans, I know we could code things ourselves and NOT use
>Maint Plans)... THanks, Bruce
>|||This is a multi-part message in MIME format.
--=_NextPart_000_048B_01C3B33F.F3F4BCC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Maintenance plans give you ease of use, but that does not always translate
to "most efficient".
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Bruce de Freitas" <bruce@.defreitas.com> wrote in message
news:109a01c3b368$e3450d70$a401280a@.phx.gbl...
Yep, we talked about that as a possibility. It's nice to
have DB backups in one Maint Plan though sometimes, and
was wondering if there was a way to do that. THanks
Tom... Bruce
>--Original Message--
>If you're cramped for space, consider replacing the
single maintenance plan
>with one plan for each DB. This way, the old backup for
a database is
>removed before the next plan kicks in.
>--
>Tom
>----
--
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com/sql
>
>"Bruce de Freitas" <bruce@.defreitas.com> wrote in message
>news:0fca01c3b360$91c86e90$a401280a@.phx.gbl...
>Hello. When using a DB Maint Plan to backup databases,
>say 10 databases all in one plan... the job backs up each
>database and THEN at the end of the entire job, it deletes
>the previous backups (based on your backup retention).
>question>> is there any way to backup the database, and
>RIGHT THEN, in a Maint Plan job, delete the PREVIOUS
>backup files? The problem is that you need enough disk
>space to hold the current and old backups for ALL
>databases being backed up, unless there's some setting
>we're missing? Any thoughts on that? (using DB Maint
>Plans, I know we could code things ourselves and NOT use
>Maint Plans)... THanks, Bruce
>
--=_NextPart_000_048B_01C3B33F.F3F4BCC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Maintenance plans give you ease of =use, but that does not always translate to "most efficient".
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
"Bruce de Freitas" wrote in =message news:109a01c3b368$e3=450d70$a401280a@.phx.gbl...Yep, we talked about that as a possibility. It's nice to have DB =backups in one Maint Plan though sometimes, and was wondering if there was a =way to do that. THanks Tom... Bruce>--Original Message-->If you're cramped for space, consider replacing the single maintenance plan>with one plan for each DB. This =way, the old backup for a database is>removed before the next plan =kicks in.>>-->Tom>>--=---->Thomas A. Moreau, BSc, PhD, MCSE, MCDBA>SQL Server MVP>Columnist, =SQL Server Professional>Toronto, ON Canada>www.pinnaclepublishing.com/sql>>>"Bruc=e de Freitas" wrote in message>news:0fca01c3b360$91c86e90$a401280a@.phx.gbl...>Hell=o. When using a DB Maint Plan to backup databases,>say 10 databases =all in one plan... the job backs up each>database and THEN at the end of =the entire job, it deletes>the previous backups (based on your backup =retention).>>question>> is there any way to =backup the database, and>RIGHT THEN, in a Maint Plan job, delete the PREVIOUS>backup files? The problem is that you need enough disk>space to hold the current and old backups for =ALL>databases being backed up, unless there's some setting>we're missing? =Any thoughts on that? (using DB Maint>Plans, I know we could =code things ourselves and NOT use>Maint Plans)... THanks, Bruce>

---

--=_NextPart_000_048B_01C3B33F.F3F4BCC0--

DB backup job for DB maintenance plan failed

I have few doubts as below state:
1) What's the cause for DB backup job for DB maintenance plan failed?
2) What's the measure to correct this problem?
Thanks in advance.
MS KhorKhor,
What's in the:
1) SQL Server error log
2) SQL Agent error log
3) Windows Event log
Right click the maintenance plan, select History, and double click any
errors you see there. What do they say? Paste the text to this group.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Khor wrote:
> I have few doubts as below state:
> 1) What's the cause for DB backup job for DB maintenance plan failed?
> 2) What's the measure to correct this problem?
> Thanks in advance.
> MS Khor

DB backup job for DB maintenance plan failed

I have few doubts as below state:
1) What's the cause for DB backup job for DB maintenance plan failed?
2) What's the measure to correct this problem?
Thanks in advance.
MS Khor
Khor,
What's in the:
1) SQL Server error log
2) SQL Agent error log
3) Windows Event log
Right click the maintenance plan, select History, and double click any
errors you see there. What do they say? Paste the text to this group.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Khor wrote:
> I have few doubts as below state:
> 1) What's the cause for DB backup job for DB maintenance plan failed?
> 2) What's the measure to correct this problem?
> Thanks in advance.
> MS Khor

DB backup job for DB maintenance plan failed

I have few doubts as below state:
1) What's the cause for DB backup job for DB maintenance plan failed?
2) What's the measure to correct this problem?
Thanks in advance.
MS KhorKhor,
What's in the:
1) SQL Server error log
2) SQL Agent error log
3) Windows Event log
Right click the maintenance plan, select History, and double click any
errors you see there. What do they say? Paste the text to this group.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Khor wrote:
> I have few doubts as below state:
> 1) What's the cause for DB backup job for DB maintenance plan failed?
> 2) What's the measure to correct this problem?
> Thanks in advance.
> MS Khorsql

DB Backup Job for a Maintenance Plan taking a long time

Hello,
I am trying to schedule complete backups of some of the databases that I
have on my database server using the Database Maintenance Plan. However,
when the DB Backup Job is run for backing up the database, it just keeps on
executing (status). There is no backup file created for any of the database
that I have chosen.
However, if I can manually backup each of the database by Right-clicking
each database in Enterprise Manager and choosing 'Backup Database'.
For some reason, the same backup process fails / takes very very long time
when I use a scheduled job created from the Database Maintenance Plan.
Any ideas?
Thanks
What's in the maintenance report? Any errors ? Where are you backing up
to ? Disk or Tape. If it is tape, did you check that the path to the
default backup directory exists ?
Markus
|||Sorry, that last comment should have been "IF yo backup to DISK (not
tape) check if the path exists"
M
|||I have the same problem (SQL7), except that the backup file is created (in
about a minute and a half) but the SQL Agent Job never completes. I have to
manually stop and restart SQL agent for the job status to return to "not
running". I have checked the backup and it is a valid file (restores in
about three minutes).
Job was created using Maintenance plan, backing up to device (filepath) on
the server.
The actual command in the job step is:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
153F9792-4A76-44CD-944E-C581659E556D -To "Warren Rudman" -WriteHistory
-BkUpMedia DISK -BkUpDB -UseDefDir -DelBkUps 1WEEKS -CrBkSubDir -BkExt
"BAK"'
"Vince Keller" wrote:

> Hello,
> I am trying to schedule complete backups of some of the databases that I
> have on my database server using the Database Maintenance Plan. However,
> when the DB Backup Job is run for backing up the database, it just keeps on
> executing (status). There is no backup file created for any of the database
> that I have chosen.
> However, if I can manually backup each of the database by Right-clicking
> each database in Enterprise Manager and choosing 'Backup Database'.
> For some reason, the same backup process fails / takes very very long time
> when I use a scheduled job created from the Database Maintenance Plan.
> Any ideas?
> Thanks
>
>
|||Follow up:
The problem persisted, so I removed the backup from the maintenance plan and
created it as a stand alone job. There are several ways to do this, the
simplest being to go to enterprise manage, expand your server, expand
Management, and and right-click on Backup. Select backup database, and make
sure that the schedule checkbox is selected (at the bottom of the dialogue).
Now the job runs fine. The remaining jobs of the orignial maintenance plan
show the same errant behavior, though... never quite completing.
"WD Rudman" wrote:
[vbcol=seagreen]
> I have the same problem (SQL7), except that the backup file is created (in
> about a minute and a half) but the SQL Agent Job never completes. I have to
> manually stop and restart SQL agent for the job status to return to "not
> running". I have checked the backup and it is a valid file (restores in
> about three minutes).
> Job was created using Maintenance plan, backing up to device (filepath) on
> the server.
> The actual command in the job step is:
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 153F9792-4A76-44CD-944E-C581659E556D -To "Warren Rudman" -WriteHistory
> -BkUpMedia DISK -BkUpDB -UseDefDir -DelBkUps 1WEEKS -CrBkSubDir -BkExt
> "BAK"'
> "Vince Keller" wrote:

DB Backup Job for a Maintenance Plan taking a long time

Hello,
I am trying to schedule complete backups of some of the databases that I
have on my database server using the Database Maintenance Plan. However,
when the DB Backup Job is run for backing up the database, it just keeps on
executing (status). There is no backup file created for any of the database
that I have chosen.
However, if I can manually backup each of the database by Right-clicking
each database in Enterprise Manager and choosing 'Backup Database'.
For some reason, the same backup process fails / takes very very long time
when I use a scheduled job created from the Database Maintenance Plan.
Any ideas'
ThanksWhat's in the maintenance report? Any errors ? Where are you backing up
to ? Disk or Tape. If it is tape, did you check that the path to the
default backup directory exists ?
Markus|||Sorry, that last comment should have been "IF yo backup to DISK (not
tape) check if the path exists"
M|||I have the same problem (SQL7), except that the backup file is created (in
about a minute and a half) but the SQL Agent Job never completes. I have to
manually stop and restart SQL agent for the job status to return to "not
running". I have checked the backup and it is a valid file (restores in
about three minutes).
Job was created using Maintenance plan, backing up to device (filepath) on
the server.
The actual command in the job step is:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
153F9792-4A76-44CD-944E-C581659E556D -To "Warren Rudman" -WriteHistory
-BkUpMedia DISK -BkUpDB -UseDefDir -DelBkUps 1WEEKS -CrBkSubDir -BkExt
"BAK"'
"Vince Keller" wrote:
> Hello,
> I am trying to schedule complete backups of some of the databases that I
> have on my database server using the Database Maintenance Plan. However,
> when the DB Backup Job is run for backing up the database, it just keeps on
> executing (status). There is no backup file created for any of the database
> that I have chosen.
> However, if I can manually backup each of the database by Right-clicking
> each database in Enterprise Manager and choosing 'Backup Database'.
> For some reason, the same backup process fails / takes very very long time
> when I use a scheduled job created from the Database Maintenance Plan.
> Any ideas'
> Thanks
>
>|||Follow up:
The problem persisted, so I removed the backup from the maintenance plan and
created it as a stand alone job. There are several ways to do this, the
simplest being to go to enterprise manage, expand your server, expand
Management, and and right-click on Backup. Select backup database, and make
sure that the schedule checkbox is selected (at the bottom of the dialogue).
Now the job runs fine. The remaining jobs of the orignial maintenance plan
show the same errant behavior, though... never quite completing.
"WD Rudman" wrote:
> I have the same problem (SQL7), except that the backup file is created (in
> about a minute and a half) but the SQL Agent Job never completes. I have to
> manually stop and restart SQL agent for the job status to return to "not
> running". I have checked the backup and it is a valid file (restores in
> about three minutes).
> Job was created using Maintenance plan, backing up to device (filepath) on
> the server.
> The actual command in the job step is:
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 153F9792-4A76-44CD-944E-C581659E556D -To "Warren Rudman" -WriteHistory
> -BkUpMedia DISK -BkUpDB -UseDefDir -DelBkUps 1WEEKS -CrBkSubDir -BkExt
> "BAK"'
> "Vince Keller" wrote:
> > Hello,
> >
> > I am trying to schedule complete backups of some of the databases that I
> > have on my database server using the Database Maintenance Plan. However,
> > when the DB Backup Job is run for backing up the database, it just keeps on
> > executing (status). There is no backup file created for any of the database
> > that I have chosen.
> >
> > However, if I can manually backup each of the database by Right-clicking
> > each database in Enterprise Manager and choosing 'Backup Database'.
> >
> > For some reason, the same backup process fails / takes very very long time
> > when I use a scheduled job created from the Database Maintenance Plan.
> >
> > Any ideas'
> >
> > Thanks
> >
> >
> >

DB Backup Job for a Maintenance Plan taking a long time

Hello,
I am trying to schedule complete backups of some of the databases that I
have on my database server using the Database Maintenance Plan. However,
when the DB Backup Job is run for backing up the database, it just keeps on
executing (status). There is no backup file created for any of the database
that I have chosen.
However, if I can manually backup each of the database by Right-clicking
each database in Enterprise Manager and choosing 'Backup Database'.
For some reason, the same backup process fails / takes very very long time
when I use a scheduled job created from the Database Maintenance Plan.
Any ideas'
ThanksWhat's in the maintenance report? Any errors ? Where are you backing up
to ? Disk or Tape. If it is tape, did you check that the path to the
default backup directory exists ?
Markus|||Sorry, that last comment should have been "IF yo backup to DISK (not
tape) check if the path exists"
M|||I have the same problem (SQL7), except that the backup file is created (in
about a minute and a half) but the SQL Agent Job never completes. I have to
manually stop and restart SQL agent for the job status to return to "not
running". I have checked the backup and it is a valid file (restores in
about three minutes).
Job was created using Maintenance plan, backing up to device (filepath) on
the server.
The actual command in the job step is:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
153F9792-4A76-44CD-944E-C581659E556D -To "Warren Rudman" -WriteHistory
-BkUpMedia DISK -BkUpDB -UseDefDir -DelBkUps 1WEEKS -CrBkSubDir -BkExt
"BAK"'
"Vince Keller" wrote:

> Hello,
> I am trying to schedule complete backups of some of the databases that I
> have on my database server using the Database Maintenance Plan. However,
> when the DB Backup Job is run for backing up the database, it just keeps o
n
> executing (status). There is no backup file created for any of the databas
e
> that I have chosen.
> However, if I can manually backup each of the database by Right-clicking
> each database in Enterprise Manager and choosing 'Backup Database'.
> For some reason, the same backup process fails / takes very very long time
> when I use a scheduled job created from the Database Maintenance Plan.
> Any ideas'
> Thanks
>
>|||Follow up:
The problem persisted, so I removed the backup from the maintenance plan and
created it as a stand alone job. There are several ways to do this, the
simplest being to go to enterprise manage, expand your server, expand
Management, and and right-click on Backup. Select backup database, and make
sure that the schedule checkbox is selected (at the bottom of the dialogue).
Now the job runs fine. The remaining jobs of the orignial maintenance plan
show the same errant behavior, though... never quite completing.
"WD Rudman" wrote:
[vbcol=seagreen]
> I have the same problem (SQL7), except that the backup file is created (in
> about a minute and a half) but the SQL Agent Job never completes. I have
to
> manually stop and restart SQL agent for the job status to return to "not
> running". I have checked the backup and it is a valid file (restores in
> about three minutes).
> Job was created using Maintenance plan, backing up to device (filepath) on
> the server.
> The actual command in the job step is:
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 153F9792-4A76-44CD-944E-C581659E556D -To "Warren Rudman" -WriteHistory
> -BkUpMedia DISK -BkUpDB -UseDefDir -DelBkUps 1WEEKS -CrBkSubDir -BkExt
> "BAK"'
> "Vince Keller" wrote:
>

DB Backup Job

Hi All,

I have a db backup job on SQL Server 2005 server that has a delete step that deletes a backup file that is located on the SQL Server 2000 server. Here is the step:

EXEC master..xp_cmdshell 'del \\DevServerName\Dev-bkups-db\BackupsDB\DBName\DBName_db*.bak /q'

The step doesn't create any errors but it doesn't delete the file. When I run the same command from the command prompt it deletes the file.

I can't figure out what is wrong. Any Idea?

Thanks.Try using Query Analyzer to execute:DECLARE @.foo INT
EXEC @.foo = master..xp_cmdshell 'del \\DevServerName\Dev-bkups-db\BackupsDB\DBName\DBName_db*.bak /q'
SELECT @.foo AS CmdErrorLevelBoth the output and the error level ought to give you clues. My first guess is that the Windows Login being used by xp_cmdshell doesn't have permissions.

-PatP|||I get an Access Denied error and CmdErrorLevel 1. How can I find out which account is used by xp_cmdshell? And what permissions does this accout need?|||it needs sysadmin rights. I think it is using whatever account is running the SQL agent. This account also needs write access to the destination.|||How can I find out which account is used by xp_cmdshell?
sp_xp_cmdshell_proxy_account (http://msdn2.microsoft.com/en-us/library/ms190359.aspx) is where you can set it.what permissions does this accout need?This is the $64,000 question. Microsoft recommends little or no permissions, and I generally agree with them because of the security risks.

I would recommend making the step in the backup job a command step instead of a SQL step. That way you can set the Windows Credentials there, and you don't need to open up xp_cmdshell at all.

-PatP|||How do you set the credentials?|||Check the sql agent service in services.msc. If it's running with a domain account, then that account needs to have access to delete from \\DevServerName\Dev-bkups-db\BackupsDB\DBName\. It doesn't necessarily need admin rights to DevServerName.|||It is running with a local system account.|||local system account can not access network resources.|||Which account should be SQL Agent service startup account?|||typically I have the network guys create a LAN account dedicated to this purpose with a password that does not expire. This last part is very important.|||Thanks for your help.|||How do you set the credentials?The easy way is to change the job owner. There are sneaky ways too, especially if you've installed the Windows Resource Kit or are willing to write a bit of VBA code.

-PatP|||Thrasymachus,

Forgot to ask what are the minimum rights does this account need?

Db Backup

I need to creat SQL Database backup that I can have a user with no SQL serve
r
installed on his/her PC to be able to execute the Backup Job how can I use i
n
exe.
thanks,
OmranHi
You can write a program in ADO or ADO.NET that will execute the backup
command for you.
Alternatively you can set up a SQL Agent job on the server that will
automatically backup the database at a given time/date. Check out the backup
database wizard or maintenance plans. This would require no intervention fro
m
the user.
John
"Omran Abdurrahman" wrote:

> I need to creat SQL Database backup that I can have a user with no SQL ser
ver
> installed on his/her PC to be able to execute the Backup Job how can I use
in
> exe.
> thanks,
> Omransql

Db Backup

I need to creat SQL Database backup that I can have a user with no SQL server
installed on his/her PC to be able to execute the Backup Job how can I use in
exe.
thanks,
OmranHi
You can write a program in ADO or ADO.NET that will execute the backup
command for you.
Alternatively you can set up a SQL Agent job on the server that will
automatically backup the database at a given time/date. Check out the backup
database wizard or maintenance plans. This would require no intervention from
the user.
John
"Omran Abdurrahman" wrote:
> I need to creat SQL Database backup that I can have a user with no SQL server
> installed on his/her PC to be able to execute the Backup Job how can I use in
> exe.
> thanks,
> Omran

DateTime function question

Greetings all,

Is there a function that exists that returns the last day of each month?

I need to allow payments to a job number if the import date is before the cancel dates following month end.

So I can't dateadd or datediff as far as I can see with any accuracy.

Any suggestions?

Adamus

how about this Adamus

Code Snippet

CREATE function [dbo].[Last_Day_Of_Month](@.monthIn varchar(2), @.yearIn char(4))

returns datetime

as

begin

DECLARE @.wrkMonth char(2),

@.wrkDay char(2),

@.wrkDate DATETIME

select @.wrkMonth = right('00' + @.monthIn, 2)

if isdate(convert(char(02), @.wrkMonth) + '-01-' + convert(char(04), @.yearIn))=0

begin

return null

end

SET @.wrkDate = @.yearIn + '/' + @.monthIn + '/01'

return DATEADD(DD, -1, DATEADD(M, 1, @.wrkDate))

end

|||

Another way is something like:

Code Snippet

select dateadd(day, -1, dateadd(mm, 1, dateadd(mm, datediff (mm, 0, getdate()), 0)))

2007-07-31 00:00:00.000

You're welcome Adam.

|||

Both work beautifully.

Thanks guys...I just couldn't wrap my head around it this morning.

Adamus