The first option is reasonable, except WinZip doesn't work with the files of such size.

The second option is not clear, I don't see how stripped backup can help you with...

That is correct.

You may also run this script, which gives you more related info:

---------------------------------------------------------------------------------

--Database Backups for all databases For Previous Week

---------------------------------------------------------------------------------

SELECT

CONVERT(CHAR(100), SERVERPROPERTY('Servername'))...

You are welcome.

Just remember that code of SP doesn't care about physical location of SP, only a job does. So if you put the USE YourDB_name... statement in a code...

You can fix your problem with SP like that.

Just point your SP to the right database placing this code at the beginning of code in your SP:

USE YourDB_name

...

Hmm..

If you are looking for more simple way, I can see two:

1. Create this SP in a master database instead, so it will be always there regardless of your restores

2....

You may want to see some other options from the previous discussion:

http://www.sqlservercentral.com/Forums/Topic736321-146-1.aspx?Highlight=backup+table

I want to put my 2 cents since this discussion moved from "How to move files" to "How to copy/move database".

In this case we can also use a Copy Database...

You can install any other version of SS except EE on Windows XP.

Look at here:

http://technet.microsoft.com/en-us/library/ms143506(SQL.90).aspx">Look at here:

http://technet.microsoft.com/en-us/library/ms143506(SQL.90).aspx

Again, you simply cannot install SS Enterprise edition on Windows XP SP3 clearly, this cofiguration is not supported.

Steve and Lynn,

Thank you for a good discussion.

The UPDATE/DELETE/INSERT may not even be able to complete the respective action because it can't get the required locks due to the locks put on the rows/pages/extents/table as a result...

I also think you missed the point, as Steve pointed out, only changes are logged. A simple, or complex, select statement for a report is only reading the database. Not...

Steve Jones - Editor (9/24/2009)

---

Only changes are logged in the transaction log. A SELECT will not cause problems in the transaction log. It could cause tempdb issues, and possible tempdb...

Lynn,

If it is only one process running against this DB, it will...