And (broken record time) the execution plans for the queries that are causing you the most pain.

I had never heard of that before, so I did some searching around. You're not the only one to see this. From what I can see out there, it's actually...

Lookup Backup in the books online.

You might also look at this[/url].

The pro to having a single table, and I see only one, is that you don't have to worry about JOIN statements in your queries. With decent indexes and appropriate...

Make sure the other parts of the IF statement are also wrapped in BEGIN..END. You simply can't have multiple statements within an IF clause without wrapping them.

You only get one statement after an IF clause so your current code is hitting RETURN and exiting. Try this:

ELSE

BEGIN

--==== If The file does not exist...

Thanks for that. I love these forums. I learn something new every single day.

I haven't tried that yet. I suppose it will work if documentation says so. It's not one of these places I like to take chances with.

Then you have to restore to a new location, either a new database or a new server, and then move the data you need to recover from that new location...

The answer to that really depends on the query in question. Here's an example where each results in the same data

SELECT a.*

FROM TableA a

WHERE a.ColA IN (SELECT ColA FROM TableB)

SELECT...

Please don't cross-post.

Answering over here: http://www.sqlservercentral.com/Forums/Topic540018-149-1.aspx

As long as you don't have conditional execution of the procedures, you can really go either way. You should get identical plans. This becomes a problem when people put IF...

If you're creating the SSIS packages in 2008, you won't be able to deploy them to 2005. I also strongly recommend you DO NOT install 2008 alongside 2005 just yet....

Interesting Jack, thanks for the info. I was under the impression that it was possible to lose data, regardless of the mechanisms...

So, if I start the service on the server...

Statement complete should have choked you out with information, especially if you're running cursors. So you went into TSQL and turned on SQL:StmtCompleted and into Stored Procedures and enabled SP:StmtCompleted?...