In SQL Server 2000 (by the way, you posted this ina SQL Server 2005 forum)...

Is this what you are after?

/*

code date ...

24 5/15/08

24 6/12/07

26 1/15/02

27 7/24/08

27...

Remember ... (Name the movie and the character!)

Looks like it has to do with the order in which your items are listed in the UPDATE statement. Please check out the following code based on what you...

Better question, are there any rows...

In the senerio you have created, it may not be possible. It might, however, if the mdf file became corrupt during normal processing to perform a tail log backup...

Or it is being done in a test environment to identify/test recovery processes.

That doesn't mean that the threshold for running an autoupdate for statistics has been reached. This doesn't happen with every insert.

If you want to ensure statistics are updated on...

It depends on how much update activity occurs on the table. If there isn't a lot of activity, the statistics won't get updated unless you force it. autoupdate...

clive (11/6/2008)

---

Below are 2 reasons to truncate SQL Server log file/s (transaction log):

1.

Truncate log file/s if you have very little disk space left due to the SQL Server log...

That explains it. You posted this in...

If the transaction log file still exists, you may still be able to run a tail log backup and recover your database up to the point the database file was...

Glad to have been able to help.

Not mentioned as an answer, but here is a workaround using varchar(max) (or nvarchar(max)); build views over the two tables and cast the text/ntext column as a varchar(max)/nvarchar(max) datatype in...

Yep, you are missing the STOPAT = date-time in the second restore log. You need to specify the time just before dropping the table to recover the table from...