serge.kovacs (1/26/2009)

---

Maybe I wasn't clear on the inner workings of the application on start-up. It will load all data from all tables so there should be no need to use...

Please don't shout (type in all caps). It's not going to make someone help you faster. If I may suggest,...

Can you ask then to substantiate the statement? Either prove it with an exec plan (where a covering...

madhu.arda (1/26/2009)

---

How this will effect sharepoint databases? if anything happens, will MS support us? and they said rebuild index task is corrected in SP2, that means if we have SP2...

I just wanted to emphasise the fragmented indexes that it would cause.

Since the PK column is not declared as identity, you'll need to specify the values for the ID column. That's what it's complaining about, not the 'John Doe' name.

As the...

Jeff Moden (1/26/2009)

---

Doesn't look like they fixed then in 2k8 and I'd be real surprised (and happy) if they actually fixed them in 2011. Seems like they're spending...

madhu.arda (1/26/2009)

---

when the large mdf file is corrupted, we will lose all the data. If we have multiple file, if one of the filees is corrupted, then we have a...

No idea. I know databases, not drives

That said, from those errors it appears that you have one...

If that table is frequently inserted into, then I'd suggest put the cluster on the identity, even if it's never used. That way the cluster will organise the table and...

Still, if it's giving errors there's a problem. You don't want to find the problem when the drive...

Jeff Moden (1/26/2009)

---

The backup to such a "break" for the quirky update method is that the ORDER BY method also works although it works at about half the speed. ...

Yes! Very much so. A bad choice of a cluster can do terrible things to performance. Uniqueindentifier...

That looks like problems with the IO subsystem. Possibly intermittent right now.

Check the windows event log for anything indicating hardware problems, check the SQL error log, check any logs from...

Cricketdogger (1/21/2009)

---

Then I turned on auto-shrink overnight and was very happy to see that this morning the database was only 56 gb (down from 128 gb). I will re-index...