Err, no. Selects don't change indexes.

When I ran the query I was...

ugo boy (2/20/2013)

---

When I ran the query, I did not specify any sort order so I am assuming the result will automatically be displayed in the sort order of the...

*Daily* log backups?

Maybe take a read through this - Managing Transaction Logs[/url]

Take a look at this article. http://www.sqlservercentral.com/articles/65804/, there's a section on data purity errors and a like to a kb article that goes into detail on fixing them

Am I correct in saying that the WarehouseDB that you're trying to restore logs to was online and usable before you started? You set the DB to read only (ALTER...

The only real solutions here are:

Set the backup app to snapshot the machine but exclude the databases. Some tools can, some can't. If you have a good SQL backup strategy,...

Then speak to your IT security team and ask them what the message means and what they want you to do about it.

Where do you see that and what are you trying to do?

Or creating them online/offline?

SQLCrazyCertified (2/19/2013)

---

Hi, sorry, I was not aware of this, anyway, with truncate only option only available for sql 2005 right? because I know they took away this option for 2008...

If the code you posted was indeed the entire trigger, then yes, that will update the entire table

UPDATE test

SET col2 = col1

FROM test

Since there's no conditions, no restrictions and nothing...

Correct, shrink with truncate only doesn't fragment indexes, but it also may not reduce space usage if the space and the end of the file is in use.

The SQL engine has no such threshold (well, other than it can't rebuild a 1 page index). Even with 2 it will run the rebuild/reorg. Probably won't have much if...

In full or bulk-logged recovery model, only a log backup will truncate the log. In simple recovery, a checkpoint truncates the log.

Not directly. You could navigate the index levels like SQL does when looking for data.