Steve Jones - SSC Editor (4/28/2011)

---

One thing to keep in mind, if you are looking for partial database recovery in a DR situation, moving the indexes away from the table...

Ninja's_RGR'us (4/28/2011)

---

Himmat Singh (4/28/2011)

---

1)use db_name

2) set the database recovery to simple - sp_dboption 'db_name', 'trunc. log on chkpt.', true

3) write a store produre to delete about 10000 per loop....

Yes, that is how I do it, with no problems. It also gives...

Don't forget full backups beforehand.

Going forward, you can use something like this to identify databases that have not been backed up. Perhaps put it into a job with an email alert

SELECT B.name as...

Also, make sure you are on at least SP3. Earlier versions have various Maint Plan bugs.

Probably silly question, but did you specify "ONLINE" in your statement even though you have enterprise edition ?

I think you could use the GUI and select the tables with check marks.

Is that what you're asking ?

You're messing me up with...

I think you should apply at least SP3. SP4 has been out a while now.

What Service Pack are you on ?

Some 2005 maintenance plan problems were fixed with SP3. Not sure of the specifics though.

I would not suggest importing data into production that is not production data. Better to export from production to a test area.

For your query, just specify the database name:

select *...

I assumed an active production database would be full recovery, so I added #2 as additional suggestion.

With simple recovery, you don't mind the possibility of losing all changes made since...

use mssqlresource

exec sp_helpfile

Redgate has a data compare tool you could consider.

Or write queries comparing all the fields in all the table affected.

Give customer read-only permission.