Or add a ShopID to the appropriate tables so you know which records belong to which shop. Would require some changes to the indexing probably as well.

mw112009 (1/29/2010)

---

Sorry for the confusion.

You were right!

That was a transaction log.

We did find the actual backup file it is 78GB large and also there was a second file

that was 12GB...

Check BOL (Books Online).

Doesn't tell me a thing.

run the following and post the results:

restore headeronly N'D:\NGProd_backup_201001280600.trn'

restore filelistonly N'D:\NGProd_backup_201001280600.trn'

The .trn file is a transaction log backup file, you need to restore the most current FULL backup first. If you also need to restore differential and/or transaction log...

Gift Peddie (1/29/2010)

---

Ritesh Medhe (1/29/2010)

---

is there any sepcial kind of optimisation setting that needs to be done if SS2008 is running on AMD? I ran same SQL query on Intel...

Ryan (1/29/2010)

---

If your table is very large and the time it takes to delete a subset of the data is an issue then perhaps you could partition the table? ...

Here is a restore command. You will have to make appropriate changes to match your actual environment.

restore database NGProd

from disk = N'D:\Backups\NGProd.bak' -- assumes the file is local

with file...

You can restore your database using the most current full backup file and all transaction log backups taken since that full backup to recover your database.

Just a guess, but maybe different CU's? My SQL Server 2008 installs are all at 2531, SP 1 with no additional CU's applied.

I'm going to go with the standard consultant answer, it depends. At this point, just cut it down to the actual CREATE TABLE statements.

Please post the entire query.

thanks

CirquedeSQLeil (1/29/2010)

---

I was thinking that it could...

Assuming you are trying to delete from table1, try this:

delete from

dbo.table1

from

dbo.table1 as source

where

...

The only way I have successfully defragged my mdf/ldf files that reside on our SAN is to do it while SQL Server was shutdown. And in a couple of...