Thanks for the head's up. Anyway you can send me an example of what you've done for a backup failure message stored proc?

rogerabram@gmail.com

Rog

It worked out just fine and I really want to thank you for your help!

Rog

Thank you!

Thank you for your response. We deleted some records out of the database to be able to get back into it... it had hit the MSDE 2 gig limit....

Thanks!

Rog

Thank you... this one was the easiest for me to incorporate and it worked just fine.

Roger

Just an FYI in case someone should come across this issue too.

Make sure the following registry key exists. If not, then create the key and populate it accordingly.

Key=BackupDirectory

Type=String

Location=HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/MSSQLServer/MSSQLServer

Value=C:\Program Files\Microsoft...

Thank you for the suggestion. We rebooted the SQL server and that didn't resolve the issue.

Does anyone have any other ideas?

Thank you.

Rog

Thank you!

Rog

Thanks! That helped reveal a new problem with the data itself! Several ID numbers have matching expiration dates but different record_group types. So now the challenge is...

It worked. Thanks!

Rog

Thank you! That worked.

I have another conversion issue... I have another decimal field which stores a monetary value in the form of

393420

which I want to put into another...

Many many thanks!

That did the trick.

Roger

I do get some errors and not sure what they all mean:

Microsoft (R) SQL Server Execute Package Utility

Version 9.00.3042.00 for 32-bit

Copyright (C) Microsoft Corp 1984-2005. All rights reserved.

NULL

Started: 2:25:06...

Perfect! That did the trick... however I can't get it to run in the stored proc.. that is, actually execute the package.

Here's what I'm using:

Declare @dtscmd varchar(400) <- one...