It must have been the magnifying glass that did the trick 😀

Do you mind sharing the solution you came up with ?

In this case it is relevant !

A...

Indeed, you still need to prepare these actions;

In best cercumstances, you would collect performance data (trace), analyse it, and check your results with the dev.team.

... we're already in the doghouse...

Jeffrey Williams (6/24/2009)

---

Okay, since this was a cancelled restore you should be able to right-click the restoring database and delete it. Once deleted, you can then delete the mdf/ldf...

By default, every table should have a clustering index !

If you don't have one now, convert one of the (singl column/narror) indexes.

If that CLIX doesn't serve you well, you pick...

my 2ct.

"It doesn't matter" is to heavy, because you may need to restore more pages than with a nicely 100% organized db.

However, you will need the original databases file sizes...

Dave (6/24/2009)

---

I was trying to move a SS2000 database to a SS2005 server. I backed up the SS2000 database, copied the .bak file to the SS2005 box, and started...

- A unique key would also do just fine !

- strange .... a large...

- Be sure to add GDR R2 to your vstedba (datadude) because it adds some nice db-features.

( http://www.microsoft.com/downloads/details.aspx?FamilyID=bb3ad767-5f69-4db9-b1c9-8f55759846ed )

FYI: The Datadude's lair: http://blogs.msdn.com/gertd/default.aspx 😉

I'm not yet a user, but I...

CU4 for SP3 is out now.

What makes this CU very interesting is that "lock pages in memory" is now available in Standard Edition (X64)!

.

http://support.microsoft.com/kb/970279/en-us

its build number: 9.00.4226

Mani (6/23/2009)

---

Thank you..

one more question..Do you take the Tape backups of Differential and log backup files too? Is that necessary.

Because currently we are taking the Tape Backups after the full...

a3b2c1r46 (6/23/2009)

---

Its probably worth noting that I first noticed this problem shortly after I moved this DB to a new server. I shrunk the TL before I moved it and...

- The "inserted" and "deleted" (table) objects are only available in the trigger itself.

- The A in the code is the table alias for table F_articlewhere, meaning in that query...

Indeed, perform full db maintenance

start with:

DBCC CHECKDB (0) WITH ALL_ERRORMSGS, DATA_PURITY;

go

print '' ;

print '*********************************'

print '**'

print '** If DBCC CheckDB returned DATA_PURITY errors, you must view http://support.microsoft.com/kb/923247 !!! and repair...

did you update your statistics ?

- sp_updatestats

- dbcc updateusage (0) with count_rows