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...

Just missing one thing, the expected results. Based on the sample data provided, what SHOULD the output look like. You should be able to put that together manually,...

Provide us with the t-sql scripts you used to restore the database. Based solely on your description, we really can't tell you what you did wrong, if anything.

Actually, I can see why they may need two years of data online. Previous employer required that we maintain that much history in OLTP system (COBOL/ISAM databases). We...

How about the DDL for the tables, some sample data (as insert statements that can be cut, paste, and executed in SSMS) to load into the tables, and the expected...

What version of SQL Server are you running?

Also, post the SQL Code you used and got the error with, please.

Not really sure, but do you have indexes like these on the table in the query? The names used for the indexes are mine.

create nonclustered index IX_vgh_ProductsQry1

on dbo.GICSPFVendorCategoryHeader (

...

The best alternative you have, you've been told you can't use. This is a perfect place to use SQL Server Service Broker. A trigger sends a message to...

Here is a code sample for dropping records from a table in batches:

declare @backupcnt int;

declare @backupfile varchar(128);

set @backupcnt = 0;

-- Delete records that are more than 5 years old from...

All I can say, is maybe. When I found out that NS would not be a part of SQL Server 2008, I stopped even looking at it for anything....