Huh?

An insert into a full...

Paul White (9/8/2009)

---

GilaMonster (9/8/2009)

---

Yes, there's a slim chance and there's nothing wrong with doing a checktable after each log restore but to say "you know that the corruption occurs somewhere...

Is autoshrink on? Is there a manual shrink operation occurring?

Paul White (9/8/2009)

---

So, you are saying there are absolutely no circumstances where SQL Server can directly cause page corruption in its files? The word 'usually' suggests not - in...

Only in South Africa - http://pigeonrace2009.co.za/pigeon-race-2009

My money's on the pigeon.

Paul White (9/8/2009)

---

GilaMonster (9/8/2009)

---

Log backups generally will only have...

ben.mcintyre (9/8/2009)

---

I badly need my views here. Due to the size of the data chunks I'm dealing with I have to wrap them in views to stay sane. ...

Highlight the query and click the 'Display estimated execution plan' button on the toolbar, or select 'Display estimated execution plan' from the query menu, or press Ctrl-L

Log backups generally will only have corruption in them...

All restores (single page, file or full) have to start from a full backup. For full details of restoring a page, see http://msdn.microsoft.com/en-us/library/ms186858(SQL.90).aspx and http://msdn.microsoft.com/en-us/library/ms175168%28SQL.90%29.aspx

Why?

winston Smith (9/7/2009)

---

Cool. thanks for the answers. im just wondering as if such an issue occured, and you had to restore, chances are you dont have time to restore a...

jymoorthy (9/7/2009)

---

In case, if you have created the new file in the same file group (PRIMARY), then you may stop the grow option on the old file and enable grow...

If you add 3 indexes each on a single column, SQL will likely use only one of them. There is something called index intersection, where SQL will seek on multiple...

Look up Tail-log backup in SQL's books online (I'm not going to outright give you the answer to an interview question)

However that's only an option if the DB is in...