No. We're volunteers, and we're not here to do the job that you're paid to do. We're all perfectly willing to help out if you've made the effort...

Satish

Since the script doesn't have "7zip" in it, it's not going to get you very far. Search for "7zip command line" to get the syntax. How are you...

What script have you tried? It's quite easy to use the 7zip command line.

John

Is there any reason you can't schedule your full backup as well? It's correct to say that you can backup with users on the system. However, given that...

You certainly need to investigate why a database of that size has a log of that size. My point was only that if it won't truncate automatically, it won't...

The easiest way to do that is just to wait and the log will be automatically truncated for you. You shouldn't have to wait more than a minute for...

Here's one thing you can try:

http://social.msdn.microsoft.com/forums/en-US/sqlintegrationservices/thread/fe402094-d218-4b6c-b7a4-f45b2d604cb1/

If that doesn't work for you, do what I just did and copy that error message into your favourite search engine. There's plenty of...

I think that option is available in SQL Server 2008 but not 2005. If you have cluster resources and groups left over, have you tried removing them using the...

If you can't or won't correct your design as suggested by Joe, use the MERGE statement as suggested by Sandeep.

John

Sourav

I'm not quite sure what you're doing with your completion_Status column. You're returning 'Completed Full BKP' if the backup (of any type) is more than an hour old, and...

Definitely worth checking, yes. When he said "the job consumed 73GB", I wanted to check that it wasn't just the case that the file ended up at 73GB due...

Paul, there's also the possibility that he's backing up to the same file without using WITH INIT, which is why I asked him to run RESTORE HEADERONLY. This is...

Well, if this hasn't been working for two months, chances are that you really do have a log file that's so large that you can't fit the backup on your...

Point taken, Drew - I should have phrased it better and said "your code would be clearer if" rather than "you need to". You're right that there's no syntactical...

You need to handle all eventualities once and once only in your case expression - something like this:

...

CASE WHEN Interval < 1 THEN 'X'

WHEN Interval >= 1 AND Interval <...